![google accompanist google accompanist](http://images4.fanpop.com/image/photos/15500000/Louise-Brooks-3-louise-brooks-15591054-749-1000.jpg)
This also applies to androidx.navigation and. However, it also means that experimental APIs, being APIs that can shift out from underneath you, are strictly forbidden across different artifact groups - again, upgrading your version of agment shouldn’t break androidx.appcompat.
#Google accompanist upgrade
This is great when it comes to forward and backward compatibility - for instance, you can upgrade your Fragment version to try out a new alpha while keeping your other dependencies on their stable releases and everything just works. It would take a major version bump (i.e., a ‘2.0’) to make breaking API changes to these stable APIs. This means that any API that isn’t experimental is set in stone once a library goes to its Release Candidate (RC) phase. (If you were along for the ride for early Compose releases, you know this pain.)Īll AndroidX libraries, Navigation and Compose included, follow strict semantic versioning as explained on the AndroidX releases page.
#Google accompanist update
As such, any library that is built on those Experimental APIs would immediately crash and fail if you were to update the version of Compose you were using and not also update that library at the same time. This means that those APIs might be changed, improved, or replaced in any future release - maybe it is Compose 1.1.0-alpha04 or 1.2.0-alpha08. While a number of lower level Animation APIs like the incredibly powerful animateTo() and animate*AsState() are stable, foundational parts of Compose at this point, there’s a whole class of APIs on top of those building blocks marked with Experimental APIs and Semantic VersioningĪn Experimental API (any API using API in Kotlin land) means that these APIs are subject to change at any point. In the quest for the perfect animation APIs, a lot of changes were made as Compose marched towards 1.0.0. One of the areas that has been a huge improvement over the View world has been that of animations and transitions. Jetpack Compose has come a long, long way since the first 0.1.0-dev01 release through to the new Compose 1.0.1 release. Building towards the future Animation APIs (shared element transitions!!!) in Compose 1.1.0 and beyondĮach of these requires a slightly different approach, which we’ll cover here.Enabling support for Experimental Animation APIs present in Compose 1.0.0.Using only the stable Animation APIs in Compose 1.0.0.That’s why Navigation Compose has been working towards a set of solutions that solve three specific cases: Jetpack Compose moves the bar on animations from ‘polish, if we have the time’ to ‘so easy there’s no reason to not do it’ and a big part of that are screen level transitions.