1. On-boarding
1.1. GIF (Feature overview)
1.1.1. Sign up flow
1.1.1.1. More interactive (cool interactions / UI components)
1.1.1.2. Sequential / Step wise
1.1.1.3. Locations
1.1.2. Login flow
1.1.2.1. Social login (FB, G+)
1.2. Connecting a Kito+
1.2.1. Sequential / Stepwise
1.2.2. Indicative
1.2.3. Get rid of "Pairing" concept / Associated animations
1.2.4. Make this snappier
1.3. Tutorial Flow (First use)
1.3.1. Planning transitions + motion graphics
1.3.2. Overall flow itself (what are you really showing?)
1.4. Sandbox (First Use)
1.4.1. How long should this really be?
1.4.2. What should you not show?
1.4.3. When should this end?
1.4.4. Teaching them to keep still - both ECG and SpO2
1.5. Troubleshooting
2. Design Related
2.1. Typography
2.1.1. System fonts with support for accessibility
2.1.2. Design for old people to begin with
2.1.2.1. use clear sans serif fonts
2.1.2.2. use slightly larger fonts
2.2. UI - Android vs iOS
2.2.1. More native feel
2.2.2. Platform specific UI controls
2.2.3. Works everywhere
2.3. Design patterns
2.3.1. Sliding drawer
2.3.2. Cards (dashboard)
2.3.3. Journal / Vitals (cards or something contemporary)
2.3.4. Tabbed view on the main screen (dashboard + vitals)
3. Data Visualization
3.1. Vitals over time
3.1.1. Simple, meaningful data aggregation over time
4. New Features
4.1. Document catalog
4.1.1. Catalog photos of medical documents (lab results etc.)
4.2. Paid readings
4.2.1. Being able to pay to have one of your vitals read by a cardiologist
4.3. Learn about Kito+
4.3.1. Tutorial
4.3.2. Sandbox
4.3.3. Videos
4.3.4. Tips & Tricks
5. Main screen
5.1. Checkup flow
5.1.1. The UI to begin check up needs to be more indicative of what the person has to do (i.e. turn on Kito+ using the button on the device)
5.1.2. "Push to start" style experience to initiate check up flow
5.1.2.1. When we're on the main screen and the user presses the ON button, connect to the device and start the checkup flow
5.1.2.2. Take care to handle edge cases gracefully (e.g. low battery, connection failure etc)
5.1.3. Core measurement experience needs to be indicative of finger movements - Live feedback
5.1.3.1. ECG vitals quality meter
5.1.3.2. Written prompts for SpO2
5.2. Dashboard
5.2.1. What does it show?
5.2.2. Empty states?
5.2.3. Initial content (after first use, after first week... etc.)
5.2.4. Indicators (low battery)
5.2.5. Trends that we can identify?
5.2.6. What questions do you ask that might have meaningful results for a user?
5.2.7. Inputs (or meta data)?
5.2.8. Reminders
5.2.8.1. User set
5.2.8.1.1. Strategic reminders (auto generated)
5.2.9. Dynamic content? (Variety over volume)
5.2.10. Personalization?
5.2.10.1. Can we use the Fitbit data a little better?
5.2.10.2. How do they compare to other Kito+ users?
5.3. Vitals / Journal
5.3.1. Currently there's no way for a user to highlight or mark a reading as important for easier filtering. Fix this
5.3.2. It might be cool to have a feature where in the user has the option to add a few notes or even take an audio recording around symptoms, signs, or what they might be feeling
5.3.3. It might be useful to "geotag" the readings so we can understand patterns. Again, some users might not want to enable location access
5.3.3.1. This is not the same as the "locations feature" in settings (home, doctor's office, pharmacy etc.)
5.3.3.2. This is only to provide more meta data while grabbing the reading and allow for more refined filtering options
5.3.3.3. How do you handle a set of readings - some geotagged, others not ?a
5.3.4. Develop a part of the app that allows the user to set thresholds for the various vitals in consultation with a doctor
5.3.4.1. You could give alerts after vitals are measured if these thresholds are exceeded
5.3.4.2. These could also feature in the data viz in some form
5.3.4.3. These could also be a way to mark readings as important
5.3.5. The vitals journal is too plain right now and lacks filtration tools. Can we build a UI that allows users to filter specific readings based on specific criteria?
5.3.5.1. Important readings
5.3.5.2. Readings where thresholds were violated
5.3.5.3. Readings where location is "X"
5.3.5.4. Readings where HR is between 60-85 etc.
5.3.5.5. Filter based on custom text in notes / symptoms?
5.3.6. We'd like to add a feature where the user may manually enter readings from a Blood Pressure cuff and a Glucometer
5.3.6.1. Manual text entry
5.3.6.2. Use camera and computer vision to auto detect the numerical values
5.3.7. Sharing vitals via email
5.3.7.1. "Share this reading"
5.3.7.2. "Share multiple readings" based on filters or manual selection
5.4. Sharing readings
5.4.1. Sharing - in app
5.4.1.1. via email id
5.4.2. Creating a web app for viewing shared data
5.4.3. Accessibility / Visibility controls (allow access for X days etc.)
5.5. Settings
5.5.1. Temperature units
5.5.2. Security lock
5.5.2.1. Can we redesign the security lock to be more functional? Nobody wants to type their whole password. Use pin / pattern lock instead
5.5.2.2. Security blanket covers the screen when multitasking
5.5.3. Share settings
5.5.3.1. Mailing list
5.5.3.2. Recipient history (autofill suggestion?)
5.5.4. Levels & Thresholds
5.5.4.1. Create a UI that allows users to setup thresholds for the various vitals
5.5.5. Locations
5.5.5.1. Home
5.5.5.2. Doc's office
5.5.5.3. Preferred pharmacy
5.5.6. Reminders
5.5.6.1. Location based?
5.5.6.2. Periodic reading reminder
5.5.7. Fitbit integration
5.5.7.1. Improve it in some way (e.g. Workout calendar!?)
5.6. Users
5.6.1. add upto 5 other users
5.6.2. manage user switching more gracefully
5.6.3. Get photos of the users
5.6.4. Simpler flow for signing additional users (not the primary user)
5.6.5. Guest mode
6. Errors + Explanations
6.1. Connectivity to Kito+
6.1.1. When checkup begins
6.1.1.1. Bluetooth - off
6.1.1.2. Can't connect to Kito+
6.1.2. While the reading is ongoing
6.1.2.1. Fingers moved (not handled like errors)
6.1.2.2. Bluetooth connection lapses while reading is ongoing (rare, but its known to happen)
6.2. Battery and Power
6.2.1. Kito+ is completely discharged and the app can't even figure out if its turned on (solve using visual inspection)
6.2.2. low battery warning (<15%)
6.3. Identity related
6.3.1. Logging in / signing up etc