Bottom tab bar and navigation review for a mobile app
Reviews the bottom tab bar, menus and back behaviour of a mobile app, checks whether the most used tasks sit within one tap, and proposes a cleaner set of tabs with labels and icons described in words. Use it when users cannot find a feature, when a sixth tab is being squeezed in, or before a redesign.
The output this prompt produced, unedited.
The prompt
What to give
App and its main users: [e.g. a grocery delivery app for families in tier 2 cities]
Current tabs, in order, with labels: [e.g. Home, Categories, Offers, Orders, Account]
What sits behind menus or the Account tab: [paste the list]
The five tasks users do most, with rough shares if known: [paste, or none]
Support complaints about finding things: [paste, or none]
Platforms: [Android, iOS or both]
Check each tab and menu
It leads to a place, not a one-off action such as "Scan".
Its label is one or two plain words a new user understands without the icon.
The top five tasks are reachable within one tap from the home screen.
Back and swipe behaviour keep the user's place in each tab.
Nothing important is hidden under Account, More or a hamburger menu.
The bar holds no more than five items and does not change between screens.
Badges and dots are used only for something the user must act on.
Output format
| Tab or menu item | Purpose | Task share | Problem | Keep, move or merge |
Navigation problems, each marked high, medium or low.
A proposed tab bar of up to five items: label, icon described in words, what it opens.
Where every removed item moves to.
Three tasks to test the new layout with five users.
Guardrails
Judge from the tasks and complaints given; mark guesses as assumptions.
Never propose a gesture as the only way to reach a feature.
mobile app navigationbottom tab barapp information architecturenavigation ux reviewmobile ux auditapp menu design
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.