Get the app
Home

Testing methodology

How We Test QuizScreen

Every product workflow on this site should be reproducible from the current public app and should clearly distinguish observation from outcome claims.

Product workflow

  1. Install the current App Store version on a supported device.
  2. Grant Screen Time access through the system permission flow.
  3. Select an app, verify the shield, complete a quiz, and test each finite unlock.
  4. Verify re-blocking after the chosen deadline.
  5. Check online question generation and the offline fallback separately.

Current public baseline: version 2.0.2, iOS or iPadOS 17 or later, last checked 2026-09-06.

Website verification

Each release is built as a static site, crawled from its sitemap, and checked for one H1, one self-referencing canonical, unique metadata, working internal links, valid JSON-LD, and reachable social assets.

Performance targets follow Google’s “good” Core Web Vitals thresholds: LCP no more than 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1 at the 75th percentile. Field data—not a single lab run—is the final measure.

What testing cannot prove

A successful blocking test does not prove that QuizScreen improves grades, treats a condition, or reduces screen time for every user. Those outcomes depend on the person, task, environment, and study design.