This week, the team developed a technical storyboard for the lo-fi prototype. The prototype chosen scenarios was the ‘My Information’ option and the ‘Diagnosis’ option; which enables us to demonstrate more then one basic feature of the app. As you can see in the image above, the storyboard is all over the place with arrows showing interactions between each screen of the app. Let’s break this down step-to-step.
Step One: Home screen.
So this is a basic example of the Thick Ice home screen. The user has a variety of medical categories to choose from including viewing their personal information and a ‘Diagnosis’ option. The options are intended to be used by both the app-owner and a second party user, in case the app-owner is unable to use the app. For the purpose of the lo-fi prototype we will enable both the ‘My Information’, ‘Diagnosis’ and ‘Medical Condition’ options. Let’s say the user selects the ‘My Information’ category by tapping the option on the screen. This loads the ‘My Information’ page.
The My Information page displays the app owner’s medical information. The information displayed on this page is listed as follows:
- Known Conditions;
- Blood Type;
- ICE contact;
- Medical Insurance Information;
- Organ Donor?; and
- Extra Details.
On the right hand side of the Known Conditions details, there will be an information button. This brings me to discussing the next step.
For the purpose of this storyboard, we’ve selected the app owner to have Epilepsy. When the user touches the information icon next to the medical condition, a pop-up window will be displayed listing the information about the condition (i.e. Epilepsy). The information included will be:
- Symptoms; and
From this page, the user can navigate back to the home screen.
In the case of a situation where the user is unsure of the category of the injured person’s injury, they are able to select ‘Diagnose’ from the home screen.
The diagnose screen is an expert system which is basic Q&A for the user. One question will be displayed at a time at the bottom of the screen, and once answered will be listed at the top of the screen. The older the question the smaller the text, so the list of previously answered questions will appear to be similar to the star wars credits. This enables the user to view their previous questions and also to avoid confusion as to which questions they have answered and need to answer. Once all the questions have been answered the expert system will load the Diagnosis page.
The Diagnosis screen will be a similar layout to the Medical Conditions screen; however the user will use the expert system to access it rather than selecting a condition from the Medical Condition list. The user can then navigate back to the expert system and view their answered questions, or navigate back to the home screen.
Now let’s discuss technicalities.
The preferred prototype will be an Android SDK developed app; however the prototype may be made in a web version. Worst case would be the lo-fi prototype being on paper, and filmed to demonstrate the user interactions mentioned above. The final product will be an Android App with information, categories and diagnose completed. This app is technically achievable and the prototype will commence development this week to meet INB386 project deadlines. A lot of research will be required on behalf of the development and graphic design team members to ensure they are equipped to develop the Android SDK app prototype, or the web version prototype. The expert system is the main focus due to the technical aspects required for the system to function correctly in the Thick ICE app. This is expected to take up most of the development time.