...
- Storyboard Design 01
It's mid-morning and Robin can see that Marvin is getting quite sleepy. She sets him down in his crib and is thankful when he falls asleep right away. Robin immediately logs on to dBabies to log that baby Marvin has fallen asleep. She clicks on the "sleep" button on the side panel. Since he has just fallen asleep, all the settings have been set to the current time, so all she has to do is press submit. She sees on the schedule of events that she was supposed to try and feed him at 8:00 AM, which she failed to do. Now she knows when Marvin wakes up, he is likely to be hungry.
- Analysis:
This design aims at combining the best of the prototypes and providing the user with a UI that's learnable, efficient, safe, and prevents capture slips and common errors in UI design. The number of options is limited to the four most common tasks (e.g. feeding, putting to sleep, changing) but modular in the sense that you can add different types of events by clicking the plus box. For the log, we used used an affordance by styling the log of events after google and apple calendar. The same can be said for adding the type of event to the log. A safety feature in the UI is the multiple baby selector. Whenever a different baby is selected the color changes and the picture of the baby appears to differentiate between different infants. Also the username block is on the other end from the baby selector to prevent capture slip. In terms of efficiency, the design assumes that the user wants to keep the log updated as soon as events happen and has the time stamp set to the current time when logging an event to help the user skip the step of having to set the current time. If the user, however, wants to log the event a few hours after it happens, the user has the ability to set a different time. You can also drag and drop the events in the log to the correct time slots if a mistake is made to make mistakes reversible.
- Analysis:
- Storyboard Design 02
Before Marvin wakes up from his nap, Ted comes over to take over babysitting. Robin lets him know that she didn't feed him earlier and that Marvin should be waking up any moment now. As such, Ted starts to prepare a bottle for Marvin. Knowing that he should wake up a newborn baby every four hours for feeding, Ted gets Marvin up to feed him. As he is feeding Marvin, Ted takes out his iPhone and goes over to dBabies. He hits the homescreen and clicks on the bottle to log Marvin's feeding. While holding Marvin in one arm, he uses the other arm to mark how many ounces of milk Marvin drinks during his feeding and input the time that he started feeding Marvin. Again the current time is already input by default, however Ted is a stickler for logging things perfectly. He clicks the up button on the minute spinner to log the feeding a minute in the past when he first started feeding Marvin.
** Analysis:
This design aims at providing the user with a very mobile interface. Easy learnability is accomplished through self-disclosure (buttons with descriptive icons will be visible), consistency (icons and names are externally consistent), and fast feedback (instantaneous visible changes). The design accomplishes a level of efficiency by using large (in comparison to screen size) objects. In terms of safety, there are few errors to make and all are recoverable and revocable, e.g., an incorrect log entry can be properly edited and/or deleted.
- Storyboard Design 03
Finally, Lily gets back home to see her sweet Marvin who she has missed so very much. However, after a long day at work, she is very tired and doesn't want to have to think too much about logging all of Marvin's events. Thankfully, dBabies makes it very quick and easy to accomplish this. She logs onto dBabies and enters into Marvin's logging home page. She just changed Marvin so she drags over the diaper icons to the on-screen babies bottom. The little baby laughs and animates verifying that the event has been logged. In the process, they have run out of Wipees. Lily drags the shopping cart over to the baby to open up the "Supplies" dialog, where she marks that they need more.
** Analysis:
With a very interactive UI and using the drag and drop affordance, we believe this design to be very learnable. Additionally, we included the metaphor that you feed the baby by putting a bottle to its mouth. When thinking about efficiency, instead of having to select from menus or type anything in, all the parent needs to do is drag an item and drag it to the specific location on the baby and the code will translate that event to an event in the log. This design covers illiteracy as well. In an attempt to reach as many parent users as possible, the act of dragging and dropping different items to a baby doesn't require reading or any sort of understanding of computers. The user simply has to make the analogy. For a user who wants the less interactive version of the site, they will always have access to the log that can be edited similar to the other designs