MEGANNE JIMENEZ

• Feedback Approach

  • Users/Audience

    • Didn't do much testing for  users this time, spent more time with our sponsors about how to make the app more navigable. This time around, our users were our sponsors, so their feedback below would be the same as our 'users' feedback. We essentially went through the new layout of the app to get their general thoughts, as well as collect any changes that might be necessary for the app to make more sense. 

  • Sponsors

    • Questions:​

      • (After showing our sponsors our new navigation)​

      • How do you add to an existing interview?

      • Is the user flow in a format that makes sense? What makes sense and what doesn't?

      • Are the list items intuitive to click on?

      • Do you like the words "add" on the header bar?

    •  Answers/Feedback:

      • Most of our discussion with our sponsors was about all of our new navigation that we added. We went through page by page and showed them how we intended the user to navigate the app. They liked the overall flow and liked that the consent form wasn't able to be skipped over by the user. The biggest note that I made was that we need to have a page of interview questions somewhere in the flow so that the interviewer has the list of questions to refer to. They also recommended that we take away the 'quick add' page and just add icons in the header of the interview page. They thought that all of the buttons seemed intuitive, and they said we could probably add icons instead of words (in the header) to take away some bulk. We also discussed the back button, and how that could be a gray color without the title of each previous page in order to also clean up the header. 

  • Mentor​

    • Questions:​​

      • Questions:​

        • What's the best way to use Firebase?​

        • Are we going to need multiple Firebase components to make Firebase work?

        • How is this all going to work offline?

      • Answers/Feedback: 

        • Most of the discussion surrounded how to really get started with using Firebase. I had previously only initiated a project for both the Android and IOS app, but I never added any services/components like storage or authentication to get it started. Aileen recommended using either Firestore or Realtime Database, as well as storage. These would both give us the organization that we need as well as the storage that we would need for audio, video and notes. As far as offline usage goes, Firebase will automatically sync everything once the user has connected to WiFi/service, so there won't be a need to manually upload a portion of a project to the database. Aileen also went over different folders/bins that we could use to structure our database such as: users -> interview -> data -> consent forms, proj description, etc. ​

  • Summary of Feedback

    • The feedback received from this iteration was very helpful and puts us on a good track to be done with the final version of the app. From here, we want to take each of the apps into their native code to add things that will look more intuitive to each operating system. We only have some small tweaks to make with the layout of the app itself, it's going to be about the data storage from now on.

​

• Lessons Learned

  • Based on the feedback, I learned that we need to get started on Firebase because of how much troubleshooting it's going to take when using it with the react native framework.

  • Something that was unexpected was how much time it was going to take to set up Firebase. A lot of things don't work up to a certain point and a lot of troubleshooting was required. 

  • Our sponsors were overall pretty happy about the navigation solution that we came up with, so that worked in our favor. I don't think trying to split up the different navigation pages would have ended up working, because it doesn't make much sense. I'm glad we quit that process pretty quickly, because I think we would've ended up spending way too much time on it.

  • We accomplished the final outline of the app (apart from a page that we have to add), and started to activate the databases. Our time management this time around had to be shifted to work on the app development rather than data storage, so we miscalculated that. 

  • Changes to be made include the basic format/icons of some of the pages, mostly styling stuff that isn't priority.