Skip to content

Conversation

@Haz3-jolt
Copy link
Member

@Haz3-jolt Haz3-jolt commented Jan 7, 2026

Purpose / Description

Continuation of #14837
Full credit to S-H-Y-A for the original PR

Fixes

Approach

  • Could not rebase PR since it is quite old and diverged from main, so picked parts of it onto current point from main.

How Has This Been Tested?

Pixel 9 Pro (API 36)
Screen_recording_20260108_033309.webm

Checklist

Please, go through these checks before submitting the PR.

  • You have a descriptive commit message with a short title (first line, max 50 chars).
  • You have commented your code, particularly in hard-to-understand areas
  • You have performed a self-review of your own code
  • UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
  • UI Changes: You have tested your change using the Google Accessibility Scanner

- Fixed up the splash screen proposed in PR ankidroid#14837

Co-authored-by: S-H-Y-A <74596628+s-h-y-a@users.noreply.github.com>
@Haz3-jolt Haz3-jolt marked this pull request as ready for review January 7, 2026 22:05
@mikehardy
Copy link
Member

Interesting. The issue itself says "add splash screen to make user experiences richer"

The problem is that this is qualitative. And some users hate hate hate splash screens. The canonical reason to hate a splash screen is that you opened the app because you want to use it right now. What is this dancing baloney on the screen preventing you from using the app right now?

The historical need for a splash or loading screen was to give the appearance of activity while the app was preparing itself to be available for work. But if the app is ready for work then there is no technical need to delay doing useful work.

I would at minimum expect a lot of requests for a toggle to turn this off.
And I wouuld also expect that if it were on, it was really really brief

I have to admit I'm not sold on the idea at all - I didn't realize that was an open issue to be honest, and there hasn't been much discussion. I'll crosspost my thoughts there

@BrayanDSO
Copy link
Member

Splash screens are only useful if the app takes too much time to start up. Even on slow phones, AnkiDroid shouldn't take more than 2 seconds to appear. Animating something to fit that small time frame is jankier than a static screen. Delaying the app startup to show an animation is unnacceptable.

Particularly, I would like to focus on making the app startup faster instead of that.

@david-allison
Copy link
Member

From my comment on the issue:

Our splash screen should NOT add forced latency to the startup (other than the milliseconds to display the screen)

In order to make that work visually, I feel a subtle 'scale up' animation of the logo, from maybe 90% size to 100% size would be sufficient.

@david-allison
Copy link
Member

I'm open to this as long as it:

  • Looks good (subjective)
  • Doesn't add latency
  • Isn't developer-time intensive

@BrayanDSO BrayanDSO added Needs Author Reply Waiting for a reply from the original author and removed Needs Review labels Jan 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Needs Author Reply Waiting for a reply from the original author

Projects

None yet

Development

Successfully merging this pull request may close these issues.

#14837 Add SplashScreen

4 participants