Why Navigation Drawers Can Hurt Mobile App Engagement: An A/B Test Case Study

Imagine designing a multi‑page mobile app that cannot fit all content on a single screen. The first instinct is to add a bottom or top tab bar, but the extra row can look cluttered, so many teams consider moving navigation into a side‑drawer (the "navigation drawer" used on Android).

Usability vs. Clean Design

When the Zeekbox project started, the team used a top tab bar, believing that hidden navigation would be forgotten. Users who missed the hidden entry often could not find the drawer, and even when discovered, required extra taps to switch sections.

Removing the tab bar made the UI look cleaner and gave the main content more space, but the side‑drawer proved problematic. After Facebook and Google Play promoted drawer navigation, the team switched to it, initially expanding the drawer on first launch.

Early user feedback was positive, yet analytics showed a 50% drop in engagement, confirming the adage “what you don’t see, you don’t remember.”

Surprising Findings

Realising the impact, the team rolled back to top tabs within two weeks while keeping the drawer as an optional setting. Six months later, a new “My TV” page required more space, prompting another drawer trial, this time using a rigorous A/B test.

Favorite A/B Test Tools and Methods

The team created high‑fidelity clickable prototypes with Flinto, allowing rapid user testing on iPhone. They recruited TV‑show fans for weekly studio sessions and also ran large‑scale A/B tests using Swrve, which supports goal‑seeking automation and personalized experiences.

For the drawer test they applied a 15/85 split: 15% of users saw the drawer, 85% kept the tab layout. The results were striking.

The drawer caused weekly and daily usage frequency, as well as session time, to decline sharply. After confirming the disaster, the team switched all users back to tabs.

When Is a Side Navigation Appropriate?

If an app’s core features fit on a single screen and only secondary settings need separate pages, a side drawer can keep the main view clean. However, for apps with multiple peer‑level views that require equal attention, a drawer wastes potential interaction and reduces engagement.

In summary, the case study demonstrates that while navigation drawers are popular on Android, they can dramatically hurt user engagement in certain contexts, and thorough A/B testing is essential before committing to a navigation pattern.