FamTrack - Sell Project

Project details

Website: https://appetize.io/app/b_cedvs45ageo6yo6rei24svxahq

Video 1: https://youtube.com/shorts/XTZF_Ka8CvE?si=77kGijs7ZmT13Ld3

Next step: <p>Everything below is suggested direction. None of it is built into the package, so describe it as a roadmap, not a feature. It's ordered by how much value each step adds.</p><p><strong>1. Before launch: close gaps in the current app</strong></p><ol><li data-list="bullet"><strong>Password reset and email verification.</strong> Both are missing, and users will lock themselves out.</li><li data-list="bullet"><strong>Move </strong>allowedWatchers<strong> into a Cloud Function.</strong> Today the owner's phone maintains it, so it's the weakest trust point. A server trigger on consent changes makes revocation airtight and works even when the relative's phone is offline.</li><li data-list="bullet"><strong>Live map.</strong> MapActivity reads the location once. Firestore snapshot listeners would make it update in real time.</li><li data-list="bullet"><strong>Offline handling.</strong> Writes made offline currently wait with no feedback.</li><li data-list="bullet"><strong>Add tests.</strong> Unit tests, plus Firebase Emulator tests that check the security rules (self-approval is blocked, and so on).</li><li data-list="bullet"><strong>Crash reporting and App Check.</strong> Crashlytics catches production crashes and App Check blocks abuse of the Firebase project.</li></ol><p><strong>2. Product features (1–3 months)</strong></p><ol><li data-list="bullet"><strong>Circles and roles:</strong> family groups with admin or parent roles, instead of one-to-one requests.</li><li data-list="bullet"><strong>Place alerts:</strong> geofences such as "arrived at school" or "left home", sent as push notifications.</li><li data-list="bullet"><strong>Location history:</strong> a route trail for a limited time, with a retention setting. This is the natural paid feature.</li><li data-list="bullet"><strong>Smarter battery use:</strong> update more often when moving and less when still, using Android's Activity Recognition API.</li><li data-list="bullet"><strong>More alerts:</strong> low battery, phone shut down, and an SOS button.</li><li data-list="bullet"><strong>More sign-in options:</strong> Google sign-in or phone-number login.</li><li data-list="bullet"><strong>More languages:</strong> the app is already set up for them.</li></ol><p><strong>3. Platform and business (3–6+ months)</strong></p><ol><li data-list="bullet"><strong>iOS app</strong> using the same Firestore schema and rules. The backend needs no changes.</li><li data-list="bullet"><strong>Web dashboard</strong> (React) for organizations, school transport or elder care.</li><li data-list="bullet"><strong>Subscriptions</strong> through Google Play Billing: free basic sharing, paid history and alerts.</li><li data-list="bullet"><strong>Client-side encrypted locations</strong>, so even the operator can't read them. It's a strong selling point for a privacy app.</li><li data-list="bullet"><strong>Commercial map tiles</strong> before any large launch, because OpenStreetMap's free servers aren't meant for heavy traffic.</li></ol><p><strong>4. Engineering quality</strong></p><ol><li data-list="bullet">Move to MVVM with ViewModel and Flow, then Jetpack Compose.</li><li data-list="bullet">Add CI/CD (GitHub Actions) and automated Play Store uploads.</li><li data-list="bullet">Add data export and GDPR/CCPA tooling.</li></ol><p><strong>Things the buyer must not skip when growing</strong></p><ol><li data-list="bullet">Keep the consent step, the sharing notification and the in-app disclosure. They protect Play approval and the app's reputation.</li></ol><p>If they add child accounts, Google's Families policy and children's privacy laws apply. Get legal advice first.</p>