I'm currently working on a project in Android Studio and noticed the traditional approach to creating a splash screen involves making a separate activity and manually setting a timer before moving to the main activity.

My questions are:

Is it considered best practice to implement a splash screen this way?

Should the splash screen activity be set as the launcher activity in the manifest?

What are the pros and cons of this approach compared to newer recommended methods (e.g., using themes or SplashScreen API)?

I’d appreciate guidance from experienced developers on whether this traditional method is still valid, or if there are better alternatives.

Nikita Pawar's user avatar

1

If you are asking about the recommended approach from Google, the answer is to avoid using a dedicated Splash Activity and instead use the SplashScreen API provided by Google: https://developer.android.com/develop/ui/views/launch/splash-screen

Google suggests that, for better UX, users should not be blocked on a splash screen for too long. For this reason, they discourage the use of a dedicated SplashActivity. Even if you create one, Android Studio will show warnings and will not encourage this approach.

The new Splash Screen API itself supports drawable-based animations and allows you to control how long the splash screen is displayed.

Meet Miyani's user avatar

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.