Guide6 min readUpdated
App Design Timeline: Week by Week for a Small App Project
An app design timeline week by week: what happens in each phase, what you do and what you receive. A typical 4 week plan for a small app, with real ranges.
Suppose a founder in Siliguri says, "My developer starts in a month. Can the app design be ready by then?" The answer depends on the number of screens and on how fast feedback comes back. This guide shows an app design timeline week by week, so you can see what happens in each phase and when you are needed.
An app design timeline is the schedule that shows which design work happens in which week, from the first questions to the files handed to your developer. App design usually takes 2 to 4 weeks, and the price is a custom quote based on the number of screens and user roles. The week plan below is a typical example for a small app, not a fixed rule.
What is a typical app design project week by week?
A small app design project usually fits in 4 weeks, with one main phase per week. The table below is a typical example for a small app. Your own plan will move with your screens and your reply speed.
| Week | Phase | What I do | What you do | What you receive |
|---|---|---|---|---|
| 1 | Understand and map the flow | Ask questions, study users and competitors, plan the screens and paths | Answer questions, share ideas and any existing documents | A list of screens and the main user flows |
| 2 | Wireframe | Draw every screen in simple boxes | Review the screens and the order of steps | Wireframes for all screens |
| 3 | Design the interface | Add colour, type, icons and components | Give feedback in 2 to 3 revision rounds | Full screen designs |
| 4 | Prototype and hand off | Link screens into a clickable demo and prepare files | Click through, test with a few people, approve | A prototype and organised Figma files |
These five stages are my usual process: Understand, Map the flow, Wireframe, Design the interface, Prototype and hand off. The week plan combines the first two into week 1 because they are close in a small app. Payment is 50% to begin and 50% on completion.
For the thinking behind each phase, read my mobile app design process. This guide focuses on the calendar.
What happens in week 1, and what do I need to do?
Week 1 turns your idea into a list of screens and paths. You need to answer questions quickly, because every later week builds on these answers.
I ask who uses the app, what problem it solves and what the first successful action is. For a food ordering app, that action is "order placed". For a loan app, it may be "application submitted". Then I map the user flow: the steps from opening the app to that first success.
Suppose you plan an app for a local grocery store with two user roles: customers and delivery staff. Each role has its own screens. So two roles roughly mean two small apps inside one. This is why user roles affect the quote.
What to bring to week 1:
- A one-paragraph description of the app and the customer
- A list of must-have features, and a separate list of nice-to-have features
- Screenshots of two or three apps you like
- The name of the one person who makes final decisions
If you are unsure what to include first, MVP design: what to build first will help you cut the list.
What are wireframes, and what is week 2 for?
Week 2 produces wireframes: simple black and white drawings of every screen, showing what goes where. You check the flow and the content order, not the look.
You review the screens in order, as a user would. Ask yourself: can a first-time user finish the main task without help? On the grocery example, you tap through "Home, Product, Cart, Address, Payment, Order placed" and count the steps. If the address step asks for twelve fields, we shorten it now.
Week 2 is also the best time to remove features. A screen removed here costs nothing. A screen removed after the interface design costs the time already spent. The article on wireframe vs mockup vs prototype explains why this order is cheaper.
For Indian apps, I plan details here that people forget: OTP login, UPI payment and a regional language option.
How does week 3 work, and where do revision rounds fit?
Week 3 is the interface design phase, where the wireframes get colours, fonts, icons and real content. This is also where most of your 2 to 3 included revision rounds happen.
You will see your app as it will really look. Then you give feedback. The most useful way is one combined list per round from everyone who has a say. I fix the points, send the new version, and the next round begins.
Review the designs on a real phone if you can, not only on a laptop. Your customers will likely use a mid-range Android phone, so text size and button size matter. The guides on designing for low-end phones and slow networks and accessibility in app and web design explain what to check.
Feedback that slows week 3:
- Comments that arrive from five people at different times
- A new feature added after wireframes were approved
- A change of brand colours halfway through
What do you receive in week 4, at prototype and handoff?
In week 4, you receive a clickable prototype and Figma files organised for your developer. A prototype is a demo where you tap buttons and move between screens like a working app, without any code behind it.
Use the prototype before development begins. Give your phone to two or three real users, such as a shop owner or a student, and ask them to complete the main task. Watch where they stop. If you want to show the app to an investor, the prototype is also what you present.
Then I prepare the files: named screens, reusable components, colours and text styles, and notes for the developer. The Figma developer handoff checklist shows what a good handoff contains.
Why can an app design take 2 weeks or 4 weeks?
The range of 2 to 4 weeks comes from the size of the app and from how fast you reply. A small app with one user role and few screens sits at the short end. More screens and more roles move it toward the longer end.
Three things change the schedule most:
- Number of screens. Every screen needs a wireframe, a design and a check.
- Number of user roles. A customer app plus a seller app plus an admin panel is three sets of screens.
- Reply speed. A project can pause for days if a decision waits for one busy person.
Android and iOS also affect the plan. For the price side, app design cost per screen explained shows why screens and roles drive the quote, and how long does design take compares timelines across project types.
If your app is ready for this kind of plan, you can read about my mobile app design service or share your idea through the contact section.
Frequently asked questions
How long does it take to design a mobile app?
+
App design usually takes 2 to 4 weeks. The number of screens, the number of user roles and your reply speed decide where in that range your project falls.
Is the 4 week plan fixed for every app?
+
No. The week plan is a typical example for a small app. A larger app, or one with several user roles, needs a plan built for its own screens.
When do I pay during an app design project?
+
You pay 50% to begin and 50% on completion. UPI and bank transfer work in India, and PayPal works for international clients.
Can my developer start before the design is finished?
+
A developer can often start on setup work early. Screens should be built only after they are approved, so the developer does not build something that later changes.
Working on something like this?
Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.