Description
6.0.0:
Please allow using AppIntro as a Fragment. I plan on running the app intro when the user first opens the app for the first time, and when they decline permissions from app settings(Since my app intro will ask for permissions). This requires me to have two activities, one for app intro and one for my actual app. If I choose the app intro activity to be the launcher activity, it will slow down app startups after the app intro is complete, since the app intro will have to launch and then shut down and launch my main activity.
Also alternatively if I choose my main activity to be the launcher activity it will slow down the first-time app startup for the same reason. I ran this test on my Facetocall app for 110K users. It showed a delay of up to 300 MS if you jump between activities during app startup.
If you will be so kind and implement AppIntroFragment, it will allow faster startups. Also, it will give more control to developers who plan to have more than one app intro. I am now working on a new SMS app, and I plan to have several app startups to handle the default app permission request and regular permissions. Also, I will have some UI customizations that I will allow to launch multiple times.