![]() ![]() For example, navigation transitions require some experimental animation APIs so cannot be built within navigation-compose but can be built in Accompanist.įor standalone features, you might think, why not just mark the APIs as Experimental in AndroidX? When we add an experimental API to AndroidX, we are confident that the feature will exist in some form but possibly the API will change shape. There were features we knew we could develop that wouldn’t be allowed in AndroidX. Why does Accompanist exist?Ī major reason for Accompanist’s existence is the fact that AndroidX does not allow experimental API usage across different modules. ![]() We frequently get asked a lot of questions about this library and so thought we could write a post to answer some of the most asked Accompanist questions. We want to upstream the libraries into the official toolkit, at which point they will be deprecated and removed from Accompanist.Ĭurrently in Accompanist you can find libraries for Flow Layouts, Pager, Navigation Transitions, Swipe Refresh and more. We use it to help fill known gaps in the Compose toolkit, experiment with new APIs and to gather insight into the development experience of developing a Compose library. Accompanist is a group of libraries that aim to supplement Jetpack Compose with features that are commonly required by developers but not yet officially supported in Jetpack Compose AndroidX libraries.Īccompanist is a labs-like environment for new Compose APIs. ![]()
0 Comments
Leave a Reply. |