Organize menus and where each function is accessed from - About Page, Burger Menu, Settings

[oleg-rswll]

Problem Statement
Currently the menus contain a mix of features without any particular logic. There is no definition for what goes into this one menu vs another menu, it appears like a random mix of features.

Without any particular organization logic, a person would not be able to intuitively easily find particular features, they would need to look in all the places and over time learn where they are located. This is time consuming not a great experience.

Reducing the learning curve for the app would improve the experience and increase satisfaction with the app.

Criteria

Definition for the type of functions go into each menu

• Main page / map: primary features which are used the most often and relating to the core functionality of the app.
  - Add a plus button for adding a place to OpenStreetMap. This makes it easier to add places, and encourages people to contribute more often.

• About Page: related to the company and how to interact with the company.

• Burger Menu: secondary features, which are second in priority after the primary features on the main menu and map.
  - Remove the map layer options - they are already located on the main map and that is a good place for them, no need to duplicate features.
  - In place of where the map layers were, move features from the list and create icons for the following features: Add Place to OpenStreetMap, Record Track, Share My Location, Download. In the vertical list leave: Settings, Donate, OpenStreetMap Account.
  - Move OpenStreet Account from Setting to Burger menu vertical list. Connecting an account is not a setting, but an account synchronization, which is a more significant function than a settings change (also, the Burger menu is a good place to have an OM account, if one is ever added in the future).

• Settings: configurations and tuning of features, not activation of features.
  - Move OpenStreetProfile from Setting to Burger menu vertical list.

Maps.Me design of the menu appears intuitive and well arranged.
https://www.figma.com/design/EXZNQgYd09am8DzFSXF82Q/OM-Track-Recorder?node-id=7%3A109&t=AfLkUGeDDVoMHQJT-1

[biodranik]

@oleg-PK in the context of #1577 , there was an idea to change the interface for the current activity type, e.g. driving, public transport, cycling, hiking, city tourism, skiing, etc. Does it make sense to plan app interface changes with that in mind? In this case, for example, choosing/switching a "layer"/activity style may become the main button.

Some buttons like start recording may also be needed on the map screen. Yet another idea is to allow users to customize buttons (someone proposed to make it a premium feature to sponsor development 😄 ).

Did you check how an interface is organized in other apps/maps? Is copying some existing interface the best approach that what we can do?

[oleg-rswll]

Of course when designing these menus, the broader UI perspective needs to be considered and how features will interact with other features. When work starts on several issues which are close in interaction, at that time it would be a good idea to revisit them together in a single design instead of in isolation.

There are many navigation apps and it’s a good idea to get inspiration from them and how they address certain designs. The OM main menu is very poorly done, the features are not really related in a meaningful way, some don’t even belong there. We can organize it better, and that may make it similar to another navigation app. Or we can completely redesign it. It may not make sense to change the look just to make it different, but if a new design is actually more intuitive and doesn’t require reading anything to use it, that can be a good option. The thing to keep in mind is that there are only a certain number of arrangements for a UI, there is a decent chance that a redesign will look similar to another navigation app.