How to Structure Mobile App Menu to Improve Discoverability

People leave apps when they can't find what they're looking for. It's that simple.

Card sorting helps you figure out how your users actually think about your app's features, so you can build a menu that matches their expectations instead of your internal org chart. You run a few sorting sessions with real users, look at the patterns, and build a navigation structure based on what you find. The result is a menu people can navigate without thinking too hard, and fewer costly redesigns after launch.

Difficulty: Intermediate Time Required: 4-6 hours (including participant testing)

What You'll Need

Before you start, gather these materials:

• 20-40 app features or functions to organize
• 8-10 participants from your target user base
• Sticky notes or index cards (for offline sorting)
• A CardSort account (for online testing)
• Spreadsheet software for analyzing results
• A wireframing tool like Figma or Sketch

Step 1: Inventory Your App's Functions

You need a complete list of everything your app does before you can organize any of it. Miss something here and you'll end up bolting it on later in some awkward spot that nobody checks.

Time: 45-60 minutes

Go through your app and write down every single thing a user can do:

• Every screen, feature, and action
• Administrative stuff like settings and profile management
• Give each feature a clear, unique name and a short description

Example: For a fitness app, your inventory might include: Workout Plans, Progress Tracking, Nutrition Calculator, Exercise Library, Social Sharing, User Profile, Settings, Notifications, Premium Features, and Help Center.

Don't rush this step. An incomplete inventory means you'll be reworking your menu after launch, and that's never fun.

Step 2: Prepare Your Card Sort

How you write your cards matters more than you'd think. If labels are too long or confusing, participants spend their mental energy reading instead of sorting. Keep things tight.

Time: 30-45 minutes

• Write each function on a separate card or sticky note for physical sorting
• For online sorting, create a new project in CardSort and add each function as its own card
• Stick to 2-5 words per label
• Add a brief description for anything that might be unclear

Example: Card label: "Progress Charts" with description: "View weight, measurements, and workout performance over time."

Run through your cards once before testing. If you have to re-read a label to understand it, rewrite it.

Step 3: Recruit and Brief Participants

This is where a lot of teams cut corners, and it shows. If you recruit the wrong people, your menu will be structured around the wrong mental model. You want 8-10 people who actually resemble your target users. Not your coworkers. Not your mom.

Time: 30-60 minutes (plus waiting time)

• Pull participants from your existing user base, social media communities, or user testing platforms
• Give them clear instructions about what card sorting is and what you need from them
• If you're using CardSort, write out your instructions inside the platform
• For in-person sessions, prepare a simple script so every participant gets the same briefing

Example instruction: "Group these features into categories that make sense to you. Create as many or as few groups as you like, and name each one. There are no right or wrong answers -- we just want to see how you'd naturally organize these."

Eight to ten participants is the sweet spot for this kind of study. You'll see clear patterns emerge without needing a massive sample size.

Step 4: Conduct Open Card Sorting

In an open card sort, participants create their own categories from scratch. This is where the real insights come from. You're not testing whether your proposed structure works -- you're discovering how people naturally think about your app's features.

Time: 1-2 hours

• Give each participant 20-30 minutes for in-person sessions
• Set a reasonable deadline for remote sessions in CardSort
• Ask participants to name every group they create
• If you're in the room, encourage them to think out loud
• Take notes on patterns as they emerge

Example: Fitness app participants tend to create groups like "Workout Tools," "My Progress," "Social Features," and "Account Settings." Those groupings tell you something real about how people think.

Pay attention to where people hesitate or change their minds. Those moments often reveal the trickiest navigation decisions you'll face.

Step 5: Analyze Results and Identify Patterns

Now you dig into the data. The goal is to find where your participants agree and, just as importantly, where they don't.

Time: 1-2 hours

• Use CardSort's built-in analysis tools or build a similarity matrix by hand
• Look for functions that 70% or more of participants grouped together -- those are strong signals
• Write down the core categories that showed up across multiple participants
• Flag outliers and items that landed in different groups for different people
• Note which category names participants gravitated toward

Example: If 8 out of 10 participants put "Workout History" and "Progress Photos" in the same group, those items should live together in your final menu. That's not a coincidence -- it's a genuine pattern in how people think about your app.

Items with inconsistent placement are worth the most discussion. They often need clearer labeling or might belong in multiple places.

Step 6: Design Your Menu Structure

Here's where card sort data meets the realities of a small screen. Mobile navigation has hard constraints that desktop doesn't -- limited space, one-handed use, thumb reach zones. You have to respect those limits.

