There will of course always be a (small) learning curve with a new UI/UX⌠one way is to show the new features / UI in a step-by-step âquick tourâ when first opening the new version of the app, e.g.:
Just wanted to note my admiration both for what youâve done with this (especially since I have no talent in that direction whatever, so it always seems a bit miraculous to me when someone else displays it), and the obvious time and care youâve taken.
Very nice work.
One way to get rid of that annoying space consuming side menu would be to make a drop down for each tabâŚ, I canât do a demo but I think it speaks for itselfâŚ
Regards
Phil
Thanks ![]()
Why not just implement a simple âswitchâ to hide/show the sidebar, like this one found on the AudirvÄna Community forum?

Brilliant!
Brillianto!
Why not just implement a simple link to the AudirvÄna âKnowledge baseâ in the current UI found here below?
Exactly.
And, a well designed system allows for an intuitive system. Left handers will adapt, as they always will. Scio, quia ego sum.
Phil
âPluralitas non est ponenda sine necessitateâ,
![]()
A âhamburger menuâ is generally not associated with a sidebar toggle, but with the navigation of a website/app, not something that is contextual, like in my mockups (the content of the sidebar is different every time)⌠The hamburger menu could be used though on the mobile app e.g. to show the music sources instead of the dropdown on the top left in my initial mobile mockups:
That link can always be implemented in the âHelpâ Menu or somewhere in the settings⌠I like the step-by-step quick tours on some apps that I use, because that way, you get the basic concept/UI of the new version of the app in a few steps⌠and, if you want info/help for all (new or more advanced) features, then you can open the Knowledge Base link of course.
Apparently, you have not used this âswitchâ to hide/show the sidebar in the Community forum display⌠It is not a hamburger menu, it is a simple switch⌠However the graphic is a familiar convention⌠The switch graphic could be more indicative of its functionâŚ![]()
Apparently, you have not really looked at the âstep by stepâ functionality of the Knowledge base⌠and if implemented contextually, it is a simple application of something that does not need to be invented because it already exists and available to all levels of users. ![]()
At least your lover knows youâll never care to look at another piece of fill in the blanks ![]()
Iâd be interested in granular search/sort* approach with quick multi-parameters-selection, which of course would also need some UI changes.
- Much like an online shop



