Skip to content

Shared Element Activity Transition

Jump to bottom
nidhi1608 edited this page Mar 9, 2015 · 38 revisions

Overview

Traditionally transitions between different activities or fragments involved enter and exit transitions that animated entire view hierarchies independant to each other. Example of such transitions are a fade transition, slide transition or the newly introduced explode transition.

Default Activity Transition:

<iframe title="YouTube video player" width="480" height="390" src="https://www.youtube.com/watch?v=XxnsSNX22hY?autoplay=1" frameborder="0" allowfullscreen></iframe>

However, many times, there are elements common to both activities and providing the ability to transition these shared elements separately emphasizes continuity between transitions and breaks activity boundaries as the user navigates the app.

SharedElement

The nature of this transition forces the human eye to focus on the content and its representation in the new activity instead of the actual activity frame sliding or fading which makes the experience a lot more seamless.

<iframe title="YouTube video player" width="480" height="390" src="http://youtu.be/XkWI1FKKrs4?autoplay=1" frameborder="0" allowfullscreen></iframe>

Created by CodePath with much help from the community. Contributed content licensed under cc-wiki with attribution required. You are free to remix and reuse, as long as you attribute and use a similar license.

Finding these guides helpful?

We need help from the broader community to improve these guides, add new topics and keep the topics up-to-date. See our contribution guidelines here and our topic issues list for great ways to help out.

Check these same guides through our standalone viewer for a better browsing experience and an improved search. Follow us on twitter @codepath for access to more useful Android development resources.

Clone this wiki locally