Show relevant screen transitions on a mobile web application is a difficult problem.
At Doctolib, we faced this problem. We haven't found any satisfactory solution in the open source world. We had to improvise and respond with an original solution.
1. Screen transitions with ease
Olivier Tassinari, Doctolib, @oliviertassinari
React Paris Meetup
2. Why using transitions ?
• Provide a better UX
• Makes the users wait
• Create a visual mapping of the state of the app
• The native apps have well understood this, what
about the web?
16. No :(
• We also need to manage the transitions based on
the screen we display
17. Using a custom state?
• No
• We need to be highly bound to the history API
• We need to handle the Android back button
18. Apply the transition on the routes? :(
• Is declarative
• But, we need to distinguish the show and dismiss
transition
• But, we often need
some custom
transition
on some button
We can’t have show-from-
right and reveal-from-right
at the same time
19. With a full mapping :(
• The number of combinations can potentially be n^2
• Hard to maintain over time
28. • Advanced features:
• Support nesting
• Upcoming improvements
• Open sourcing of the TransitionGroup
• Wait for the screen to be mounted before triggering the
transition
• Disabling the transitions on low-end devices that are
just too slow
doctolib/react-router-transitions
Open source