What should a mobile app designer know before you hire one?
A mobile app designer decides how an app behaves in a hand, on a train, with one bar of signal. Screen size is the smaller half of that job. The larger half is knowing what each platform expects and where an app can safely depart from it. iOS users expect the navigation and gestures described in Apple’s Human Interface Guidelines. Android users expect Material 3 patterns, including adaptive layouts and system back behaviour.
If your product ships on both, the designer must decide which patterns to share and which to keep native. Forcing one look onto both platforms is the most common reason a cross-platform app feels slightly wrong everywhere.
What we vet for
We screen mobile designers on shipped apps and ask them to walk through trade-offs. We look for:
- Platform fluency. Tab bars versus bottom navigation, sheets, swipe actions, dynamic type and system fonts. A designer who can name where iOS and Android differ saves weeks of engineering rework.
- Gestures and touch. Reachability on large phones, thumb zones, swipe conflicts with the system back gesture, and minimum tap targets.
- Offline and poor-network states. What the user sees with no signal, with stale data, during sync and after a failed upload. These screens are rarely in a mockup unless the designer insists on them.
- Permissions and onboarding. When to ask for notifications, location or camera, and what the app shows if the user says no.
- Accessibility. VoiceOver and TalkBack labels, contrast, large text settings and reduced motion.
- App store assets. Icons, screenshots, preview videos and listing copy that match store guidelines. Store pages convert installs, so they belong to design.
- Handoff. Named tokens, component variants, spacing rules and motion specs that a React Native or native team can implement without a meeting for each screen.
What does the first month look like?
The first tasks depend on whether the app exists. For a new product, the designer maps the core journey, defines a small component set and prototypes the main flow on both platforms. For a live app, the work starts with an audit: crash-adjacent flows, drop-off screens, accessibility gaps and inconsistencies between the iOS and Android builds.
From there the designer sets up the shared library in Figma, agrees the handoff format with your engineers and takes over store listing updates. If you build with React Native, we pair the designer with engineers from our React Native development team so components are designed for how they will be built. Teams going fully native can work with our iOS development and Flutter development engineers instead.
Proof from a mobile build
An APAC seed travel startup needed an iOS and Android app within two months and had no engineers. We ran a two-week design sprint before any code, aligning the screens with the concierge workflow the founders already knew, then built one React Native codebase. Search results were cached locally so travellers could browse itineraries in low-connectivity areas. The app reached both stores in eight weeks. See the cross-platform MVP case study.
How do you engage a mobile app designer?
| Model | Fits when | What you get |
|---|---|---|
| Dedicated designer | A mobile product with a continuing roadmap | One designer in your sprints and tools |
| Team extension | Your designers lack mobile depth | A specialist added to the existing team |
| Project | An MVP design, an audit or a redesign | Defined screens, library and handoff |
Rates sit in the “$50 to $150 per hour” range and depend on seniority. We explain the contract options on the IT staff augmentation page, and if you want a designer and engineers together, hire a dedicated team. A designer starts after a short intro call and your interview. For the broader service, see mobile app development and our other designer roles.
