Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Android Transitions
Search
Bryan Herbst
February 06, 2016
Programming
0
450
Android Transitions
A tour of the Transitions framework in Android
Bryan Herbst
February 06, 2016
Tweet
Share
More Decks by Bryan Herbst
See All by Bryan Herbst
Semantics in Jetpack Compose
bherbst
0
11k
Kotlin Multiplatform
bherbst
0
780
Android App Architecture & Navigation
bherbst
0
2k
What's in the Android Toolbox
bherbst
0
490
Gradle Deep Dive
bherbst
2
1.9k
Actions with Google
bherbst
0
1.3k
Databinding in Android
bherbst
0
420
Activities Vs. Fragments
bherbst
0
330
Android Transitions
bherbst
0
58
Other Decks in Programming
See All in Programming
20250426 GDGoC 合同新歓 - GDGoC のススメ
getty708
0
110
Bedrock×MCPで社内ブログ執筆文化を育てたい!
har1101
7
1.4k
Golangci-lint v2爆誕: 君たちはどうすべきか
logica0419
1
230
eBPF超入門「o11yに使える」とは (20250424_eBPF_o11y)
thousanda
1
110
Memory API : Patterns, Performance et Cas d'Utilisation
josepaumard
1
170
The Nature of Complexity in John Ousterhout’s Philosophy of Software Design
philipschwarz
PRO
0
160
fieldalignmentから見るGoの構造体
kuro_kurorrr
0
130
AI時代の開発者評価について
ayumuu
0
230
Jakarta EE Meets AI
ivargrimstad
0
800
SwiftDataのカスタムデータストアを試してみた
1mash0
0
140
KANNA Android の技術的課題と取り組み
watabee
0
190
複雑なフォームの jotai 設計 / Designing jotai(state) for Complex Forms #layerx_frontend
izumin5210
6
1.5k
Featured
See All Featured
For a Future-Friendly Web
brad_frost
177
9.7k
Side Projects
sachag
453
42k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
105
19k
Chrome DevTools: State of the Union 2024 - Debugging React & Beyond
addyosmani
5
590
Intergalactic Javascript Robots from Outer Space
tanoku
271
27k
RailsConf 2023
tenderlove
30
1.1k
Put a Button on it: Removing Barriers to Going Fast.
kastner
60
3.8k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
280
13k
How to Create Impact in a Changing Tech Landscape [PerfNow 2023]
tammyeverts
52
2.4k
Making Projects Easy
brettharned
116
6.2k
Why Our Code Smells
bkeepers
PRO
336
57k
Documentation Writing (for coders)
carmenintech
71
4.7k
Transcript
Transitions Bryan Herbst Android Engineer @ Target
Abrupt transitions are jarring
Smooth transitions provide continuity
Smooth transitions keep users engaged
Smooth transitions delight users
“In the world of material design, motion describes spatial relationships,
functionality, and intention with beauty and fluidity.”
Android Transitions Activity to Activity Fragment to Fragment
Scene to Scene (Views)
Hold on… Requires API 21
Hold on… Progressive enhancement, graceful degradation
Hold on… Support APIs offer default behavior
on older versions
Scenes Snapshot of a ViewGroup
Scene transition TransitionManager.beginDelayedTransition(rootView, new Fade()); button.setVisibility(View.INVISIBLE);
What is this black magic?
How it works 1. beginDelayedTransition() => Take a snapshot of
ViewGroup 2. Update Views 3. On next layout pass, Android takes another snapshot and creates animations
How it works 1. beginDelayedTransition() => Take a snapshot of
ViewGroup
How it works 1. beginDelayedTransition() => Take a snapshot of
ViewGroup 2. Update Views
Transition types Fade Explode Slide ChangeBounds
AutoTransition Fade Move Resize
What about property animation? ObjectAnimator.ofFloat(button, "alpha", 1f, 0f) .start();
What about property animation? button.animate().alpha(0f);
What about property animation? Fine if you want to think
about Views individually
What about property animation? Fine if you want to think
about Views individually Scenes allow us to think in groups
Activities With shared elements
Activity Transitions- setup Request Window.FEATURE_ACTIVITY_TRANSITIONS and Window.FEATURE_CONTENT_TRANSITIONS in both
Activities
Activity Transitions- setup Set a transition name on
the View in both Activities
What are these transition names? An ID for the transition
framework
Rule #1 All animating Views must have a transition name
Rule #2 All transition names must be unique within a
layout
Not a rule #1 Transition names don’t need to match
between layouts
Activity Transitions- setup Create a Bundle with ActivityOptions .makeSceneTransitionAnimation(activity,
sharedView, viewTransitionName) .toBundle();
Activity Transitions- setup Set your Transitions
Activity Transitions- setup Call startActivity(intent, transitionBundle);
Specifying shared elements makeSceneTransitionAnimation(activity, sharedView, transitionName); We specify pairs of
Views and transition names.
Specifying shared elements makeSceneTransitionAnimation(activity, sharedView, transitionName); We specify pairs of
Views and transition names. The sharedView is the original view in our current layout (the starting state)
Specifying shared elements makeSceneTransitionAnimation(activity, sharedView, transitionName); We specify pairs of
Views and transition names. The sharedView is the original view in our current layout (the starting state) The viewTransitionName is the name of the corresponding view in the new layout (the ending state)
Activity transitions magic Captures Views in first Activity, then second
Activity
Activity Transitions use the Window e.g. getWindow().setEnterTransition(new Fade());
Four transition types Enter Exit Reenter
Return
Four transition types Enter
Four transition types Exit
Four transition types Reenter
Four transition types Return
Four transition types x2 with Shared elements
Or not Stick with enter and return for shared elements
Shared exit and reenter Allow for animation before the transition
Sample Exit, shared enter, enter
Sample Reenter, shared return, return
A note on timing Because sometimes Views don’t exist right
away
Delayed transitions postponeEnterTransition(); startPostponedEnterTransition();
WARNING! Blocks transition
WARNING! Blocks transition
WARNING! Prefetch or find clever alternatives
Fragment example
Transition setup setExitTransition(new Fade()); Fade out non-shared elements
Transition setup newFrag.setSharedElementEnterTransition(new AutoTransition()); AutoTransition shared elements
Transition setup newFrag.setEnterTransition(new Fade()); Fade in non-shared elements
Making the transition fragmentManager.beginTransaction() .replace(R.id.container, newFrag) .addSharedElement(sharedView, "transitionName") .commit();
What about delayed transitions? Ugh. It isn’t good in
Fragments.
I didn’t want to animate that!
Targets- includes <fade> <targets> <target android:includeId="@id/fancyWidget"/> <target android:includeClass=“com.example.FancyWidget"/> <target android:includeName=“fancyWidget"/>
</targets> </fade>
Targets- excludes <fade> <targets> <target android:excludeId="@id/toolbar"/> <target android:excludeClass=“android.support.v7.widget.Toolbar"/> <target android:excludeName="toolbar"/>
</targets> </fade>
Support for <21
Support for <21 ActivityOptions => ActivityOptionsCompat .makeSceneTransitionAnimation(activity, view, name)
Support for <21 startActivity(intent, transitionBundle); Has existed since API 16!
Support for <21 Transition names android:transitionName="name" is ignored on
older versions ViewCompat.setTransitionName(view, “name);
Support for <21 Delaying transitions supportPostponeEnterTransition(); supportStartPostponedEnterTransition();
Support for <21 Specifying transitions The only place we need
a version check if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.LOLLIPOP) { getWindow().setEnterTransition(new Fade()); }