Intermediate
Open
Pro
Redesigning a Flat 32-Option Settings Screen for Mobile
A desktop web app has a single settings page listing 32 individual toggles and fields in one long flat list — notification preferences, privacy controls, account details, display preferences, and billing info, all mixed together with no grouping, relying on the user scrolling and scanning to find what they need. You've been asked to adapt this screen for the company's new mobile app.
- Explain why porting this screen directly to mobile (same 32 options, same flat list, just narrower) is a worse problem on mobile than it already is on desktop, citing the relevant law.
- Propose a specific progressive-disclosure structure for these 32 options on mobile — name the actual groupings you'd use and how a user navigates between them.
- Give one example of a bad application of progressive disclosure to this same screen — over-applying the technique in a way that adds friction without a real space-saving benefit.
Share this question