|Latest Update||Current Stable Release||Next Release Candidate||Beta Release||Alpha Release|
|October 28, 2020||1.0.0||-||-||-|
Your feedback helps make Jetpack better. Let us know if you discover new issues or have ideas for improving this library. Please take a look at the existing issues in this library before you create a new one. You can add your vote to an existing issue by clicking the star button.
See the Issue Tracker documentation for more information.
October 28, 2020
androidx.startup:startup-runtime:1.0.0 is released. Version 1.0.0 contains these commits.
Major features of 1.0.0
- Provides a straightforward, performant way to define
Initializers to run at application startup without having to define a
- Provides a consistent API for lazy initialization.
Initializers can define dependencies on other
Initializers which helps define the order of initialization explicitly.
October 14, 2020
androidx.startup:startup-runtime:1.0.0-rc01 is released. Version 1.0.0-rc01 contains these commits.
This release is identical to
September 16, 2020
androidx.startup:startup-runtime:1.0.0-beta01 is released. Version 1.0.0-beta01 contains these commits.
This version is identical to
androidx.startup is now API stable.
August 19, 2020
androidx.startup:startup-runtime:1.0.0-alpha03 is released. Version 1.0.0-alpha03 contains these commits.
- Added a new
isEagerlyInitialized()API which provides a way for the
Initializerto determine if it has been eagerly initialized. (aosp/1372879, b/159952713)
July 22, 2020
androidx.startup:startup-runtime:1.0.0-alpha02 is released. Version 1.0.0-alpha02 contains these commits.
- Publish consumer proguard rules for startup-runtime. (aosp/1347583, b/159595260)
- Improve static checks in
June 10, 2020
androidx.startup:startup-runtime:1.0.0-alpha01 is released. Version 1.0.0-alpha01 contains these commits.
The App Startup library provides a straightforward, performant way to initialize components at application startup. Both library developers and app developers can use App Startup to streamline startup sequences and explicitly set the order of initialization.
This initial release is