You Are Not Sitting Still

APP NAME
You Are Not Sitting Still

APP IDEA
A live counter that starts the moment the page opens and keeps adding layers of motion, so the distance the user has "travelled" while sitting still grows by orders of magnitude as they scroll.

CORE EXPERIENCE
The app opens directly on a title asking how fast the user is moving, a green banner reading "It has been 0 seconds" that starts counting immediately, and the first illustration. Scrolling reveals each successive layer of motion.

INTERACTION AND STATE
A single elapsed-seconds timer drives every figure on the page at once; all distances recompute live as the timer runs. Each layer adds its own velocity to the running total and restates the cumulative distance, so the number jumps by orders of magnitude down the page. Between layers a small "But wait..." line acts as the connector. The final layer inverts the whole thing and returns zero. No input beyond scrolling.

VISUAL AND CONTENT DIRECTION
Light page, one centred card per layer, with the elapsed-seconds banner pinned in green at the top. Each layer is a short paragraph with its speed in bold and the cumulative distance rendered as a large emphasised figure on its own line. One tectonic-plate diagram illustrates the first layer; the remaining layers are typographic.

OUTCOME
A final cumulative distance, immediately undercut by the closing line that says speed is relative and the user has moved zero miles.

ONE-SENTENCE INSTRUCTION
Just scroll — the counter has already started.

TASK-SPECIFIC REQUIREMENTS
Include exactly these ten layers in this order with these rates: tectonic plates at about 2 inches per year; Earth spinning at about 1,000 mph at the equator; Earth orbiting the Sun at 66,000 mph; the Sun moving toward Vega at 43,000 mph; the Sun orbiting the Milky Way at 483,000 mph; the Milky Way and Andromeda closing at 225,000 mph; the whole Milky Way moving at 1,300,000 mph; the expansion of the universe measured from the furthest known galaxy; a speculative multiverse figure with a question mark; and finally the relativity line resolving to 0 miles. Each layer states the cumulative distance, not just its own contribution.

Server-render determinism: do not call Date.now(), new Date() or Math.random() during initial render. Read the clock and generate randomness only inside client effects, and hard-code the default locale to English rather than detecting navigator.language, so first paint is identical on server and client and never produces a hydration mismatch.

REPLICATION SCOPE

This specification is a faithful rebuild of an existing reference experience, described here in full. Reproduce it as closely as the platform allows.

Must be reproduced exactly: the complete content inventory listed above with its exact ordering and wording, the mechanic and its state transitions, the copy voice, the visual structure and the overall pacing. Do not add levels, items, scoring, achievements, timers, onboarding or extra features that are not described here. Do not drop or abbreviate any listed content.

Acceptable platform adaptations, and only these: touch input in place of mouse input; layout reflow for a phone-sized portrait host; the bilingual layer, the one-sentence instruction and the result/Replay/Share affordances required below; and host safe-area insets. Everything else stays as specified.

All content must be self-contained. Do not call any external API, data service, map, media or image service at runtime; every dataset, table, constant and asset this app needs must live inside the project.

IMPLEMENTATION INSTRUCTIONS

Treat this specification as the final implementation brief and build the complete app now.

Open directly into the live app experience. Do not add a splash screen, opening cover, welcome page or separate onboarding flow.

Include exactly one concise sentence that explains how to play or use the app. Use the sentence provided under ONE-SENTENCE INSTRUCTION. Show it inside the live app interface, not on a separate opening screen.

Internationalization is required. Implement a lightweight built-in i18n layer supporting exactly two locales: English (en) and Simplified Chinese (zh). The app must always open in English and must never auto-detect or follow the browser, device or system language. Provide one clear EN / 中文 language toggle. Every user-facing string, including the one-sentence instruction and all loading, empty, success, error and result states, must have complete English and Chinese versions. Switching languages must update the entire interface without mixed-language text or untranslated fallback strings.

Let Eazo adapt the app to its actual host and available viewport. Do not hard-code or target a particular browser size, device size, viewport width or height, App frame size, root-height formula, or host-container CSS implementation. In the live preview, keep the current primary action easy to discover and usable without requiring an initial downward scroll; avoid horizontal overflow and avoid decorative layers blocking required controls. Optional detail may scroll. Keep active media and secondary copy compact enough that the next action remains visible. In result states, show the summary plus Replay and Share before optional detail. Do not eagerly render a large collection of full-size result images in one long page; use a compact summary, carousel, pagination, expansion, or virtualization. Use accessible touch targets.

Respect the host safe areas for iPhone notches, Dynamic Island, the status bar and the bottom home indicator in the initial implementation, before the first preview. Apply the safe-area treatment to the App's entire usable content region across the live flow, result, modal, empty and error states, not only to the first header. Keep the header, language toggle, primary controls and result actions entirely inside the usable safe area. In the standard Eazo mobile host, use `padding-top: max(56px, env(safe-area-inset-top, 0px))` and `padding-bottom: max(34px, env(safe-area-inset-bottom, 0px))`, or Eazo's current official safe-area equivalent. If the header or action footer is sticky or fixed, include the matching inset in that region and reserve content clearance so it does not overlap the scrollable body. These are safe-area insets only, not fixed viewport or App-frame dimensions; continue to let Eazo adapt the overall width and height. Make sure flex children can shrink inside the remaining usable area and that required controls are not covered or pushed off screen.

Use Eazo's built-in defaults and official platform capabilities. Do not add unrelated features or expand the scope beyond this specification.

When implementation is complete, provide a working preview for QA.