search

minakhan01 / RL_app

0 stars 0 forks source link

Design + development considerations #1

Open minakhan01 opened 3 years ago

minakhan01 commented 3 years ago

Mental model for user input

  1. Future Preferences (initial settings) Timings a. calendar breaks (allow users to add their calendar. maybe they don't have to add their breaks to the Google calendar, but they can add it to the calendar view in our app so that their breaks are private, yet integrated with their calendar) b. interval-based breaks c. adhoc breaks Messages: enter a custom message Break Duration

  2. Current Preferences a. before break -us asking the user to take a break -user indicating that they want to take a break (without us asking) b. during break -break duration countdown, break custom message, minimize break window, (break animation: optional) c. after break -feedback after break: how helpful was the break?

  3. Past Preference (+self-tracking and visualization on our custom calendar view) a. show users the breaks they have taken -things to consider: how to recognize breaks? let users add break activities, e.g., netflix, etc b allow users to indicate on the calendar what breaks they would have liked to avoid c. allow users to indicate on the calendar what breaks they would have liked to add

minakhan01 commented 3 years ago

Development considerations:

a. Activity tracking app (phone+desktop): https://activitywatch.net/ b. The app will run "offline" on the Desktop c. The app will interact with a python back-end for RL

Older UI sketches: a. https://invis.io/53ZT86QQ27Y (old) c. https://projects.invisionapp.com/share/TUZFY1845JC#/screens/439119347 (older)

minakhan01 commented 3 years ago

Development features: Let's plan this two-week development timeline. Please consider the above to plan the development.

  1. [ ] Future Preferences Settings Screen - Basic screen

  2. [ ] a. calendar breaks (allow users to add their calendar. maybe they don't have to add their breaks to the Google calendar, but they can add it to the calendar view in our app so that their breaks are private, yet integrated with their calendar)

  3. [ ] b. interval-based breaks

  4. [ ] c. adhoc breaks

  5. [ ] Messages: enter a custom message

  6. [ ] Break Duration

  7. [ ] Logic to calculate break times based on initial preferences

Current Preferences Interface a. before break

  1. [ ] us asking the user to take a break

  2. [ ] user indicating that they want to take a break (without us asking) b. during break

  3. [ ] break screen: duration countdown, break custom message, minimize break window, (break animation: optional) c. after break

  4. [ ] feedback after break: how helpful was the break?

  5. [ ] Saving all the above info - Database

  6. [ ] Calendar View for Past Preference (+self-tracking and visualization on our custom calendar view)

  7. [ ] a. show users the breaks they have taken and allow them to label the breaks that took, including specific activities -things to consider: how to recognize breaks? let users add break activities, e.g., netflix, etc

  8. [ ] b allow users to indicate on the calendar what breaks they would have liked to avoid

  9. [ ] c. allow users to indicate on the calendar what breaks they would have liked to add

[TODO: for @crimsontrigger ]