Exercise 2: Why a Splash-Screen Screenshot Violates Guideline 2.3.3 — Possible Solution ============================================================================================ Guideline 2.3 exists to make sure a customer genuinely knows what they're getting before they download an app - the real metadata, including screenshots, is supposed to accurately reflect the app's own core experience. A splash or launch screen is, by its own real design purpose (Chapter 1's own real UILaunchScreen material), a brief, static placeholder shown only for the moment an app takes to actually finish launching - it deliberately shows no real content or functionality at all, since none has loaded yet. A screenshot showing only that launch screen would genuinely mislead a prospective user: it shows them nothing about what the app actually does once it finishes loading - no real task list, no real interface, no real functionality of any kind. A customer looking at that screenshot has no real, accurate basis for deciding whether the app is actually useful to them, which is precisely the outcome Guideline 2.3.3 exists to prevent. A genuinely compliant screenshot would instead show the app already running, mid-use, displaying its own real, populated interface - for TaskFlow, this would mean a real screenshot of the actual task list with genuine sample tasks visible, not an empty state, a loading spinner, or the launch screen itself. That gives a prospective user an honest, accurate picture of the real experience they'd actually get after downloading. ANSWER: A splash-screen screenshot shows no real content or functionality at all, since a launch screen deliberately displays nothing while the app is still loading - this leaves a prospective customer with no accurate basis for judging what the app actually does, which directly violates 2.3.3's own requirement that screenshots genuinely show the app in use. A compliant screenshot instead shows the app already running with real, populated content on screen. WHY THIS WORKS AS AN ANSWER ------------------------------ This connects the launch screen's own real, deliberate design purpose (from an earlier chapter) to why it fails as a screenshot, and describes a concrete, genuinely compliant alternative rather than just restating the rule.