...
The main content of Pack Planner is the interactive calendar which users see upon login. During the initial paper prototype designing, we experimented with many different calendar representations ranging from a strict metaphor of a calendar, to a representation so simplified it was simply a list of events. Ultimately something in the middle was chosen. The focus of the calendar is put around the week, as we found that is what users mostly focus on. On load, the current day is expanded to show a list of tiles, each tile representing an activity planned for the current day. During GR1, interviewees said that they most often look at their calendar to quickly remind themselves what needs to be done on the current day, so we made our interface cater to this quick current day view. Users can navigate easily within the week by clicking the vertical tile for a given day, or use the previous/next day buttons at the top. Furthermore, the mini cal on the left hand side of the screen allows a user to more efficiently navigate to a day that may be further in the future, or simply help the user by alleviating the need to recall the structure of the given month.
Within the current day, Tiles are listed to show all the events of a day. This is where the simplicity of the interface shines. Instead of trying to show complicated timelines, a simple ordered list is used to display the tiles. Furthermore, each tile is color coded to give the user the best information scent as to the plans of each family member. The tiles are specifically designed to help parents arrange the driving to and from their children's events. In the middle of the tile are three buttons, a 'driving to' button and a 'driving from' button with a button in the middle with a car symbol on it. The 'driving to' and 'driving from' buttons are used to quickly assign drivers, or give the user a chance to reach out and ask a contact to drive. These 'driving to' and 'driving from' buttons are turquoise, the main color of the interface, when a driver is assigned. However when a driver is not assigned, these buttons are red to draw the users attention. Because of the simplicity of tiles, it is difficult to give the user a good idea of when two events overlap. However, the user should most often care if events overlap, only when driving must be coordinated. So by utilizing the harsh red on the 'driving to' and 'driving from' buttons, the same goal can be achieved as the user's attention is attracted to events which do not have an assigned driver.
Modals are used across this interface to minimize the number of screens, thus simplifying the user's mental model. The biggest challenge with the modals, particularly the event creation and editing modals, was creating efficient inputs for all fields. For simple fields like title and location, typing into the tex text box is all the user needs. But inputs which must be structured, such as time or date, are more difficult to implement safely and efficiently. Ultimately, a date time picker was utilized for these fields, however some issues were encountered by using these input methods. To improve overall interface, this is the first place improvements should be made as it is most confusing and possibly harmful. Lastly, when assigning drivers in the modals, type ahead was utilized to make the process more efficient. The reach out modal was designed to quickly and efficiently reach out and ask friends to drive for an event. The reach out modal can be accessed by clicking the middle car button on a tile, or by clicking "reach out" within the drop-downs of the 'driving to' and 'driving from' buttons. This modal is a list of the user's contacts, each contact is clickable which checks a box next to the user's name to indicate they have been selected. After a user selects as many users as he or she wants, the user clicks "send driving request" and all those checked will receive a message asking for availability to drive for the desired event. The simplicity of this modal increases the chance of a user finding a friend to help drive as it enables the user to ask more friends by lowering the barrier to request help.
Lastly, the contacts page utilizes a simple design to give the user the basic functionality needed to intact with others within Pack Planner. The contacts page acts as a user's physical contact book would. There is one entry per family, and when the entry is clicked, information is displayed on the right pane to show the family details including the parents' names, the children's names, and other useful information like email address and street address. From the contacts page, a user can send a message to a contact, perhaps just to communicate about an upcoming event, or to plan a carpool. Furthermore, a "find friends" button is present to search for the user's other friends which may have recently signed up for pack planner.
...
All users liked the calendar representation of the application.
- Change of color when once driver assigned within event tile (Color coordination)
...
Potential solutions and Moving forward
...
The use of colors to represent children specific events and the status of assigned drivers gave immediate feedback and satisfaction. Users saw the uses of the application very beneficial, especially for reaching out to other parents/neighbors/relatives to carpool and schedule events. Navigation within the calendar view seemed easy and simple. The use of multiple affordances added to the ease of navigation. Layout was clean and a tabbed toolbar made finding sections more intuitive.
...
Potential solutions and Moving forward
...
Most of the problems resulted from the non-accustomed layout of representing a calendar in the application. Users were more familiar with large calendars with days represented as blocks rather than vertical tabs in a weekly view. Perhaps an option to view a normal calendar may be more helpful. Users also expressed their thoughts and aesthetics and functionality. Images of cars did not make it seem intuitive they represented reaching out to other potential drivers. When selecting drivers or contacts, there was no highlighting so not exactly sure if selected. Also, color scheme of filters for children within and event seemed arbitrary. Potential solutions would be to add help and documentation to the application to help guide users. Also, it may be helpful to add the option of customizing the skin of the calendar and/or colors to filters to make it fit user appeal. Most of the problems resulted from the non-accustomed layout of representing a calendar in the application. Users were more familiar with large calendars with days represented as blocks rather than pages on a
There were also some latency, error handling
...
issues. This could be due to the default settings on the backend/frontend used. There were noticeable issues with input for events and time. Refreshing a page can be jarring as it shifts to
...
the current day. A solution may be to go back to some "hacky" solutions to the code and make it more clean.
Reflection
We learned a variety of things about the design process in this project:
- The need for user testing became salient. There were various quirks about our system that were immediately apparent to usour test users, but which weren't quite as obvious to our test usersus, and we wouldn't have been able to catch this without user testing. Since we are all familiar with the mental model of our design, it's easy to overlook things that may be difficult to understand to outsiders.
- There is a lot of value in sketching out and designing the object models and relationships before beginning implementation. Some of the relationships between objects in our system aren't always that obvious and have some quirks. A lot of time and grief could have been avoided if we had sketched out in full detail all of the different models, their properties, and their relationships to each other, before beginning implementation. To provide some examples: Each person has a user account. Each user account has an associated family member profile, which belongs to a family. Event details belong to a family (so all members in the same family see the same calendar) but there can be multiple event details (including drivers and such) associated with each event (to permit sharing). None of this is necessarily particularly convoluted, but it would've made development much simpler for all parties had we hashed out these models and relationships beforehand.
- As is often the case with most projects, one starts off very ambitiously, and when it comes time to implement and meet deadlines, it becomes really obvious really fast that one won't be able to implement the feature set one desires and needs to scale down. It would have been good, from the start, to begin with a much simpler product with less features (yet still satisfying the core necessities) and scaled up from there if time permits. Having a few too many features left to our engineering efforts becoming spread too thin, with many features not being as polished as they could be. This may also be a consequence of simply the problem we chose to tackle, which would necessarily have required a diverse set of features. Thus, there may have been some value in being more critical at the early stages of which problem we wanted to tackle, and pick one that intuitively might not require a solution with a large amount of functionality.
- In terms of choosing which technologies we work with, though this shouldn't be central to the project, it has a large effect on the amount of time required to complete various tasks. General unfamiliarity with the various technologies used (Django/Postgres/HTML/CSS/etc...) meant that completing relatively simple tasks would take a fair bit of time since one would need to constantly consult the documentation. Not really something we could have done much about, since we picked technologies we were most familiar with, but it couldn't have hurt for our members to have had more experience in them to begin with.