The future of page transitions with Shared Element Transitions
The future of page transitions with Shared Element Transitions
By Milan Vogels
4 min read
The Shared Element Transitions API allows creating page transitions using a browser API that can provide users with a better visual connection between page-a and page-b by transitioning shared elements on both pages.
- Authors
- Name
- Milan Vogels
- linkedinMilan Vogels
- twitter@milanvogels
In native mobile app development transitioning from one page/state to another is something that has been supported for a long time. For example, you can do this using Activity transitions for Android. For the web, however, things aren't all that easy.
Yes, we can create transitions between pages using libraries like BarbaJs. But these don't provide any visual connection between page-a and page-b to the user. So to close the gap, a new browser API is in the works: Shared Element Transition API.
The Shared Element Transition is a proposal for a new Web API. It allows for creating transition animations between page navigation and transitioning elements that are present on both pages.
Getting started
To get started with the Shared Element Transition API the following flags have to be enabled in Chrome:
chrome://flags/#document-transitionchrome://flags/#enable-experimental-web-platform-features
First of all, we need to check if the browser supports the API, and add a fallback if they don't.
async function navigate() {
if (!document.createDocumentTransition) {
updateDOM(); // update the DOM
return;
}
}
If it does support the new API, we can use the createDocumentTransition function to create a new transition.
async function navigate() {
if (!document.createDocumentTransition) {
updateDOM(); // update the DOM
return;
}
const transition = document.createDocumentTransition();
await transition.start(() => updateDOM());
}
The default transition the API creates is a simple fade. I created a small CodePen example that just toggles between a card view and a detail view by toggling the display style.
Changing the animation
The animation is using CSS. The default browser UA styles will animate ::page-transition-incoming-image from opacity: 0; and ::page-transition-outgoing-image to opacity: 0;.
We can add our own animations by using the following pseudo-element selectors
::page-transition
::page-transition-container(root)
::page-transition-image-wrapper(root)
::page-transition-outgoing-image(root)
::page-transition-incoming-image(root)
For example, we can change the animation to a slide out:
@keyframes slide-to-top {
to {
transform: translateY(-100%);
}
}
::page-transition-outgoing-image(root) {
animation: 400ms ease-out both slide-to-top;
}
::page-transition-incoming-image(root) {
animation: none; /* disable default animation */
}
To animate separate elements, instead of the whole page, we can replace root with a page-transition-tag property value you can add to another css selector. The default animation transitions the width and height attributes from the 'before' state to the 'after' state. Also, it animates the transform to update to the position of the targeted element.
In the following example, we add a page-transition-tag: article-img to an image tag.
.foo img {
page-transition-tag: article-img;
}
::page-transition-outgoing-image(article-image) {}
::page-transition-incoming-image(article-image) {}
This gives us an already pretty cool effect.
If we want specific elements of our site to stay in place during the transition, we have to add a page-transition-tag and contain: paint. Assuming the element won't change between page-a and page-b, the element will now remain in the same place.
.header {
page-transition-tag: header;
contain: paint;
}
We can't have the same page-transition-tag being used multiple times on the same page. We'll get an error in the console when starting the transition:
Unexpected duplicate page transition tag: tag-name
So instead of defining it in CSS, we can add it with JavaScript, for example on a click event.
async function navigate() {
if (!document.createDocumentTransition) {
updateDOM(); // update the DOM
return;
}
const foo = GetElementYouClickedOn();
foo.style.pageTransitionTag = 'article-img';
const transition = document.createDocumentTransition();
await transition.start(() => updateDOM());
foo.style.pageTransitionTag = '';
}
Here's an example of a full grid of cards animating each card's image to the full article image. It still shows the singular article detail view we created, hence the detail image doesn't reflect the card's image.
Multi-page applications
The current iteration of the Shared Element Transition API only supports Single-page applications (SPAs). Support for Multi-page applications (MPAs) is on the roadmap to be added in the future. The use of the API for SPAs or MPAs should work similarly.
Start experimenting!
I'm really excited about this API myself, it allows us to create page transitions that can add context to the user in a non-complicated way without the use of any 3rd party libraries. The Shared Element Transition API is still in an early phase and it will take some time until it's ready for shipping and implemented by other browsers, but we can already experiment a lot with it.
I would like to encourage you to do the same and share your opinions in the Github repository. Can't wait to see what others can create with this new API.
Bright times ahead for page transitions!
Upcoming events
Mastering Event-Driven Design
PLEASE RSVP SO THAT WE KNOW HOW MUCH FOOD WE WILL NEED Are you and your team struggling with event-driven microservices? Join us for a meetup with Mehmet Akif Tütüncü, a senior software engineer, who has given multiple great talks so far and Allard Buijze founder of CTO and founder of AxonIQ, who built the fundaments of the Axon Framework. RSVP for an evening of learning, delicious food, and the fusion of creativity and tech! 🚀 18:00 – 🚪 Doors open to the public 18:15 – 🍕 Let’s eat 19:00 – 📢 Getting Your Axe On Event Sourcing with Axon Framework 20:00 – 🍹 Small break 20:15 – 📢 Event-Driven Microservices - Beyond the Fairy Tale 21:00 – 🙋♀️ drinks 22:00 – 🍻 See you next time? Details: Getting Your Axe On - Event Sourcing with Axon Framework In this presentation, we will explore the basics of event-driven architecture using Axon Framework. We'll start by explaining key concepts such as Event Sourcing and Command Query Responsibility Segregation (CQRS), and how they can improve the scalability and maintainability of modern applications. You will learn what Axon Framework is, how it simplifies implementing these patterns, and see hands-on examples of setting up a project with Axon Framework and Spring Boot. Whether you are new to these concepts or looking to understand them more, this session will provide practical insights and tools to help you build resilient and efficient applications. Event-Driven Microservices - Beyond the Fairy Tale Our applications need to be faster, better, bigger, smarter, and more enjoyable to meet our demanding end-users needs. In recent years, the way we build, run, and operate our software has changed significantly. We use scalable platforms to deploy and manage our applications. Instead of big monolithic deployment applications, we now deploy small, functionally consistent components as microservices. Problem. Solved. Right? Unfortunately, for most of us, microservices, and especially their event-driven variants, do not deliver on the beautiful, fairy-tale-like promises that surround them.In this session, Allard will share a different take on microservices. We will see that not much has changed in how we build software, which is why so many “microservices projects” fail nowadays. What lessons can we learn from concepts like DDD, CQRS, and Event Sourcing to help manage the complexity of our systems? He will also show how message-driven communication allows us to focus on finding the boundaries of functionally cohesive components, which we can evolve into microservices should the need arise.
| Coven of Wisdom - Utrecht
Go to page for Mastering Event-Driven DesignThe Leadership Meetup
PLEASE RSVP SO THAT WE KNOW HOW MUCH FOOD WE WILL NEED What distinguishes a software developer from a software team lead? As a team leader, you are responsible for people, their performance, and motivation. Your output is the output of your team. Whether you are a front-end or back-end developer, or any other discipline that wants to grow into the role of a tech lead, RSVP for an evening of learning, delicious food, and the fusion of leadership and tech! 🚀 18:00 – 🚪 Doors open to the public 18:15 – 🍕 Let’s eat 19:00 – 📢 First round of Talks 19:45 – 🍹 Small break 20:00 – 📢 Second round of Talks 20:45 – 🙋♀️ drinks 21:00 – 🍻 See you next time? First Round of Talks: Pixel Perfect and Perfectly Insane: About That Time My Brain Just Switched Off Remy Parzinski, Design System Lead at Logius Learn from Remy how you can care for yourself because we all need to. Second Round of Talks: Becoming a LeadDev at your client; How to Fail at Large (or How to Do Slightly Better) Arno Koehler Engineering Manager @ iO What are the things that will help you become a lead engineer? Building Team Culture (Tales of trust and positivity) Michel Blankenstein Engineering Manager @ iO & Head of Technology @ Zorggenoot How do you create a culture at your company or team? RSVP now to secure your spot, and let's explore the fascinating world of design systems together!
| Coven of Wisdom - Amsterdam
Go to page for The Leadership MeetupCoven of Wisdom - Herentals - Spring `24 edition
Join us for an exciting web technology meetup where you’ll get a chance to gain valuable insights and knowledge about the latest trends in the field. Don’t miss out on this opportunity to expand your knowledge, network with fellow developers, and discover new and exciting possibilities. And the best part? Food and drinks are on us! Johan Vervloet - Event sourced wiezen; an introduction to Event Sourcing and CQRS Join me on a journey into the world of CQRS and Event Sourcing! Together we will unravel the misteries behind these powerful concepts, by exploring a real-life application: a score app for the 'Wiezen' card game.Using examples straight from the card table, we will delve into the depths of event sourcing and CQRS, comparing them to more traditional approaches that rely on an ORM.We will uncover the signs in your own database that indicate where event sourcing can bring added value. I will also provide you with some tips and pointers, should you decide to embark on your own event sourcing adventure. Filip Van Reeth - WordPress API; "Are you talking to me?" What if the WordPress API could be one of your best friends? What kind of light-hearted or profound requests would it share with you? In this talk, I would like to introduce you to it and ensure that you become best friends so that together you can have many more pleasant conversations (calls). Wanna be friends? Please note that the event or talks will be conducted in Dutch. Want to give a talk? Send us your proposal at meetup.herentals@iodigital.com 18:00 - 19:00: Food/Drinks/Networking 19:00 - 21:00: Talks 21:00 - 22:00: Networking Thursday 30th of May, 18h00 - 22h00 CET iO Campus Herentals, Zavelheide 15, Herentals
| Coven of Wisdom Herentals
Go to page for Coven of Wisdom - Herentals - Spring `24 edition