Guide6 min readUpdated
Mobile App Design Questions Answered: Screens to Handoff
Answers to mobile app design questions: screens, Android vs iOS, prototypes, admin panels, handoff, next steps and protecting your idea.
By Tithi Mondal, UI/UX Designer
Screens and scope
How many screens does a mobile app have?
A simple app has about 10 to 15 screens. A marketplace or a booking app can have 30 or more, because each user role, each error state and each empty state needs a screen. Count the screens by writing each task a user does, then list the screens that task needs. The count drives the price.
What screens does almost every app need?
Almost every app needs a splash screen, a sign-in screen with OTP, a home screen, a profile screen, a settings screen, a notification list, and error screens for no internet and no results. Designers often forget the error and empty screens. See app onboarding UX best practices.
How much does mobile app design cost?
Prices in the market vary with the number of screens, the number of user roles and the amount of research. My UI/UX work for apps is a custom quote based on screens and user roles. Write your screen list first, then ask for a quote. Read mobile app design cost in India.
What is a user role and why does it change the price?
A user role is a type of person who uses the app, such as customer, seller or admin. Each role sees different screens and different buttons. On a seller app I designed for a marketplace, the seller needed screens for onboarding, verification and listings that a buyer never sees. More roles mean more screens.
Should I design every feature in the first version?
No. Build the first version around one main task. A food ordering app needs browsing, cart and payment first. Reviews, offers and loyalty points can come later. A smaller first version reaches users sooner, and real feedback shows which later features people want. Write the extra features in a separate list.
Android, iOS and the web
Should I design for Android or iOS first?
Start with the platform your customers use. In India most users are on Android, and many use mid-range phones. If your customers are mostly in Indian towns, begin with Android. If they are mostly in cities with higher spending, check your own audience before choosing. Read designing apps for Indian users.
Do I need separate designs for Android and iOS?
Not always. One well-made design can serve both platforms, with small changes to match platform habits, such as the back gesture and the way menus open. Separate designs for each platform cost more time. Ask your designer which differences matter for your app.
What is the difference between a native app and a cross-platform app?
A native app is built separately for each platform, for example one for Android and one for iOS. A cross-platform app is built once and runs on both. This is a development choice, not a design choice. Your developer decides it, and the design works for both. Ask the developer to explain the trade-offs.
How should an app handle payments for Indian users?
Offer UPI first, because most Indian users already pay with it. Show the amount clearly, let the user pick a UPI app, and show a clear success or failure screen with a retry button. Do not make people type card details unless needed. See UPI payment UX and checkout design.
Can the app work in Bengali, Hindi or other languages?
Yes, but plan it from the first screen. Indian scripts take more space than English, and long labels can break a button. A design for one language must be checked in each language. I work in Bengali and English. Read regional language app design in India.
Should I build an app or a mobile website?
Choose an app when people use the product often, need notifications, or need the camera or location. Choose a mobile website when people visit rarely, such as for a one-time booking, or when you want a low-cost start. Many businesses launch a site first and an app later.
What phone sizes does the design need to cover?
Phones differ in screen width, and a design must not break on a small screen. I design for a common mid-size phone first, then test the layout on a smaller and a larger frame. Text must stay readable and buttons must stay tappable. See designing for low-end phones and slow networks.
Prototype and testing
What is an app prototype?
A prototype is a clickable model of your app made from the designed screens. You tap on a button and the next screen opens. No real data or code runs. You can install the link on a phone and show it to users, investors or developers, before spending money on development.
Is a prototype different from a wireframe or a mockup?
Yes. A wireframe is a plain sketch of the layout. A mockup is the full-colour design of one screen. A prototype links the screens so they can be tapped. Each stage adds more detail. Read wireframe vs mockup vs prototype.
How do I test a prototype with real users?
Give the prototype to five people who match your customers. Ask each person to finish one task, such as "order a meal for dinner", and say nothing else. Watch where they pause or tap the wrong place. Each pause is a design problem to fix. See usability testing on a small budget.
Admin panel and handoff
Does my app need an admin panel?
If the app has content, users or orders that someone must manage, yes. An admin panel is a web dashboard for your team. It lets staff approve sellers, answer orders, change prices or send notices without asking a developer. Without it, every small change needs code. Read about admin dashboard UI/UX design.
Is the admin panel designed together with the app?
It should be planned together, because the app and the panel share the same data. If a seller uploads a document in the app, the admin panel needs a screen to review it. Designing both at once avoids missing screens. The panel is usually a larger screen layout with tables and filters.
What is design handoff?
Handoff is the step where the designer passes the final design to the developers, with spacing, colours, fonts, icons and the order of screens clearly marked. A clean Figma file saves developers' time and reduces mistakes. See the Figma developer handoff checklist.
After the design
What happens after the app design is finished?
Developers build the app from the design, and testers check it on real phones. Expect small questions from developers during this time. Agree at the start whether your designer will answer these questions and for how long. Then you will know who to ask when something is unclear.
How long does mobile app design take?
App design usually takes me 2 to 4 weeks. More screens, more user roles and slow feedback make it longer. The design alone is not the whole app. Development takes extra time after design. See mobile app design cost in India and the mobile app design service.
Protecting your idea
Will a designer steal my app idea?
Ideas are rarely the real value. Execution is. Still, your worry is fair. Ask your designer to sign a non-disclosure agreement (NDA) before you share details. Check their past work and ask for references. See questions to ask a UI/UX designer before hiring.
What is an NDA and when should I ask for one?
An NDA is a written promise that the other person will not share your private information. Ask for it before you explain your business model, your technology or your plans. Share only what the designer needs at each stage. This is general information and not legal advice. For a binding contract, ask a lawyer.
If you have an app idea and want to see how many screens it needs, you can write to me through the contact section.
Frequently asked questions
How many screens does a mobile app have?
A simple app has about 10 to 15 screens. A marketplace or a booking app can have 30 or more, because each user role, each error state and each empty state needs a screen. Count the screens by writing each task a user does, then list the screens that task needs. The count drives the price.
Should I design for Android or iOS first?
Start with the platform your customers use. In India most users are on Android, and many use mid-range phones. If your customers are mostly in Indian towns, begin with Android. If they are mostly in cities with higher spending, check your own audience before choosing. Read designing apps for Indian users.
Does my app need an admin panel?
If the app has content, users or orders that someone must manage, yes. An admin panel is a web dashboard for your team. It lets staff approve sellers, answer orders, change prices or send notices without asking a developer. Without it, every small change needs code. Read about admin dashboard UI/UX design.
What is an NDA and when should I ask for one?
An NDA is a written promise that the other person will not share your private information. Ask for it before you explain your business model, your technology or your plans. Share only what the designer needs at each stage. This is general information and not legal advice. For a binding contract, ask a lawyer.
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.