maxrave-dev / maxrave-dev/SimpMusic

Improve high refresh rate support (90Hz / 120Hz optimization)

Open
#2,086 0 comments 0 reactions 0 assignees View on GitHub

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 UI animations and transitions do not feel fully optimized for high refresh rate displays.

On devices with 90Hz or 120Hz screens, the interface can still feel slightly inconsistent or less smooth than expected.

Proposed Solution

Improve support for high refresh rate displays by optimizing animations, scrolling, and transitions across the application.

This could include:

  • Smoother screen transitions
  • More consistent animation frame rates
  • Better scrolling fluidity
  • Overall optimization for 90Hz and 120Hz displays

The goal is to fully utilize modern display capabilities and make the UI feel more responsive and fluid.

Alternative Solutions

If full high refresh rate optimization is not possible globally, it could be improved gradually:

  • Prioritize key UI areas such as player screen and navigation
  • Optimize only main animations and transitions
  • Add optional performance / smoothness settings in the future
Additional Context

This improvement would significantly enhance the overall user experience, especially when combined with modern UI effects like blur and glass animations.

At the moment, the interface sometimes feels less fluid than other modern media applications on high refresh rate devices.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Start by locating the UI animation, transition, scrolling, and player-screen code, then measure behavior on 90Hz and 120Hz devices. Done means the prioritized UI areas feel consistently smooth at those refresh rates, with the scope and validation criteria agreed before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, performance
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.