Menu-hierarchy design for settings on mobile

[taoeffect]

Problem

The conventional way of doing settings on mobile is to use a hierarchy of menus, and this works really well. The way we're doing it right now however is instead of using a menu hierarchy, we're putting the content of all of the settings (the values at the end of the menu hierarchy), all on a single settings page. This gives a somewhat cluttered and disorganized look on mobile.

Solution

• Create a mobile-first design for the settings using the menu-hierarchy approach.
• Afterward, create appropriate issues to implement components for this

NOTE: this isn't a high priority for the prototype, but would be nice at some point, and should be relatively simple to design. For this reason, I'm making this as low-priority for now.

[mmbotelho]

We are using this approach on the user settings, right @taoeffect ? Or are you talking about something else?

[mmbotelho]

Quick summary of what we discussed in the hackathon:

The first navigation level should look more compact and have the sections clearly separated (e.g.: Discord, iOs native settings)

cc @taoeffect