Design Requirements
Using two different classification categories: Action, Object, Context, and Data, Functional, Contextual, we came up with design requirements that were integral to the purpose of our application. We created our design requirements from our research to properly address the wants and needs of our users. The design requirements were used to generate ideas that could be used in our storyboards and final design.
Takeaways
-
Single parents needed a way to effectively communicate with their support groups
-
Single parents needed a design that could coordinate schedules with the support group
-
Single parents needed a way to request assistance when they needed help
Storyboards
Each member of our team created storyboards to help visualize potential design solutions that could be integrated into our final product. Our team used storyboards to explore the different potential applications for our mobile app Parents United. These visual scenarios gave us the chance to compare different key aspects of our mobile app while helping us determine which functionalities we wanted to incorporate into our final design.
Takeaways
-
Storyboards explored different possible functionalities of our mobile app design
-
Storyboards presented visualizations of the designs our team thought would be beneficial to our final product
Information Architecture
Our application aims to make communication between single parents and their support system more efficient. Two user groups are involved; the single parents and support members. The information architecture shows the features of the two user groups. After receiving feedback, we made several changes to the information architecture.
Takeaways
-
We got rid of the dashboard and made a navigation bar so that the user can access different feature more easily.
-
We linked the "Edit Event" to "Create Request" so that the user can create help request in both ways
