New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The Bottom Menu is a bit strange #1
Comments
Thanks, Demola. Where would you suggest the menu be? Jam isn't available as a feature yet, so it should probably be taken away. Yep, I like express-ws cos its abstraction fits into express' pipeline smoothly |
The Menu could be on top or may be fixed to the bottom. The latter may not play well with the Piano. Besides, the current position seems to be the best option for the Piano 😅 |
How about indicators that point users to the bottom when they first load the app? |
@mykeels Yeah. That's awesome 🔥 🔥 🔥 |
Here's what the bottom menu should look like
Still no updates on the indicator that tells users about the menu at the bottom. I don't even know what it's normally called 😄Maybe make a separate issue for that, if it's necessary? |
Yeah. LGTM! |
Great job on this, @mykeels! Just checked out the app and I was quite confused too about which button was active. I'm in support of this implementation though – easy to understand. @ooade, an indicator is an indicator, no special term for that. I'm not sure though; what kind of indicator are y'all talking about? |
@whizkydee Indicator, like an arrow pointing down immediately the component get rendered to let the user know there's a menu bar below. |
Oh yeah, totally. Actually, the menu should be at the top. It's much more accessible there. I also think you can reduce the height of the menu and strip off the additional I think we can forget about the indicator once this is done. Good luck! |
BTW, Nice project. I got to know about
express-ws
. Dived into that 😸The text was updated successfully, but these errors were encountered: