At the moment, Commet doesn't seem to have an option to adjust or disable animations, as such I'd suggest implementing a slider to adjust or disable animations.
For some people animations can feel frustrating if they're perceived as too slow. For others, they can be an accessibility issue.
I think by default that Flutter respects an operating systems PreferReducedAnimations-esque setting, but not all systems have this setting, and I think an explicit setting within the app would be more useful. It would fit neatly under the Application/Text scaling section in the Appearance setting, and I think would be a valuable addition to the application.
Now, flutter seems to have a built in property for this in the scheduler, timeDilation (see https://api.flutter.dev/flutter/scheduler/timeDilation.html), but from the cursory research I've done (primarily being a .NET dev) it seems like this is more of a debug tool, but it could potentially be a quick and easy way of implementing it as it affects all animations in the application.
Should this feature be aligned with the applications ideals, would that be an okay way to go implementation wise, or should we make bigger changes to the application structure and apply the animation speed value on a more granular basis?
At the moment, Commet doesn't seem to have an option to adjust or disable animations, as such I'd suggest implementing a slider to adjust or disable animations.
For some people animations can feel frustrating if they're perceived as too slow. For others, they can be an accessibility issue.
I think by default that Flutter respects an operating systems PreferReducedAnimations-esque setting, but not all systems have this setting, and I think an explicit setting within the app would be more useful. It would fit neatly under the Application/Text scaling section in the Appearance setting, and I think would be a valuable addition to the application.
Now, flutter seems to have a built in property for this in the scheduler, timeDilation (see https://api.flutter.dev/flutter/scheduler/timeDilation.html), but from the cursory research I've done (primarily being a .NET dev) it seems like this is more of a debug tool, but it could potentially be a quick and easy way of implementing it as it affects all animations in the application.
Should this feature be aligned with the applications ideals, would that be an okay way to go implementation wise, or should we make bigger changes to the application structure and apply the animation speed value on a more granular basis?