As usual we will tackle this design question with keeping Goal in mind. We will then list out the personas, their use-cases, features, metrics to track, and prioritization.
Goal: Safe browsing for kids.
Personas:
- Toddler
- Young kids
- Teenagers
Use-cases:
- Education
- Browsing
- Entertainment
Solutions/Features
- Profiling: While setting up the browser the parent/authority will set the profile in a manner so that safe browsing is always enabled. Payments are automatically disabled in this profile.
- Pros: Serves the purpose
- Cons: Extra setup and some technical expertise.
- API call:
- When call is initiated from the safe profile then safe results are surfaced.
- Payment fails if the call is initiated from the safe profile. This ensures that child doesn't order digital products by mistake.
- Pros: Serves the purpose.
- Cons: Requires expertise as to which content makes sense v/s which does not.
- Notification: If weird/questionable content is requested then notification is sent to the authorities for review.
- Pros: Proactive notifications ensure parents are on top of their kids searches.
- Cons: Chances of false positive. If kids is required to do some weird searches for their biology class then it will result into false positives.
- Override for parent functionality wherein they can use the same browser for their use.
- Pros: Convenience. No need of second browser on same machine.
- Cons: Chances are kid could learn how to override defeating the whole idea.
- Reporting a summary of their kids searches.
- Mature APIs based on search results and customer satisfaction.
Metric:
- Customer satisfaction: Need to ensure that parents are satisfied with the product. And children are able to use it with ease.
- Implementation complexity: Based on customer satisfaction, we will prioritize features based on implementation complexity. High complexity features can start earlier. Features on which a lot of other features are dependent can start earlier.
Prioritization:
- Profiling as it a basic feature & API call as its part of the basic feature as must haves in MVP.
- Override is also MVP as otherwise the browser will be unusable for the parents.
- Notification, Reporting, Mature APIs can be part second release.
