On the readme we have a non-technical people friendly version of it.
Make the application available offline.
According to our product owner clinic's often have dodgy/ no internet connection. During the graduate project we would build it to be a progressive web app, so it can work without internet connection.
Use an IndexDB database
For the design print we stored our data in a simple JS object, since we only had the 6 most frequently asked questions for the three treatments. However, our product owners have an extended list of questions (~30 more questions). If wwe have the chance to work on this project for a month, it would worth to use a database.
During the design sprint, we hand client side templating for the cards. We had 3 templates, for different scenarious (the answer is different for every treatment options, the answer is same for 2 of the options (2 variations of this)).
Use partials for Navbar,too.
Implement feature in Q&A guide to save questions and answers to be discussed later.
According to our product owners clinicians use decision aids/ grids, where the patients can circle (manually with a pen), which questions they are the most concerned about, and later they can further discuss these questions with the clinican.
The save questions for further discussion would modernize this process.
Collect statistics about most frequently saved questions.
Our product owners have spent months on collecting the 6 most common questions that people ask about the treatment options. The real product would include the extended list of questions (~40), and it could be a valuable information for later research studies, if we can keep track of the most commonly asked questions.
Bring the talking and medication illustrations to life in animated form, to complete the interactive section of the site.
Add the animations.
Pay attention to browser compatibility
According to our product owners, most of the clinicians use Internet Explorer. We developed the MVP using Chrome, and didn't focus on browser compatibility. E.g. we know some of the features don't work on Safari. During the graduate project, we should and we will focus on browser compatibility from the start.
Feel free to edit it, to add anything you want!
On the readme we have a non-technical people friendly version of it.
According to our product owner clinic's often have dodgy/ no internet connection. During the graduate project we would build it to be a progressive web app, so it can work without internet connection.
For the design print we stored our data in a simple JS object, since we only had the 6 most frequently asked questions for the three treatments. However, our product owners have an extended list of questions (~30 more questions). If wwe have the chance to work on this project for a month, it would worth to use a database.
We would use IndexDB, because it is suitable for progressive web apps . (short intro)[https://medium.com/dev-channel/offline-storage-for-progressive-web-apps-70d52695513c#.eiji3snrf]
During the design sprint, we hand client side templating for the cards. We had 3 templates, for different scenarious (the answer is different for every treatment options, the answer is same for 2 of the options (2 variations of this)).
Use partials for Navbar,too.
According to our product owners clinicians use decision aids/ grids, where the patients can circle (manually with a pen), which questions they are the most concerned about, and later they can further discuss these questions with the clinican. The save questions for further discussion would modernize this process.
Our product owners have spent months on collecting the 6 most common questions that people ask about the treatment options. The real product would include the extended list of questions (~40), and it could be a valuable information for later research studies, if we can keep track of the most commonly asked questions.
Add the animations.
According to our product owners, most of the clinicians use Internet Explorer. We developed the MVP using Chrome, and didn't focus on browser compatibility. E.g. we know some of the features don't work on Safari. During the graduate project, we should and we will focus on browser compatibility from the start.