Page History

Paul drops off Chuck; Dan signs Chuck in

The child selection page is an easy tiling of "entries" of different children that Dan has control over. Each entry contains a checkbox that toggles whether or not a given child is presence right now. The question, "Who's Here?" is informal, conversational, learnable, obvious, and understandable, and Dan understand what it means and chooses to select all the children that he sees at any point in time.

To enhance the usability of ChildFeed, each time the "Who's Here" screen is loaded, the entries are sorted such that the kids who are "here" appear first, followed by kids that are not here. This makes it easier for Dan to see both kids who are here and not and check them on or off.

Patricia checks the account; sees notification of Chuck being dropped off

Patricia checks the account on her tablet and sees the latest feed items. One of these news feed items is a "drop off" action that indicates that Chuck was safely received by Dan the Daycare Worker.

Dan shares photo story of Chuck finger painting

The conversational layout is obvious here. The dialog attempts to flow naturally and extract the needed information from Dan through the questions it asks.

Dan can indicate who is there by typing into the text box and benefiting from Autocomplete (in a manner similar to that of the "To:" field in GMail, Hotmail, etc.). However, Dan can also click on the "+" icon next to the textbox, where a Child Selection modal/page pops up and allows Dan to select the relevant children for the story.

*Note that the "publish story" button should say "share story".

Patricia checks the account; sees notification of Chuck's new story

Now being at her workplace, Patricia checks the account from her laptop, on a bigger screen. This allows her to see more information on the stories, and sidebar information with the latest report about Chuck from the previous day, and some of his eating habits history.

Dan and his coworkers go through the children in his ChildFeed app, logging what they all ate and how much they ate

Dan achieves this by listing the meals provided in lunch. This is done by clicking on the "Add other meal..." (or "Add meal...") text box, which makes it an active item. Pictures can be added to each meal, also.

After information on the meals provided is entered, Dan needs to tell ChildFeed how did everyone eat. Dan can choose not to answer the question by clicking on the checkbox next to a child's name, to deselect that child from the report operation.

Dan answers questions for each child, by selecting what that child ate from a dropdown box (which Shift+Click can be used to select multiple meals), and a slider to indicate how much the kid had to eat. This slider is labeled by "Too little" "Just Right" and "Too much", but with the ability for the slider to go smoothly anywhere on that scale.

The app also leaves a space for text comments. This is shown by the "Comments" label on the child tile, with a clipped part of a textarea underneath it. This has the affordance of a textarea and behaves like one when hovered over. Upon getting focus, the tile floats over the screen (while remaining in its own position) and expands to show the entire textarea, allowing the user to enter data there. Upon losing its focus, the interface returns to its previous state. One done, Dan will publish this information.

Paul and Patrica notice that Chuck did not eat much today, and go back to check his eating history, and notice that he doesn’t eat very much whenever they serve macaroni and cheese

The history view shows a graph history of different trends that are selected from the right-hand-side bar. The trends that are selected are the same as those entered in the daily report or food report, and include any value or metric that is decided with a slider in this design.

Hovering a certain trend line point will result in a floating message popping up that describes the relevant activity at that point in time. For example, hovering over a point on the food trend line will tell the parent any comments Dan had on that day, as well as what the child ate on that day.

For this example, Paul and Patricia look at the low points in the food trend line and hover over all of them, noticing that Paul always eats less when macaroni and cheese is being served, and thus arrive at this conclusion.

Dan puts all of the kids to sleep and sits down and logs information about each child’s mood, temperament, overall energy, etc.

Dan's daily report is a simple tile of user information with sliders and comment boxes as described for the lunch entry.

Patricia checks ChildFeed for overall information on Chuck’s wellness and notices that he is not in a very good mood

Patricia views the daily report screen for today's date. She can see a wealth of sliders indicating Chuck's mood today, as well as stories that involve Chuck that took place today, and any additional comments given by Dan. Different trend lines also show in the sidebar (if viewed from desktop), with today's settings visible and thus easily comparable.

The mobile UI to view the daily report is also shown in the bottom part of the image.

Patrica picks Chuck up; Dan signs him off

Dan will deselect chuck to show that he has been picked up by his parents.