Choose the device ecosystem first, create the child’s own account, configure the few controls that shape daily use, and schedule a review before handoff.
Why this decision matters
A first phone combines identity, purchases, communication, browsing, location, school use, and family expectations. Treating those as one setup project prevents contradictory settings and makes later changes easier to explain.
A practical starting sequence
Choose the correct account foundation
Use the child’s own Apple or Google account inside the family system. Do not hand over an adult’s signed-in account.
Decide the day-one experience
Set who can contact the child, how downloads are approved, when the phone rests, and which school or transport functions must always work.
Test and review
Have the child make a call, request an app, open an allowed site, meet a time boundary, and find the charging place. Review after real use.
What the child experiences
Your child should know what happens when an app, purchase, website, or extra-time request is blocked—and which adult will respond. Predictability matters more than an invisible maze of restrictions.
Configuration can reduce accidental access and make decisions visible. It cannot judge every message, prevent every risky interaction, or replace an ongoing conversation.
When to review it
Review after the first week for broken essentials, after 30 days for recurring friction, and whenever school needs, maturity, or the device ecosystem changes.
Start with the free pre-handoff checklist
Make the 12 key decisions before opening every settings screen.
Current official sources
Interfaces and defaults change. These first-party sources were checked for this page; verify the live device before publishing or relying on an exact menu path.
- Apple: How Family Sharing works
- Apple: Use Screen Time for a child
- Google: Set up parental controls with Family Link
- Google: Sign a child into an Android device