Lyft Teen
Lyft Teen lets 13 to 17 year olds request their own rides while a parent or guardian keeps full visibility: live tracking, PIN verification, audio recording, and drivers held to a higher bar. It launched in February 2026 across more than 200 US markets.
By the numbers
- 200+
- US markets live at launch in February 2026
- 13–17
- New rider age range the platform had to support
The problem
Opening the app to minors isn't a feature you add, it's a constraint on every feature that already exists. The rider platform assumed an adult account holder throughout, so before teen rides could launch someone had to answer two questions: what a teen account actually is in the system, and which of the flows built for adults must be closed. Until those answers existed, the teams building on top were blocked.
Approach
I wrote the definition first and the code second. A teen definition document and a product feature registry gave every team one shared answer for how a teen account is represented and which product surfaces it may reach. From there the work was auditing rider flows against that registry and shutting the ones that didn't belong, treating each as a safety guardrail rather than a config toggle.
My contribution
I owned the access-control foundation: the definition other teams built on top of, and the restriction work that came out of it.
Teen definition and feature registry
Authored the definition of a teen account and the registry of which product surfaces are open or closed to one. It was the piece downstream teams were waiting on, and it became the single source of truth they built against instead of each inferring their own age rules.
Closing ride-for-others
Drove the strategy and implementation to disable requesting rides on someone else's behalf from a teen account, keeping a minor's ride tied to their own verified account. The flow it replaced had high abandonment and low conversion, which made it a clear one to close.
Restricting ride modes and upsells
Disabled autonomous-vehicle upsells and instant matching for teens, so a minor is never offered a ride type that falls outside the vetted-driver standard the product promises guardians.
Exposing restrictions to clients
Surfaced teen restrictions and date of birth through the GraphQL layer and added the fields backing teen ride monitoring, so mobile and support tooling read one consistent state.
What we built
Guardian-created accounts: only a verified adult can add a teen, who then completes a safety tutorial
PIN verification at pickup and audio recording on every ride
Live ride map, driver details, and pickup and dropoff notifications for the guardian
Drivers held to a higher standard: annual background checks, strong ratings, and road experience
Shared family payment, so guardians keep full billing visibility
Next
International Expansion
Roaming backend letting a Lyft rider request, pay for, and track a ride on the FREENOW network in Europe.
Learn more →