Tatiana: Organized presentation slides, wrote report on Hackster, contributed to evaluation page on prototype and other small tasks
Ianto: Ianto kicked off the project by researching the science behind alleviating Jet Lag. He then produced the MainActivity page, had a hand in all user input screens, and developed the backend Schedule and Night objects. He then created the Schedule page, including the Agenda, and the summary bar with options menu. He then created the history list layout and adapter. He developed the larger structure of the mobile application, connecting the many activities together.
Josef: Created the sleep schedule graph, and set up the Slide Views to quickly swipe between daily schedules.
David: helped configure and design the app screens in which users input information, focusing mainly on the sleep strategy selection screen. Debugged errors in the app's input pipeline and worked on displaying time information in a human readable --:-- AM/PM format. Responsible for the wear portion of this app, making sure messages can be passed to and from mobile and wear and that reminder notifications are launched properly at the right time and under the right conditions.Problem and solution overview
Our main problem was the readability of our graph interface. During our lowfi testing, our users had a difficult time interpreting the graph. Many could not decipher what the sine curve symbolized, where they were supposed to be sleeping in relation to the graph, and what the numbers at the top and bottom corresponded to. In order to solve this problem, we will be making the interface more readable and easier to interpret. We will make labels clear and be sure that the user does not have to do much interpreting in order to understand the output of the graph. We will change the design of the sine curve so that the user understands its function. In addition, users requested that we add more information regarding our sleep strategies (melatonin and light therapy). Overall, we will clean up the design of our interfaces and add more information in order to facilitate user interactions.Tasks
Task 1 [Easy]: View history of uses: Users should be able to access their sleep strategy logs from all of their trips.
Currently, people may have a hard time remembering how well certain strategies worked for them. Our application keeps track of this easily in a simple interface.
Task 2 [Moderate]: Entering Travel Information: To understand the parameters of a user's trip and potential jet lag, our application will first ask users about the details of their trip. We need to understand the following variables:
- Origin time zone
- Destination time zone
- Day of travel
- Current Sleep Schedule
- Target Sleep Schedule
User will need to input this information for our app to perform the calculations necessary to plan out their sleep strategy. Users will go through multiple screens that present this information in an appealing way. User may google different time zones to find differences. This can be mentally taxing. In this app, the user only needs to enter in their location and destination. This task is of moderate difficulty because users may need to look up flight data. It requires active engagement, compared to passive consumption.
Task 3 [Hard]: Implementing Sleep Strategy: It will be the user's task to implement the sleep strategy that we provide. The watch will try to assist with this by providing gentle reminders of our suggested sleep, light, and melatonin schedules.
This is a very difficult task with or without this application. The application intends to make remembering to take these steps easier, but the actual task itself will still be difficult.Revised interface design
The main problem that we encountered was the design of our sleep graph [Screenshot #1]. In order to solve this problem, we have made our design simpler and more interpretable. One way we did this was by making the curve clearly denote the day and night cycle. We also plan to utilize the use of symbols of the sun and the moon in order to provide the user a with pictorial representation in our final product. In addition, we have clearly labeled the top and the bottom of the graph with “Current Time” and “Target Time” and have made the overall labels larger in order to increase readability. There will also be a shaded region on the graph that corresponds to when the user should be sleeping [Screenshot #2]. Moreover, we cleaned up the overall design of our application and changed the layout of a few screens.
In addition, users requested that we change our sleep strategy selection page [Screenshot #3]. One user preferred that we add more information regarding our strategies. Another user noted that users are forced to choose between melatonin and light therapy even if they prefer neither. In order to accommodate for this, we have added additional information that explains the two suggested strategies [Screenshots #5 and #6]. In addition, we have allowed the user the option to continue without selecting any of the options [Screenshot #4]. This way our users will be better informed on our suggested strategies and will not be forced into selecting a strategy they are not interested in.
We were able to implement all portions of our interface, so no additional sketches are necessary. Nothing was left out and no Wizard of Oz techniques were necessary. Here are our storyboards demonstrating our three tasks:
When users first launch the application, they will be directed to our homepage where they have the option to either start a new sleep schedule or view their history of past sleep schedules [Screenshot #1]. Upon selection of “Start a new sleep schedule”, users will be prompted to enter their origin and destination [Screenshot #2]. They can use the Place Picker to do so by dragging the pin to the general location of their origin and destination [Screenshot #3].
The Place Picker will then calculate the time zones. In addition, the user must enter their date of travel. After they have provided this information, they will be brought to another screen where they can enter their usual wake and sleep times in their current time zone [Screenshot #6]. We use their current wake and sleep times in order to calculate how much they should adjust each day. Next, the user is directed to our sleep strategy page where they can select either melatonin, light therapy, or simply continue [Screenshot #9].
Upon holding down one of the strategies, more information will pop up in order to provide the user with a more detailed description about its purpose [Screenshot #10 and #11]. The user can then see a summary of all their information provided so far and confirm its accuracy [Screenshot #13]. Once all this information has been collected, the user will see their generated graph that corresponds to their new sleep cycle [Screenshot #14]. The top of the graph denotes the current time zone, while the bottom of the graph denotes the target time zone. The sine wave in the middle of the graph corresponds to the day cycle. The shaded region is the time during which we recommend the user to sleep.
As the days approach their departure date, the shaded region will slowly move until the user is sleeping within his or her projected wake and sleep time in their target time zone. Users can come back to check this graph daily in order see their progress. In addition to the graph, the user will also see a recommended agenda of when to implement their selected sleep strategies. If the user returns to the homepage when they have an active sleep schedule, they will see a new option [Screenshot #15]. Upon clicking "View current sleep schedule", they will be taken back to their graph and agenda.
If on the homepage the user selects View History, the user can see a list of their past sleep schedules. Each element in the list has a brief summary of their schedule, including their past ratings. Upon clicking on each element, the user can see their destination, their strategy used (i.e. melatonin or light therapy), and the rating (based on a 5 star scale) on the effectiveness of the schedule. The rating will come from the rating page that will pop up once the user has completed their sleep schedule [Screenshot #16].
Since we acknowledge that implementing a new sleep schedule may be difficult for some users, we have implemented reminders that will be sent to the users smartwatch at various times throughout the day. For example, a reminder will be sent to remind the user to take melatonin, to get more or less sunlight, or to not fall asleep. We will be taking advantage of the smartwatch's sensors (heart rate and light exposure) in order to determine the appropriate times to send these reminders.
Although mobile reminders will also be sent, smartwatch notifications will allow the user to be continue being active throughout the day. For example, the user could be cooking when the notification is sent - a time when users would not normally have their phone close at hand. Our reminders aim to ease the difficulty of transitioning into a new sleep schedule.Prototype screenshots