Article5 min readUpdated
Android or iOS First? How to Decide What to Design Now
Android or iOS first? A design-focused guide to platform differences in UI, when one design can serve both, and how to choose your first platform.
Android or iOS first is a design question before it is a development question. It decides which patterns you follow: how users go back, where the main tabs sit, how buttons and alerts look. Android is the operating system from Google. iOS is the operating system on iPhones. Each has its own design guidance, and users expect apps to follow it.
Imagine a founder in Siliguri who is building a booking app for local tour guides. Her guides use Android phones. Her first tourists use both. She asks me which to design first. My answer depends on who touches the product in the first three months, not on which system seems more premium.
Should I design for Android or iOS first?
Design first for the platform of your first 100 users. Not the platform you personally use, and not the one that looks nicer in a pitch.
If you are building for Indian consumers, small shopkeepers, delivery partners, farmers or students, you will often meet mid-range Android phones. That is a general truth about India and you can test it. Ask your first users to show their phone, or add one question to your signup form: "Which phone do you use?"
iOS first can still be right. A paid tool for designers, a premium service for urban professionals or an app for foreign visitors may begin on iPhones. The rule is the same: follow your users.
What are the main platform differences in UI?
The differences are in navigation, system components and small behaviours, not in your product idea. A person should feel at home on their own phone.
| Part of the screen | iOS habit | Android habit |
|---|---|---|
| Going back | Swipe from the left edge, back arrow in the top bar | System back button or gesture, which every screen must respect |
| Main navigation | Tab bar at the bottom | Bottom navigation bar or a side drawer |
| Title alignment | Often centred | Often left aligned |
| Primary action | A button in the top bar or inside the page | Often a floating round button |
| Alerts and pickers | Native iOS sheets and wheels | Native Android dialogs and date pickers |
| Sharing | The iOS share sheet | The Android share menu |
| Fonts | System font of the phone | System font of the phone |
| Safe areas | Notch and home bar at the screen edges | Status bar and gesture bar at the edges |
Two differences cause the most real problems. The first is the back action. On Android, users press back constantly, including from the middle of a payment flow. If your design has no clear answer for what back does there, users get lost. The second is system components. A date picker built by hand looks nice in Figma but feels wrong next to the native one that people use in every other app.
Can I use one design for both platforms?
Yes, for the flow, the content and the brand. Partly, for the components. One design for both platforms works when you separate what is shared from what is platform-specific.
Shared on both platforms:
- The screens and their order, such as signup, home, booking, payment, confirmation.
- The wording, labels and error messages. See UX writing and microcopy for apps.
- Colours, icons, illustration style and tone.
- The rules of your design system.
Different per platform:
- Back behaviour and the main navigation component.
- System pickers, permission pop-ups and share menus.
- Screen edges and safe areas.
- Spacing and touch target size on smaller or older phones.
Cross-platform tools let a team write one codebase for both. That is a development choice. As a designer, I still check each platform's rules, so the result does not feel foreign on either.
Choose Android first if, choose iOS first if
Choose Android first if:
- Your users are students, drivers, shopkeepers, farmers or customers in tier-2 and tier-3 cities.
- Your first users tell you they have Android phones.
- Your app must work on low memory and slow networks. See designing for low-end phones and slow networks.
- You plan to test with real users quickly and share a test build by link.
Choose iOS first if:
- Your first customers are mostly on iPhones, for example a premium service or an international audience.
- Your sales are to companies whose staff carry iPhones.
- You have a strong reason, like an investor demo on a specific device.
My recommendation for most Indian startups with consumer or small business users: design Android first, test on a mid-range phone and a small screen, then adapt for iOS. If you are unsure, ask first. Thirty phone calls give a better answer than any opinion.
How does this work on a real project? A worked example
Suppose the tour guide booking app in Siliguri has five main screens: search guides, guide profile, choose date, pay with UPI, booking confirmed.
Step 1. I design the flow once. The order of screens, the labels, the confirmation message and the brand stay the same.
Step 2. I design the Android version first. Bottom navigation with three items: Explore, Bookings, Profile. The date step uses the native Android date picker. The back button returns to the guide profile and keeps the chosen date.
Step 3. I check the awkward spots. The UPI step opens another app and then returns. If the user presses back during that, what do they see? A clear "Payment pending, check your UPI app" message is better than a blank screen. I covered this in UPI payment UX and checkout design.
Step 4. For iOS, I keep the same flow. I change the navigation to a bottom tab bar, add the left-edge swipe back, and use the iOS date picker. Most screens need small changes, not a redesign.
The result is two apps that feel right on each phone, with one set of decisions behind them.
What should I hand to developers for each platform?
Give developers the shared flow once, then a short list of platform rules. This keeps the work small and avoids arguments later.
A clean handoff has:
- One flow map and one set of screens.
- A page that lists, for each platform, the back behaviour, navigation component and system pickers.
- Components with states: normal, pressed, disabled, error.
- Notes on safe areas and small screens.
The Figma developer handoff checklist covers the file side of this. If your app also uses Bengali, Hindi or other languages, test long words on both platforms, as described in regional language app design in India.
If you are planning an app and want the platform rules sorted before development, you can see how I work on mobile app design.
Frequently asked questions
Do I have to design two separate apps for Android and iOS?
+
No. You design one flow and one brand, then adjust navigation, system pickers and screen edges for each platform. The adjustment is small compared with a full second design.
What is Material Design?
+
Material Design is the design guidance published by Google for Android apps. Apple publishes its own guidance, called the Human Interface Guidelines, for iPhone apps.
Can I launch on one platform and add the other later?
+
Yes, and many teams do. If you keep a clear flow map and a shared set of colours, icons and wording, adding the second platform is faster.
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.