This guide is for product owners and founders who specify or accept a mobile app. It sits in the product design cluster of our product engineering service, next to the guides on prototype fidelity and usability testing without a research team.
In this guide
- Why judge a mobile pattern by its failure case?
- Which navigation model fits a mobile app?
- When should a gesture be the only way to do something?
- What should a screen show when the network is slow or gone?
- Which pattern fits which situation?
- How to review navigation, gestures and offline states before release
- Where AI fits
- What delivery record exists, and what does not
- Alternatives: other ways to settle a pattern question
- Limits of this guide
- Frequently asked questions
- Next step
Why judge a mobile pattern by its failure case?
Most pattern advice describes the happy path: a user who knows the app and has a fast connection. Real sessions are short, one-handed and often happen where the signal drops. A pattern that looks clean in a design review can still hide the main navigation, swallow a swipe meant for the system, or show a spinner where the user needed yesterday's data.
Judging by the failure case changes the review question to "what does the user see and do when this pattern goes wrong?" That question has a concrete answer for every screen and can be tested on a real device before sign-off.
Which navigation model fits a mobile app?
The navigation choice depends mostly on how many top-level areas the app has and how often users switch between them.
A tab bar suits apps with a small number of top-level areas that users move between often. Apple's Human Interface Guidelines say to use a tab bar for navigation, not for actions, and to keep it visible when people move between sections, because people who lose the bar can forget which area of the app they are in. The failure case is overloading: a sixth or seventh tab, a tab that opens a form, or a tab bar hidden on scroll that users never find again.
A navigation drawer behind a menu icon holds many destinations, but it hides them. In a Nielsen Norman Group study of mobile navigation, sites with visible or combined navigation saw navigation used more often and found sooner than a site whose menu sat behind a small, low-contrast icon. The failure case is a feature that nobody uses because nobody finds it.
Stack-only navigation suits task flows such as checkout or a field inspection. It fails when users must go back several levels to reach another area, or when a deep link opens a screen with no sensible parent.
When should a gesture be the only way to do something?
Almost never. Apple's guidelines say a custom gesture should not be the only way to perform an important action, should avoid conflicting with gestures that open system UI, and should be added only when necessary. Gestures are shortcuts: swipe to archive works well when the same action also sits in a visible menu or on the detail screen.
Four gesture failures recur in mobile reviews:
- Hidden-only actions. A swipe or long press with no visible equivalent is invisible to new users and to anyone using a screen reader or switch control.
- System conflicts. Since Android 10, the system back gesture is an inward swipe from the left or right edge, and the Android developer guidance on gesture navigation tells apps to handle conflicting gestures; apps cannot opt out of the home and quick-switch gestures at the bottom edge. A carousel or drawer that starts at the edge competes with the system.
- Destructive swipes without undo. A delete on swipe needs either a confirmation or an undo window, because an accidental swipe while scrolling is common.
- Drag-only controls. WCAG 2.2 success criterion 2.5.7, Dragging Movements, asks that any function done by dragging also works with a single pointer without dragging, such as reorder buttons next to a draggable list.
What should a screen show when the network is slow or gone?
Offline is not one state. A screen can be in at least five conditions, and each needs its own design: fresh data, cached data that may be out of date, a change the user made that is queued, a change that failed to send, and content that was never loaded. Many apps design only the first.
The failure cases are predictable. A spinner with no time limit leaves the user guessing; an empty list that is really "not loaded yet" reads as "you have no orders"; a form that loses its input when the request fails teaches users to stop trusting the app. The fix is to label stale data with its age, mark queued changes as pending, keep failed input with a retry control, and tell the user which features still work without a connection.
What the app can do offline is also an architecture decision. Our guide to mobile backends, APIs and offline sync covers the sync models and conflict rules behind these states; this page covers what the user sees.
Which pattern fits which situation?
| Pattern | Choose it when | Typical failure case | Check before release |
|---|---|---|---|
| Tab bar | A few top-level areas that users switch between often | Too many tabs, tabs used as actions, bar hidden on scroll | Every top-level area is reachable in one tap from any tab |
| Navigation drawer | Many secondary destinations, few used daily | Main features never found | The most used area is not inside the drawer |
| Stack-only flow | One task from start to finish | No way to another area; deep link lands with no parent | System back and deep links return to a sensible screen |
| Gesture shortcut | A frequent action that also has a visible control | Hidden action, edge conflict, accidental destructive swipe | The action works without the gesture and can be undone |
| Offline state ladder | Users work on weak or no network | Endless spinner, false empty state, lost input | Each of the five network conditions has a designed screen |
How to review navigation, gestures and offline states before release
-
List the top-level areas and count the taps
Map every primary destination and check it is reachable from the main navigation without going back through several screens.
-
Test the system back on both platforms
On Android, test with gesture navigation and with three-button navigation; on iOS, test the edge swipe on every pushed screen and every modal.
-
Find every gesture and its visible twin
For each swipe, long press or drag, name the button or menu item that does the same thing, and the undo for destructive actions.
-
Run the app with no network and with a slow one
Use the device's flight mode and a throttled connection, and walk every main screen through the five network conditions.
-
Hand the build to someone who has not seen it
Ask them to complete two or three core tasks without hints; a short round, as described in the usability testing guide, shows whether gestures and hidden menus are found.
-
Record each failure with the screen and the condition
Fix the ones that block a core task first; the rest go into the backlog with the evidence attached.
Where AI fits
AI tools help where the review is tedious: listing every screen and network condition that needs a design, drafting state copy and turning review notes into tickets. A designer still decides what each state says and a tester still checks each one on real devices, because generated copy can promise behaviour the app does not have. Netbase works with the major commercial and open-source AI tools and models, chosen per project, under human control.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online printing store; it is not a mobile review tool.
- Available capability
Screen-state inventory and state copy drafting
State lists and draft copy reviewed by designers and testers; not yet tied to a published case.
What delivery record exists, and what does not
The registered record is about building mobile apps, not about measuring pattern choices. For RB Marketplace, Netbase built the customer shopping app on the marketplace API, an Android app with iOS in the extended scope, including offline browsing, dark mode and push notifications; the RB Marketplace work record lists the scope. For Dey Page, a business directory, Netbase built a React Native app for iOS and Android with consumer and business-owner modes and deep links, and the field verification behind its Location-Confirmed Badge includes offline sync.
Netbase delivery teams combine business analysts, project managers, solution architects, developers, QA and UI/UX designers, and discovery is the first step of the delivery lifecycle, which is where navigation and offline scope are set. Most Netbase projects are delivered on fixed-price contracts, and the client owns the IP created for it in custom development.
What does not exist: Netbase publishes no usability metric, task-success rate, gesture analytics or before-and-after result for these apps, and this guide claims none.
Alternatives: other ways to settle a pattern question
- Follow the platform defaults. Use the standard tab bar, back behaviour and system components unchanged; choose this when the app is mostly content and forms, and accept a less distinctive interface.
- Test a clickable prototype first. Put two navigation models in front of five users before building; choose this when the team disagrees and the screens are not built yet.
- Commission a build with the review included. Ask the delivery team to run the six review steps as part of acceptance; choose this when the app has offline or field use and no in-house design lead. Our UI/UX design service and mobile app development service describe that route.
Limits of this guide
- It covers phone apps; tablets, foldables and wearables need their own review.
- Platform guidance changes with each operating system release; check the current documentation.
- It does not replace an accessibility audit.
Plan the next step with a Netbase consultant
Frequently asked questions
Use a tab bar when the app has a few top-level areas that people switch between often, and keep it visible. A hamburger menu suits secondary destinations, but hiding the main areas behind it makes them harder to find, so the most used area should never live only in the menu.
Swipe gestures are useful shortcuts when the same action also has a visible control and a destructive swipe can be undone. They become a problem when they are the only way to do something, when they start at a screen edge that the system uses for back, or when they replace a button that screen-reader users need.
It should show cached content labelled with its age, mark changes the user made as pending, keep any input that failed to send with a retry control, and say which features work without a connection. An endless spinner or an empty list that really means "not loaded" are the two failures to avoid.
Next step
If you are specifying or accepting a mobile app and want its navigation, gestures and offline states reviewed before release, tell us about the app and its users and we will reply with a proposal for the review and the build.
Related services and solutions
AI-enabled software product engineering from discovery to operation Netbase provides software product engineering for companies that need a web, SaaS, mobile or custom platform built and kept running, with AI features and AI-assisted engineering where they pay off. We cover the full lifecycle, from discovery to operation, and the same team stays accountable for architecture, delivery and handover, so nothing important gets lost between phases.
Learn More
Mobile app development with AI features for commerce and product teams Netbase provides mobile app development for retailers, startups and product teams to reach customers on the phone they already use: cross-platform React Native apps and mobile-optimized commerce that loads fast, converts and uses AI where the phone makes it useful. We scope each app in discovery, reuse your existing backend and APIs, and plan the store release with you.
Learn More
UI/UX design services: research, interfaces and design systems built in code Netbase designs the interfaces of web apps, SaaS products, mobile apps and online stores: user research, flows, wireframes, clickable prototypes and visual design, plus a design system shared by designers and developers. Because UI/UX designers sit inside the delivery team, the same people who design a screen see it built, tested and released.
Learn More
Mobile product accelerator for AI-ready apps: reusable foundations for auth, push, offline and payments A mobile app accelerator is a set of reusable app foundations, covering sign-in, push notifications, offline data and payments, that Netbase configures for each new product, so the build starts on what makes your app different, such as AI search, personalisation or on-device AI. It is a growth capability, delivered as custom development with cross-platform React Native skills.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.