maxrave-dev / maxrave-dev/SimpMusic
Improve and complete Liquid Glass implementation on Android
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 current Liquid Glass implementation feels incomplete and inconsistent across the application.
While the feature is available as a beta toggle, it is only partially applied to the interface. Some screens and components use the glass effect, while others remain in the standard design style.
This creates a fragmented visual experience where the UI does not feel like a unified design system.
In addition, there are missing smooth transitions and animations between elements, which reduces the overall fluidity expected from a Liquid Glass-style interface.
As a result, enabling Liquid Glass currently feels more like activating a visual experiment rather than switching to a complete and polished UI theme.
Proposed Solution
I would like to suggest improving and expanding the current Liquid Glass implementation on Android.
At the moment, the effect feels partially implemented and is only applied to certain parts of the interface.
Suggested improvements:
- Apply Liquid Glass styling to more screens and UI components.
- Create a more consistent visual experience throughout the app.
- Improve the integration of the bottom navigation bar.
- Improve the integration of the mini-player.
- Add smoother transitions and animations between interface states.
- Make Liquid Glass feel like a complete design language rather than a collection of separate visual effects.
The current toggle should remain available so users can choose whether to enable or disable Liquid Glass.
Alternative Solutions
If a full implementation across the entire application is too complex or could impact performance, some alternative approaches could be:
- Gradually expand Liquid Glass support to additional screens and components.
- Add separate customization options for specific UI elements.
- Focus on improving animations and visual consistency within the current implementation.
- Keep the current scope but further polish the existing design before removing the Beta label.
Additional Context
The current Liquid Glass mode feels visually inconsistent because different parts of the application use different design styles.
Some elements support the glass effect while others continue to use the standard Material Design appearance.
There is also a lack of smooth visual transitions between interface elements, which makes the experience feel less fluid than expected from a Liquid Glass design.
Because of this, the feature currently feels more like an experimental visual effect than a fully realized design system.
My goal is not to make Liquid Glass mandatory for all users, but to improve the existing implementation so it feels more complete, polished, and consistent throughout the application.
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
Start by locating the current Liquid Glass beta toggle and the existing Android screens and components where the effect is applied. Review the bottom navigation bar and mini-player integration first, then define a bounded set of screens, components, transitions, and animations whose appearance can be verified while keeping the toggle behavior unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- design, mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100