Time: 1-2 hours

• Cap your top-level categories at 5-7 items. More than that and people start struggling
• Write clear, short labels for each category
• Put the most-used actions where thumbs can easily reach them
• Consider a hybrid approach: bottom navigation for primary tasks, hamburger menu for the rest
• Create wireframes showing the full menu structure and how users move through it

Example: Based on your card sort results, your bottom navigation might be Home, Workouts, Progress, and Community. Settings and admin functions go in a hamburger menu since people access them less often.

Resist the urge to cram everything into your primary navigation. The whole point of this process is to prioritize.

Step 7: Validate With Reverse Card Sort

You've built a menu structure. Now test it before writing any code.

A reverse (or closed) card sort flips the process: you give participants your proposed categories and ask them to sort functions into them. If they can't figure out where things go, you have a problem worth fixing now rather than after launch.

Time: 1 hour

• Set up a new card sort with your proposed categories already defined
• Use the same feature list from your original sort
• Ask participants to place each item into the category where they'd expect to find it
• Watch for items that consistently end up somewhere you didn't intend
• Document every mismatch -- these are your revision targets

Example: If users keep putting "Notification Settings" under "Profile" instead of "Settings," that's worth paying attention to. Either move it, or rethink your category labels.

Catching these issues now saves you from a navigation overhaul down the road.

Tips and Best Practices

Mobile-specific considerations:

• Be ruthless about what goes in primary navigation. Screen space is precious
• Pair icons with text for main navigation items -- recognition beats recall
• Design for one-handed use and keep critical actions within thumb reach
• Group related tasks that people typically do back-to-back

Card sort optimization:

• Run a quick pilot test with 1-2 people first to catch confusing labels or instructions
• Include a "doesn't fit anywhere" option for outlier functions
• Keep your sort under 30-40 items to avoid participant fatigue
• Combine card sorting with task analysis for a fuller picture of your navigation needs

Common Mistakes to Avoid

Creating too many top-level categories. Once you go past 7 primary items, people start scanning aimlessly and give up faster.

Organizing by company structure. Your users don't know or care about your internal departments. Menu labels like "Platform Services" mean nothing to them.

Using ambiguous labels. "More" and "Other" are where features go to die. Be specific.

Burying frequently used features. If people use it daily, it needs to be front and center. Don't hide it two taps deep.

Skipping validation. Running an open card sort without a follow-up closed sort means you're shipping a guess. Always validate before development.

Next Steps and Further Reading

• What is Card Sorting? Complete Guide
• Navigation (UX Glossary)
• Information Architecture (UX Glossary)
• How To Organize Website Navigation For Better User Experience

Once your new menu is live, run usability tests with specific tasks to see how it performs in practice. Set up analytics to track where people get stuck, and plan to revisit your structure as you add features or notice completion rates dropping.

Further resources:

• Nielsen Norman Group's mobile navigation patterns research
• Baymard Institute's mobile navigation best practices
• CardSort's analysis methodology guide

Frequently Asked Questions

How many participants provide statistically significant card sorting results for mobile apps? You generally get solid, reliable results with 8-10 participants drawn from your actual target audience. Beyond 10, you'll see fewer and fewer new patterns. It's better to recruit the right people than to recruit a lot of people.

What's the difference between open and closed card sorting for mobile app navigation? Open sorting lets participants make up their own categories, which shows you how they naturally think about your features. Closed sorting hands them your proposed categories and asks them to sort into those. Use open sorting first to discover patterns, then closed sorting to validate your design. They work best as a pair.

How often should mobile app menus be restructured based on usage data? Don't overhaul your navigation on a whim -- major changes disorient returning users. Save full restructuring for big moments, like when you've added a significant batch of new features or your analytics clearly show people struggling to complete key tasks. Smaller tweaks based on usage data can happen quarterly.

Can card sorting methodology work for apps with highly technical or specialized functions? Absolutely, but you need to recruit from your actual user base. If your app is for radiologists or network engineers, test with radiologists or network engineers. Non-expert participants will create structures that don't reflect how real users think, because they don't understand the terminology or workflows.

What mobile-specific constraints affect card sorting results compared to desktop navigation? Mobile has unique physical constraints that desktop doesn't: thumb-reach zones, one-handed usage, and much less screen real estate. These realities mean you need to be stricter about limiting top-level navigation to around 5-7 categories and placing frequently-used functions in the bottom third of the screen, where thumbs can reach them comfortably.