A software development kit (SDK) can affect mobile launch performance as much as its feature set. When analytics, crash reporting, authentication, push notifications, and mapping accumulate, initializing every SDK at startup can add seconds before the app becomes usable. section 5.2.2
Schedule SDK initialization by user impact rather than treating every dependency as launch-critical:
- Initialize lightweight analytics and crash reporting synchronously when immediate availability is needed. section 5.2.2
- Defer push-notification registration until the first screen is displayed. section 5.2.2
- Initialize a mapping SDK only when the user opens a map view. section 5.2.2
Launch-path budget
A native iOS or Android app can choose exactly which SDKs run on launch and which load on demand. This control can protect launch time, but platform-specific implementations may differ because Swift and Kotlin expose different lifecycle, concurrency, and memory-management APIs. section 5.2.2

