+ User can browse 5-8 instructional videos in their
category of exercise and play them.
+ Video list and videos are downloaded from a
server on-the-fly so that content can be updated at any time.
+ App will keep a record of each time a video is
viewed by the user
+ While a video is open, the user can tap “Start” to
begin recording their health data
+ App will either collect and send accelerometer data
from the device, or wait until the end of the workout and query for
data from a connected FitBit / Apple HealthKit device (Apple Watch,
maybe others? difficulty of setting up Apple Health / FitBit
accounts could be a concern.) to verify the user’s effort.
+ User will be presented with a “congratulations,
your activity has been recorded” screen that shows them moving up
in the leaderboard / receiving points / other gamification
reward.
+ User can see the number of days they’ve logged
activity, and see a leaderboard showing how they compare to others
in their category of exercise.
+ User can view recent messages from the team,
and subscribe to push notifications for updates (?)
+ User can log out / reset their password
API & Administration Website
[30-40 hours]
+ API for the iOS app
+ Fetch user information
+ Fetch video list / videos
+ Fetch workout history
+ Submit new workout (start / stop time &
accelerometer data)
+ Doctor can sign in on the web
+ Doctor can see the users of the app in a list
showing:
+ Name
+ Category of exercise
+ Total workouts performed
+ Time last workout performed
+ Other quantitative metrics TBD
+ Doctor can invite a new participant to
join
+ Creates an account for the participant and sends
them an email with instructions to install the app
+ Collects health information, chooses a category of
exercise for the participant
+ Doctor can view and edit calendar events /
reminders shared with participants. (For this, we’d most likely
just embed a Google Calendar editor inside the admin
dashboard.)
+ Doctor can export a chronological list of all
participant workouts in CSV format
+ Doctor can export participant’s raw fitness /
accelerometer data in CSV format
QA, Testing, App Store
Release [10]
Deployment [10]
Because the app associates health data with users it
might be necessary to deploy it in a HIPPA-compliant environment.
When I’ve worked with healthcare startups in the past, this has
boiled down to “transport data securely and encrypt it at rest”,
which is fairly standard and just takes a bit of extra time to set
up. Since the app has such a small number of users, the cost of
running the API / Admin website should be very small (< $40 /
month).