Devolutions / Devolutions/UniGetUI
[IMPROVEMENT] Adopting Non-linear Slide-In Animations Across the UI
- Dominant language
- C#
- Stars
- 26.1k
- Forks
- 924
- Avg merge
- 15h 52m
- Merged PRs (30d)
- 52
Description
### Please confirm these before moving forward.
- [x] I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- [x] This improvement refers to an existing feature. If you want to suggest a new feature, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=new-feature&projects=&template=feature-request.yml&title=%5BFEATURE+REQUEST%5D+%28Enter+your+description+here%29).
- [x] This improvement is not a bug. If you want to report a bug, please use [this template](https://github.com/Devolutions/UniGetUI/issues/new?labels=bug&projects=&template=bug-issue.yml&title=%5BBUG%5D+%28Enter+your+description+here%29).
### Describe the improvement
https://github.com/user-attachments/assets/4ffa9ec7-c986-4066-bb36-2d9206d8bce2
The current UI uses linear slide-in animations across the board, which can look a bit dated when compared to modern fluent design principles.
Non-linear example:
https://github.com/user-attachments/assets/e138b588-00fd-40c4-814f-71917c7402fa
### Describe how this improvement could help users
\
Contributor guide
Research direction
No files, tests, or entry points are named. Start by locating the UI entry points responsible for the current linear slide-in animations and compare them with the linked non-linear examples. Done means the applicable UI slide-ins use an agreed non-linear behavior consistently across the defined scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100