Version limitations (MVP expectations)
MVP exclusions (unless added later)
- [Fact from product-brief] Full wearable integration ecosystem.
- [Fact from product-brief] Live streaming to public audiences.
- [Fact from product-brief] Automated officiating or line calling.
Positioning (non-goals)
- [Fact from product-brief] Not replacing professional coach judgment as the sole technical feedback.
- [Fact from product-brief] Not a full league/tournament operations platform unless expanded later.
- [Fact from product-brief] Not a generic fitness-only app without tennis-specific workflows.
Other constraints
- [Fact from product-brief] Device cameras — quality/placement vary; ML depends on capture conditions.
- [Fact from product-brief] Privacy — video and biometric-adjacent processing may need consent flows by jurisdiction.
- [Fact from product-brief] Offline / connectivity — on-court connectivity may be limited; sync strategy TBD.
- [Unverified] Session and event persistence — creating a session from Today (New Session flow) may not persist or sync across devices until backend/API contracts ship; do not assume multi-device sync without release documentation.
- [Unverified] Location model — minimum viable Smart Court location model (venue database vs user-created pins) is an open question in
product-brief.md; Select Location and related UI may vary by release.
Manage expectations
- [Unverified] Roadmap dates and feature gates — not in product brief.
Related