![\"Upgrade](\"https:\/\/blogger.googleusercontent.com\/img\/b\/R29vZ2xl\/AVvXsEg_Ek2FAu4xtj3kQEqLbutxWGSu2Ia1W85rM8QjxZ6S2woXClzsDmQIS5xEbvTjy78PmL1abA1OJ2lD2qbmC_NpsWfRP1fObeLs5rcJNPBOHK_GF_qV8Zrf3mKAb3Fjd2oOQNoKcLAgmIGUNn0VafZAUUaaEieNUc7rmWlFi8GHbHEwqumdX3v086ticOY\/s1600\/image7.png\")
<\/div>\nBack-to-home animation milestone<\/h3>\n
\nThe back-to-home animation<\/a> is the keystone predictive back animation.\n<\/p>\n \nTo get this animation, add \nIf you are intercepting back events in your root activity (e.g. MainActivity), you can continue to do so but you\u2019ll need to use supported APIs and you won\u2019t get the back-to-home animation. For this reason, we generally recommend you only intercept back events for UI logic; for example, to show a dialog asking the user to save before they quit.\n<\/p>\n \nSee the Add support for the predictive back gesture<\/a> guide for more details.\n<\/p>\n <\/image><\/p>\n \nIf you are a multi-activity app, you\u2019ll need to opt-in and handle back events within those activities too to get a system controlled cross-activity animation<\/a>. Learn more about per-activity opt-in<\/a>, available for devices running Android 14+. The cross-activity animation is visible to users in Android 15+ and behind a developer option in Android 13 and 14.\n<\/p>\n \nCustom cross activity animations are also available with overrideActivityTransition<\/a>.\n<\/p>\n <\/image><\/p>\n \nNext, you\u2019ll want to focus on your fragment animations and transitions. This requires updating to AndroidX fragment 1.7.0<\/a> and transition 1.5.0<\/a> or later and using Animator or AndroidX Transitions. Assuming these requirements are met, your existing fragment animations and transitions will animate in step with the back gesture. You can also use material motion<\/a> with fragments. Most material motions support predictive back as of 1.12.02-alpha02<\/a> or higher, including MaterialFadeThrough, MaterialSharedAxis and MaterialFade.\n<\/p>\n \nDon\u2019t strive to make your fragment transitions look like the system\u2019s cross-activity transition. We recommend this full screen surface transition<\/a> instead.\n<\/p>\n \nLearn more about Fragments and Predictive Back<\/a>.\n<\/p>\n \nFinally, you\u2019ll want to take advantage of the Material Component View animations available for Predictive Back. Learn more about available components<\/a>.\n<\/p>\n \nAfter this, you\u2019ve completed your quest to support Predictive Back animations in your view based app.\n<\/p>\n \nIf you\u2019re up for more, you might also ensure your AndroidX transitions are supported with Predictive Back. Read more about AndroidX Transitions and the Predictive Back Progress APIs<\/a>.\n<\/p>\n android:enableOnBackInvokedCallback=true <\/code>in your AndroidManifest.xml <\/code>for your root activity if you are a multi-activity app (see per-activity opt-in<\/a>) or at the application level if you are a single-activity app. After this, you\u2019ll see both the back-to-home animation and a cross-task animation where applicable, which are visible to users in Android 15+ and behind a developer option in Android 13 and 14.\n<\/p>\n![\"Milestone](\"https:\/\/developer.android.com\/static\/images\/about\/versions\/13\/predictive-back-nav-home.gif\")
Migrate all activities milestone<\/h3>\n
<\/div>\nFragment milestone<\/h3>\n
<\/div>\nMaterial Components milestone<\/h3>\n
<\/div>\n[Optional] AndroidX Transitions milestone<\/h3>\n