Open Bug 1814126 Opened 2 years ago Updated 2 years ago

Add Motion Transitions when navigating

Categories

(Firefox for Android :: General, enhancement)

All
Android
enhancement

Tracking

()

People

(Reporter: boek, Unassigned)

Details

From github: https://github.com/mozilla-mobile/fenix/issues/17752.

What is the user problem or growth opportunity you want to see solved?

As a daily user of Firefox Mobile, I would like to have a better user experience when navigating (screens, not pages) - today, the home does not have any transition, and tapping any button will change the UI abruptly.

How do you know that this problem exists today? Why is this important?

There is no transition from the home screen to any other first screen, giving a clumsy appearance when the app navigates, impacting the user experience. Many browsers offer fluid navigation, which is suitable for extended usage.

For more details, I prepared a visual comparison at the bottom of this description with and without motion.

Who will benefit from it?

Users that consistently use the app might benefit from a more fluid experience.

Extra Information

Android offers Motion Transition out of the box for Navigation Component and Fragments, both used by Firefox Mobile, and it is easy to integrate with (you need to set the motion transition you want per Fragment). As far as I know, it also respects accessibility configurations like disable animations or reduce motion, so there's no need to support it manually.

As I already did the necessary changes to create the visual comparison, if a Firefox designer thinks to approve those changes, I can submit a Pull Request myself. Feel free to request a different transition if you believe it would be better - you can check the official design document for Motion Transitions here, there are few options.

Visual Comparison

No Motion Motion

┆Issue is synchronized with this Jira Task

Change performed by the Move to Bugzilla add-on.

Severity: -- → N/A
You need to log in before you can comment on or make changes to this bug.