A first app MVP usually needs somewhere between 8 and 20 screens, and published design guides put the design cost of a simple one at roughly $3,000 to $15,000. Screen count is the number that moves that price most. It is also the number founders count worst. The gap between a good count and a bad one is where surprise invoices come from.
The guides agree on the shape and disagree on the figures. One places a simple MVP at 5 to 10 screens, another at 5 to 15, a third at 10 to 15. Mid-complexity apps start somewhere past 15 and run to about 40, at $15,000 to $40,000. Per-screen prices are all over the place: $200 to $1,000 in one guide, $895 to $2,555 for a US agency in another. Treat them as the outline of a market, not a quote. Nobody can price your app from a table.
A screen is not a unit. One guide estimates a static settings page at 4 to 8 hours and a role-based dashboard at 16 to 40, both at the same $50 an hour. Fifteen screens of forms and lists and fifteen with a dashboard and a map share a count and nothing else. If a quote says "15 screens" and stops there, ask which fifteen.
Then there are the screens nobody lists. A list view also needs its empty state, its loading state and its error state. One published model assumes about three states per screen, which roughly triples the number of frames a designer draws. Those states are often missing from quotes, and the work does not disappear. Developers either invent the missing states on the spot or come back with questions, and both cost more than designing them once.
Two more multipliers hide in the brief. Each extra user role (a customer, an admin, a driver) adds 30% to 50% to design hours in one guide, because every role sees different screens. Covering iOS and Android adds 15% to 30% if they share one design language, and more if each goes fully native.
On top of the screens sits fixed work: discovery and a screen inventory, a visual direction or a small design system, a clickable prototype, and handoff notes for the developers. One guide puts that at roughly 30 to 60 hours, another allows several times more. This is why a two-screen change and a whole MVP both have a floor under the price.
Can you cut screens to cut cost? Yes, if you cut features that do not carry the core value. Fewer launch screens means a smaller bill, and that is sound advice. It goes wrong when the cuts hit the screen that explains the product to a first-time user, or the error states, or the handoff. The cost does not vanish. It moves to the developers, then to the first week, when people open the app and have no idea what to do.
Before you ask anyone for a price, write the screen list. One line per screen, its states, and who sees it. A studio can price a list like that in days, and it cannot honestly price "an app like that other one". Bring the list to Kott Studio and we will tell you which screens carry the product and which can wait.