app啟動的關(guān)鍵節(jié)點(diǎn)

經(jīng)常利用content provider 和Androidx里的 startup庫來對庫進(jìn)行初始化操作,那么app啟動關(guān)鍵方法的執(zhí)行順序是什么樣的呢? 怎么樣控制我的庫的啟動順序?

參考這篇文章: Android 多個 ContentProvider 初始化順序

精髓在這張圖里:

回答上面的問題: 怎么樣控制我的庫的啟動順序?

推薦用contentprovider,設(shè)置initOrder.

不推薦用startup,因?yàn)樗荒茉赿ependices()回調(diào)里通過依賴來控制,是強(qiáng)依賴,不夠靈活

啟動時間怎么算

方案1: 參考firebase:

從第一個contentProvider的attachInfo,到第一個頁面的onReusme:

app-start-foreground-background-traces:https://firebase.google.com/docs/perf-mon/app-start-foreground-background-traces?authuser=0&platform=android

App start trace
This trace measures the time between when the user opens the app and when the app is responsive. In the console, the trace's name is _app_start. The collected metric for this trace is "duration".
?
Starts when the app's FirebasePerfProvider ContentProvider completes its onCreate method.
?
Stops when the first activity's onResume() method is called.
?
Note that if the app was not cold-started by an activity (for example, by a service or broadcast receiver), no trace is generated.

看一下FirebasePerfProvider的配置:

initOrder="101",基本是最大的. 項(xiàng)目里其他的Provider都沒有怎么配置initOrder

    <provider
            android:name="com.google.firebase.perf.provider.FirebasePerfProvider"
            android:authorities="${applicationId}.firebaseperfprovider"
            android:exported="false"
            android:initOrder="101" />

可以自己搞個類似的trace打印/上報一下

<provider
            android:name="com.xxx.logs.AppStartMeasurer"
            android:authorities="${applicationId}.AppStartMeasurer"
            android:exported="false"
            android:initOrder="102" />

然后就可以看logcat的日志輸出+ trace平臺的統(tǒng)計了

方案2 : ams

adb 命令:

adb shell am start -W 包名/入口activity全類名

在控制臺會輸出日志:

這里的時間會比方案1統(tǒng)計到的時間小一些

總結(jié)