Try the app together
This is a disposable household demo. Everyone with this link can switch between these sample identities. No private family records are connected.
Choose a sample view to begin.
Start as Child and send a sample image. Switch to a parent, open the photo, then approve or request another image. Switch back to Child to see the result. No uploads from your phone are used.
START HERE
Small jobs.
A little more play.
Submit a chore photo, talk it through with a parent, and see the time you’ve earned.
This local preview uses separate development keys for Child, Parent A and Parent B. Keys are printed in the server terminal. These are test identities, not production accounts.
EARNED TIME
App-group minutes recorded in the ledger.
Spending on an
iPhone or iPad is not connected.
What we can see
- Device enforcement
- Not connected
- Usage, content & accounts
- Unknown
- Photo review
- Parent review only
- Device acknowledgment
- None received
Missing observations do not mean activity was safe. Existing network blocking is unchanged.
Your chores
Once per day · America/New_YorkPhoto submissions
Human review, with room to ask againEarned-minute ledger
Approval records the quoted reward once, even if a request is retried. Minutes accumulate without expiry in this preview.
Clear rules. A human decision.
- Choose a chore and take or select a JPEG/PNG photo.
- A parent reviews the visible criteria. A photo can’t prove who did a task or when.
- Approval adds the quoted minutes to your app-group balance once. A parent can ask for another photo with a note.
Always room for help
If a chore is unclear or a decision feels wrong, talk to either parent and ask for another review. No automated model judges or punishes you here.
Essential access stays separate
Communication, accessibility, medical and safety tools must stay available independently of rewards and any future recording session. This preview does not restrict any apps.
What’s still ahead
Native iOS enforcement, individual app selection, calendar allowances, location rules, usage spending, network integrations and AI assistance need separate implementation and device tests. No remote lock can be confirmed without an actual device acknowledgment.
The server must be reachable to submit or approve. No offline spending is enabled. Camera availability depends on your browser; selecting a file does not verify when it was taken. Photos are stored locally until the operator deletes the preview data.