Guide5 min readUpdated
App Design Cost per Screen: How Designers Count
App design cost per screen explained: how designers count screens, states and variants, and why a simple screen count can mislead your budget.
By Tithi Mondal, UI/UX Designer
A founder in Kolkata asks three designers the same question: "What is your price per screen for my delivery app?" One says a low number per screen. Another says a much higher number. Neither is lying. They are counting different things. This guide explains how designers count, so you can compare fairly.
App design cost per screen means the design price divided by the number of screens in an app. It is a useful rough idea, but it can mislead, as the sections below show.
How do designers count screens in an app?
A designer counts a screen as one unique layout a user sees, such as a login page or an order list. Two screens that look alike but hold different content may count as one layout or as two, depending on the designer. That difference is the main reason quotes do not match.
Ask every designer one question: "What exactly do you count as one screen?" The answer tells you more than the price.
I do not use a flat rate per screen. I price UI/UX for apps as a custom quote based on screens and user roles. A role is a type of user. A buyer, a seller and an admin are three roles, and each sees different screens.
What are states and variants, and why do they matter?
A state is a different condition of the same screen. A variant is a version of the same screen for a different user or device. Both add design work that a simple screen count hides.
Take one screen, the order list in a food ordering app. It needs several states:
- Normal. A list with 5 orders.
- Empty. The user has no orders yet. A message and a button are needed.
- Loading. The list is on its way over a slow network.
- Error. The network failed. The user needs a clear retry action.
- Filtered. The user selected "this week" and sees fewer results.
That is 5 states of 1 screen. A good designer designs all five, because users on mid-range Android phones and slow networks will meet each of them. Read more about empty, loading and error screens to see why these matter.
Why does screen count mislead?
Screen count misleads because the effort of one screen can be 10 times the effort of another. A static "About us" page takes little time. A seller verification flow with document upload takes much more.
Consider two apps, both with 20 screens:
| App A | App B | |
|---|---|---|
| Type | Simple information app | Marketplace with sellers and buyers |
| Roles | 1 | 3 |
| States per key screen | 1 to 2 | 4 to 5 |
| Forms and validation | Few | Many |
| Effort | Lower | Much higher |
Both have 20 screens, yet App B needs far more design thinking. A flat price per screen would charge the same for both, and one of the two clients would overpay or the designer would lose time.
On the Sokoni seller app, the seller onboarding and verification steps had far more states than the listing screens. A raw count of screens would have hidden that. Counting by flow and by role made the scope honest.
How can I estimate the number of screens before I ask?
You can estimate by listing flows, not screens. A flow is the set of steps a user takes to finish one task. List each task, then the steps inside it.
Try it for a simple booking app:
- Sign up. Phone number, OTP (a one-time code sent by SMS), name, done.
- Find a service. Home, search, results, service detail.
- Book. Choose date, choose time, confirm, pay by UPI, success.
- Manage. My bookings, booking detail, cancel.
That is about 15 unique screens before any states. Add states, and the real number grows. This is why I ask for flows when I quote. If you cannot list flows yet, a short call on Google Meet or WhatsApp can help us draw them together.
For a first version, keep the flow list short. My guide on MVP design: what to build first shows how to cut scope without losing the core idea.
Which roles and extra screens do people forget?
Founders often forget the admin side and the small system screens. These add real work, and they are usually missing from the first estimate.
- Admin panel. Someone must approve sellers, see orders and refund payments. Read about admin dashboard design.
- Settings and profile. Language, notifications, saved addresses.
- Permission screens. Asking for camera, location or notification access.
- Payment steps. UPI app choice, pending, failed, success. Each of these four is a separate screen state.
- Regional languages. Bengali or Hindi text can change layouts, because the letters are wider and need more line spacing than English.
If you add these to your list before asking, your quote will not grow later.
Here is a small example of how the list grows. Suppose a coaching app has 12 screens in the founder's first sketch. After we add the admin login, a batch list for teachers, fee payment states, a notification settings page and an empty state for new students, the list becomes close to 30 unique screens. Nothing was wrong with the first sketch. It simply showed the happy path only. A designer who asks about roles and failures early gives you a number you can trust.
How long and how is payment handled?
App design usually takes 2 to 4 weeks. My process has five stages: understand, map the flow, wireframe, design the interface, and prototype and hand off. The flow mapping stage is where screens, roles and states become a clear list.
Payment is 50% to begin and 50% on completion, by UPI or bank transfer. Two to three revision rounds are included. For overall cost thinking, see the mobile app design cost guide and the UI/UX design cost guide.
What should I send to get an accurate quote?
Send these and I reply within 24 hours:
- A short description of the app and who uses it.
- The user roles: for example buyer, seller, admin.
- A list of tasks, or flows, in your own words.
- Apps you like, with the screens you want to be similar.
- Whether you need Android, iOS or both.
- Languages needed, such as English and Bengali.
- Whether you already have a brand look or logo.
- Your target date for the first release.
I give a fixed quote after seeing the scope. If you are ready, see my mobile app design service or write to me.
Frequently asked questions
Do you charge a fixed price per screen?
No. I price UI/UX for apps as a custom quote based on screens and user roles, because screens differ a lot in effort.
What is a screen state?
A state is a different condition of one screen, such as normal, empty, loading or error. Each state may need its own design.
How many screens does a small app have?
It depends on the number of tasks and user roles. List your flows first, and count the steps inside each flow to get a rough number.
How long does app design take?
App design usually takes 2 to 4 weeks. The time depends on the number of screens, roles and flows.
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.