Init helps Android apps schedule initialization of application, with type, priority and multi-process, tidy magic code for every process, and improves efficiency of application start.
It is originally designed for application initialization, but not confined to that, it can be applied to any complex initialization procedure.
dependencies {
compile 'cn.zhaiyifan:init:1.0.0'
}public class DemoApplication extends Application {
@Override
public void onCreate() {
super.onCreate();
// The library needs application context to get process information.
Init.init(this);
// Init.init(this, logProxy) enables custom log component
Task task1 = new Task("task1") {
@Override
protected void start() {
doSomeThing();
}
};
// Create a task which is not blocked with 300 milliseconds delay.
Task task2 = new Task("task2", false, 300) {
@Override
protected void start() {
doSomeThing();
}
};
// Create more tasks named task3, task4, task5, etc.
...
// This is like the two red tasks in the flow picture, task5 depends on task4.
task5.setParentTask(task4);
Flow flow = new Flow("flow");
flow.addTask(1, task1)
.addTask(1, task2)
.addTask(2, task3)
.addTask(2, task4)
.addTask(3, task5);
Init.start(flow);
}See demo project for more details.
Imagine how we initialize a large application like Facebook, QQ, Wechat, etc, we will face sth like:
public class XXXApplication {
// for multi-dex apps
@Override
protected void attachBaseContext(Context base) {
// log init
...
// eventbus init...
...
// global variables init
...
// process related
String processName = ...
boolean isMainProcess = ...
ProcessInit.attachBaseContext(this, processName, isMainProcess);
}
@Override
protected void onCreate() {
// process related
String processName = ...
boolean isMainProcess = ...
// CrashHandler, SafeMode, plugin, image manager, database, download, update, etc init
ProcessInit.onCreate(this, processName, isMainProcess);
}
}
public class ProcessInit {
...
public static void onCreate(Application application, boolean isMainProcess, String processName) {
if (isMainProcess) {
}
} else if (processName.contains(PUSH_PROCESS_SUFFIX)) {
...
} else if (processName.contains(WEB_PROCESS_SUFFIX)) {
...
} else if (processName.contains(MUSIC_PROCESS_SUFFIX)) {
...
} else {
...
}
...
}You see how complicated the initialization can be when the application grows, some operation should be after the other, and some can be done parallel, and some... Then we need to change the implementation of every init, to make some asynchronous, which makes code dirty and hard to understand.
How to make it simpler? I came up with this library.
The initialization procedure is abstracted to flow, wave and task.
Flow is a coarse-grained concept, normally we have only one flow, but under certain condition, we may have several flow like patch flow, broadcast flow, etc.
Each wave can be started only when all blocked task in last wave finished, and all tasks belongs to the wave will started at the same time(if no delay set).
As for task, they can be divided into two types
- Blocked task, blue tasks in the picture.
- Asynchronous task, can be
- completely asynchronous or across several waves like the green task.
- asynchronous task chain, like the two red tasks.
- 1.0 October - A workable solution to principles mentioned above DONE
- 1.1 In this year - Support more complex init flow WIP
- 2.0 Ability to reverse initialization code using this library to flow picture.
Contribution is welcomed, you can create an issue or directly make a pull request.