Settings Update
Started and led a redesign of Settings to improve scannability,
reduce redundancy, and make room for future features.
Problem
Bloated
Redundant
Lots of scanning
Saying the right thing at the wrong time
Would get worse when it grows in the future
Descriptions were hard to read due to:
Size
Poor contrast
Lack of value while scanning for features, not details
My role
Owned and initiated the project. Identified the issue, proposed the new structure, created Figma designs, and drove alignment with design leadership.
Goal
Make the Settings easier to scan
Reduce visual clutter and cognitive load
Prepare for future settings
Improve design consistency and support localization
Solution
I was involved in a similar update while working with Samsung years ago, so I already knew the solution would be similar:
Remove all descriptions or make them optional
Move some details to later in the flow when they’re more relevant and helpful
Improve clarity, value, and conciseness
See if feature names could absorb description info
However, I needed to make a strong case for it to ensure it would get accepted by the design leaders and shipped.
First, I kickstarted the presentation with a side-by-side comparison of other apps because I thought this would be a powerful motivator that would make people open to the proposal.
The last 2 screens showed the current and proposed version of Exodus. As a user, if I closed one crypto app and then opened Exodus, I would feel the instant bloat.
I had used the browser extension wallet in these examples because changes to our mobile app were more serious and risky. The browser extension had maybe 1% the number of users, so it would be easier to convince the team to change it first. But actually, the mobile app’s settings was even worse. It required lots of scrolling.
Plus, the mobile wallet also had a Security section, which was like a second list of settings.
Showed example of Twitter saying the right thing at wrong time.
It’s everything, all the time.
YouTube was a good example of how there is no description of Notifications in the main Settings screen. The details are only necessary inside of Notifications.
Airbnb was shown as another example of how descriptions can be optional on an as-needed basis.
As mentioned before, there are other settings screens, such as Security. And we have multiple platforms and products. This new style could be applied globally to our design system.
Case-by-case exceptions are OK.
What if the description is still needed for clarity? Show it in the next screen.
Or just keep them as they are.
Result
Design leaders agreed, and it went live
Lighter and less redundant
Easier to scan menus
Reduced translation costs, design upkeep, and broken UI issues
Makes Exodus feel easier to use
Related updates made later
I noticed I personally kept tapping Settings while looking for something that was in Security. So, I’d tap Settings, realize what I really wanted was in Security, then go back to open Security. I later suggested we merge Security and Settings into just one. Other team members agreed this is issue wasn’t only happening to me.
Settings in the mobile app got further updates to be even lighter. With Settings and Security merged and new features having been added, the list is still long, but it’s much easier to scan and all in one place.
First image: top of new Settings.
Second image: bottom half of new Settings.
Language screen
(Settings subproject)
As part of broader efforts to improve Settings, I later proposed a redesign of the language selection screen to make it faster to scan, more accessible, and culturally neutral. Self-started project again.
Note: Images in this subproject are taken directly from Asana and Figma.
Problems
Current screen used long 2-line labels with language codes, flags, and inconsistent translations
Flags were exclusionary and often irrelevant (e.g., for multilingual regions)
Selecting the current language unnecessarily restarted the app
Solution
Simplify to one line per language
Use translated language names instead of English-only labels
Remove flags to avoid cultural ambiguity
Alphabetize consistently, with non-Latin alphabets grouped separately
Optionally show a checkmark or message when selecting the already-active language
Result:
Created clear design options (A–D) to explore layout, translation, and accessibility trade-offs
Proposed a mobile-first version that improves scanability and reduces friction, especially for Spanish speakers using regional variants
Encouraged aligning UX with real-world user expectations seen in other major apps
It became neutral, inclusive, easy to scan, and correctly translated.
Plus, all the languages fit without scrolling.
Eventually the checkbox was also added so users didn’t feel the need to re-select their current selection (they can just tap the back arrow), which avoids them having their app restart.
