maxrave-dev / maxrave-dev/SimpMusic
[Feature request]: Improvement of the bottom navigation bar.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 11.4k
- Forks
- 599
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 7
Description
Problem Description
The new bottom navigation bar introduced in version 2.0.0 looks cluttered. Too many categories in one place, what makes it feel less fluid. Also the new transparency option combined with the new permanent floating navigation bar feels cheaper than the one we had before.
Proposed Solution
Adding a new system to change the navigation bar. First of all, you would be able to choose if you want it to be floating or not. The floating one would have the seach button separate from the other tabs, meanwhile the non-floating navbar would have it as a proper navigation tab. Then, you could choose if you want it to be opaque, transparent or with the Liquid Glass design (this last one would only be available with the floating navbar option turned on). Lastly, to make it so everyone can customize it as they like, a menu to show, hide or rearrange navigation tabs, so you could have a navigation bar with the things you use in the order that suits better to you.
Alternative Solutions
Revert back to the previous option, but this would make the app less customizable and wouldn't be suitable for everyone.
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the current bottom navigation bar implementation and reviewing the version 2.0.0 behavior described here. Done would require an agreed design and working support for floating or non-floating layouts, appearance choices, and customizable tab visibility and ordering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100