android-startup GitHub Details, Stars and Alternatives | OpenRepoFinder
idisfkj / repository
android-startup
π₯The Android Startup library provides a straightforward, performant way to initialize components at the application startup. Both library developers and app developers can use Android Startup to streamline startup sequences and explicitly set the order of initialization.
A transparent discovery signal based on current public GitHub metadata.
Recent activity35% weight
100
Community adoption25% weight
62
Maintenance state20% weight
100
License clarity10% weight
100
Project information10% weight
100
This score does not audit code, security, maintainers, documentation quality, or suitability. Verify the repository and its current documentation before adoption.
The android-startup library provides a straightforward, performant way to initialize components at application startup. Both library developers and app developers can use android-startup to streamline startup sequences and explicitly set the order of initialization.
At the same time, the android-startup support async await and sync await. And topological ordering is used to ensure the initialization order of dependent components.
Here is a piece of with Google App Startup feature comparison table.
indicator
App Startup
Android Startup
Manually Config
β
β
Automatic Config
β
β
Support Dependencies
β
β
Handle Circle
β
β
Thread Of Control
β
β
Async Await
β
β
Callback Dependencies
β
β
Manual Notify
β
β
Topology Optimization
β
β
Time Cost Statistics
β
β
Thread Priority
β
β
Multiple Processes
β
β
Open source is not easy, I hope friends shake hands, a star in the upper right corner, thank youπ
There are tow ways of using android-startup in your project,need to be initialized before using android-startup.
Define Initialize components
You define each component initializer by creating a class that implements the AndroidStartup abstract.
This abstract implements the Startup<T> interface. And this abstract defines four important methods:
The callCreateOnMainThread(): Booleanmethod,which control the create()method is in the main thread calls.Othrewise in the other thread.
The waitOnMainThread(): Booleanmethod,which control the current component should call waiting in the main thread.If returns true, will block the main thread.
The create(): T?method,which contains all of the necessary operations to initialize the component and returns an instance of T
The dependenciesByName(): List<String>?method,which returns a list of type String that the initializer depends on.
For example, Define a SampleFirstStartup class that implements AndroidStartup<String>:
class SampleFirstStartup : AndroidStartup<String>() {
override fun callCreateOnMainThread(): Boolean = true
override fun waitOnMainThread(): Boolean = false
override fun create(context: Context): String? {
// todo something
return this.javaClass.simpleName
}
override fun dependenciesByName(): List<String>? {
return null
}
}
The dependenciesByName() method returns an null list because SampleFirstStartup does not depend on any other libraries.
Suppose that your app also depends on a library called SampleSecondStartup, which in turn depends on SampleFirstStartup. This dependency means that you need to make sure that Android Startup initializes SampleFirstStartup first.
class SampleSecondStartup : AndroidStartup<Boolean>() {
override fun callCreateOnMainThread(): Boolean = false
override fun waitOnMainThread(): Boolean = true
override fun create(context: Context): Boolean {
// Simulation execution time.
Thread.sleep(5000)
return true
}
override fun dependenciesByName(): List<String> {
return listOf("com.rousetime.sample.startup.SampleFirstStartup")
}
}
Because you include com.rousetime.sample.startup.SampleFirstStartup in the dependenciesByName() method, Android Startup initializes SampleFirstStartup before SampleSecondStartup.
The first one is automatic initializes startup in manifest.
Android Startup includes a special content provider called StartupProvider that it uses to discover and call your component startup.
In order for it to automatically identify, need in StartupProvider defined in the <meta-data> label.The name as defined by the component class, value values corresponding to the android.startup.
You don't need to add a <meta-data> entry for SampleFirstStartup, SampleSecondStartup and SampleThirdStartup, because them are a dependency of SampleFourthStartup. This means that if SampleFourthStartup is discoverable, then are also.
Manually initialization in application
The second one is manually initializes startup in application.
Consider again the example,to make sure Android Startup can initializes,you can use StartupManager.Builder() directly in order to manually initialize components.
For example, the following code calls StartupManager.Builder() and manually initializes them:
class SampleApplication : Application() {
override fun onCreate() {
super.onCreate()
StartupManager.Builder()
.addStartup(SampleFirstStartup())
.addStartup(SampleSecondStartup())
.addStartup(SampleThirdStartup())
.addStartup(SampleFourthStartup())
.build(this)
.start()
.await()
}
}
You can check out the sample app for more code information.
Run the example code, the console will produce the log as follows:
After the initialization sequence sorting optimization
