Project Quote: C-CART Baycrest Caregiver Resource Mobile App

Background

C-CART Assessment Tool - Demographics

Key questions and considerations

Information architecture sets the tone

For us to quote based on where we expect you are, we would like to see the overall information architecture of each of the questions and how the variances between them lead to outputs from the system (ie, what resources will be recommended) and also what the output entails. ie, what is the list, how long are they, how are people supported in prioritizing their engagement with the amount. These are all areas that should be designed to improve engagement, action, and reduce cognitive load.

• If this information architecture doesn’t exist, we would like to map this logic out as a priority for the project so this can be validated at the code level and we can also unpack the design, language, and criteria that will guide people to the most effective results and next steps.
• If you are looking to do more research and planning to determine what content relates to each criteria in the questionnaire, we can support with this as well, but we are assuming at this stage that we are to focus on design and user flow from the questionnaire to the results, not the logic of the questionnaire.

Why an app?

• What are the use cases that validate this?
  • This is a key consideration because it is a lot of work to download an app. And if I only use it once, why?
• Current state (assumptions):
  • We assume most of the content on the recommendations page is not in-app, so this will just send people other websites so an offline mode won’t benefit (ie, download and use it later if you don’t always have access to the internet—plus this can be done on the web)
  • Single-use: my survey isn’t saved; I’d have to reenter my info when I go back?
  • What does an app offer me other than more work to download an open than just searching on the web?
• Future state:
  • Accounts?
  • Notifications?
  • Resource use tracking? Favourites? etc.
  • Training?
  • etc.
  • If there are aspects of the app that will be developed going forward that would support ongoing use and returning to the app, this may be helpful to know to understand and justify an app investment now (or later).

<aside> 👉🏼

Based on the content, experiences, and design considerations below—without more understanding of why this would benefit as an app—this feels like the focus should be on delivering a more smartphone, responsive-friendly, and accessible website experience, as opposed to shifting focus to an app.

</aside>

Technical scope questions

• You mentioned you are looking for help with front end development:
  • Are you looking strictly for help with the UI code - for example, do we write some React Native Views, deliver them to Ashja, and your team handles the rest of the integration and mobile app?
  • Or would we be responsible for the end-to-end mobile app/front-end development. ie,
    • frontend code
    • navigation logic
    • integration with the server
    • analytics
    • testing
    • build and submission to app store
• Does an API for server integration already exist?
  • What source would the app use to pull the survey information and recommended resources?
  • Is this updated over time / how?
• For Ashja, when does he need the final front-end code in order to meet the deadline?
• Requirements for usage analytics?
• Would the app need to integrated with any other systems we have not yet discussed?