-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Description
The Fade Forwards transition appears slower than native.
| Native Android Settings | Flutter |
|---|---|
![]() |
![]() |
However, the duration that we use is exactly correct according to the Android source code (800ms).
What's different is that native Android is using Material 3 Expressive springs, and Flutter is not. Even using a very long-tailed curve, Flutter seems way too slow.
Flutter's options are:
- Wait for a first party Flutter implementation of springs (I'm not sure if/when Flutter will have a spring implementation that could help here).
- Deal with the transition feeling slow (very soon it will be the default transition and lots of users will see it Predictive back route transitions by default #165832).
- Shorten the duration.
For now, I support number three.
As seen in #165832, it is quite painful to change the default page transition duration in Flutter. There were several customer test failures and Google test failures because of this. I even created TransitionDurationObserver to help with this.
In order to avoid multiple breakages, we should update this transition duration now as a part of #165832, so our users are only broken once by a changing page transition duration.
Discovered in: #154718 (comment)

