FLOW

How it works

Sessions are short and mobile-friendly. Guest state can later join an account. Visual language uses gold/amber inside the Reiwa Sakura shell.

FEATURES

Capabilities

Primary interaction in the browser.

Progression layers that start without an account.

First session does not require credentials.

Progress can attach after sign-in.

Tap, Dig, and Discover are the public loops. The client keeps the interaction close; the server stores progression when it matters.

Play starts without signup. That is a product decision, not a missing auth system.

Optional sign-in links progression to a person. Guest tokens are not administrative credentials.

Rewards and progress are product state. This site does not publish player counts or retention numbers.

ENGINEERING

Clients, APIs, and domain concerns. No private hosts or credentials.

Client

Session

Progress

Account

Browser-first clientGuest sessionOptional accountsProgression writes over HTTPS

Browser client, session, progression, account link. Private topology is omitted.

Interaction stays on the client where possible. Network writes are for progression and account events.

CSS device frames. No unverified production screenshots are published.

Tap loop Interface study — interaction surface, not a marketing screenshot dump.

Progress Interface study — guest versus account as an explicit step.

RELEASES

No versioned changelog is published here yet. Status is Live at shwetap.com.