Skip to content

Let a parent using the app for their own phone stop being asked about a child's - #55

Merged
jsconu merged 1 commit into
mainfrom
feat/own-phone-only
Sep 23, 2026
Merged

jsconu merged 1 commit into
mainfrom
feat/own-phone-only

Conversation

@jsconu

@jsconu jsconu commented Sep 23, 2026

Copy link
Copy Markdown
Owner

For someone using the parent app only to limit themselves, the dashboard kept nudging towards a child's phone.

  • "I'm only using this for my own phone" on the "Setting up a kid's phone" card hides it, and rewords the passcode prompt and status-icon note for one's own phone.
  • Passcode prompt gets "Not now"; the passcode itself stays under ⋮ → Passcode.
  • Reversible: while hidden, ⋮ shows Link a kid's phone. A phone that's actually linked always shows its card.

Local build only; cloud's "Add kid" is unchanged. Stored in a small HouseholdPrefs on the phone.

🤖 Generated with Claude Code

… about a child's

The dashboard assumed a child's phone was coming: a card about setting one up,
a passcode prompt explained in terms of "your kid's phone", and a note that
"your kids' phones show these same icons". For somebody using the app only to
limit themselves, that is a permanent nudge towards something they are not
doing.

"I'm only using this for my own phone" on the kid card puts all three away. The
card disappears, and the passcode prompt and status-icon note are reworded for
one's own phone. The passcode prompt also gets a "Not now", since it is a
suggestion rather than a requirement, and the passcode itself stays in the menu.

Neither choice is a way to lose anything. "Link a kid's phone" appears in the
menu while the kid card is hidden, and a phone that is actually linked always
shows its card - hiding a real child's usage would be worse than the nudge.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@jsconu
jsconu merged commit f3494ec into main Sep 23, 2026
2 checks passed
@jsconu
jsconu deleted the feat/own-phone-only branch September 23, 2026 13:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant