MEGANNE JIMENEZ

• Feedback Approach

  • Users/Audience

    • Questions/Instructions:​

      • Can you navigate to the "Login with Email" page and then navigate back to the "Login with Project ID" page?​

      • Input a fake email and password and then "log in"

      • Do you like the use of switches for the consent form? Or would checkmarks make more sense?

      • (on project selection/creation page) Can you fill in every available input option? Are these intuitive?

      • Does the order/flow makes sense?

    • Answers/Feedback:

      • This task was easy to follow, since the app created its own back button, so it was simple to navigate to and from different login pages/options. ​

      • This was also simple, the user was able to tell what was the text input field was. Then they clicked "log in".

      • User said that checkmarks would be nice, but the color changing switches still make sense because it feels like you're moving them from a "no" to "yes" position.

      • It was pretty straightforward to input information into every field. The picker was slightly confusing at first, but it makes sense once the user starts to tap on it. It might be easier to format it in a way that is more familiar to mobile users.

      • User said it felt like it made sense, maybe the consent form would be in a different spot and that project options were displayed before it.

  • Sponsors

    • Questions:​

      • Does this layout/user flow make sense?​

      • Does the consent form seem out of place/out of order?

      • Besides the recording audio/video, are we missing any key features?

      • Do you like the format of each page? What should be included (if necessary)?

      • What do you think about adding some sort of landing page or home page for the user to fall back to?

      • Email input for the consent form modal?

      • Does each feature work the way you imagined? What's different and what could be added/changed?

    •  Answers/Feedback:

      • We talked about the user flow and adding a home screen, and our sponsors were open to the idea, but needed to make sure that the consent form is not lost in the flow. We're going to plan a more detailed layout so that we can show them what we were thinking. Besides the audio and video components, our sponsors told us that we needed to make the first three fields of the project page autofilled. Some advice we got was to try to make the buttons round and the classic pink/salmon, and change the switch colors from red to gray and green to pink. Lastly, we discussed our MVP, and we figured that everything we have on the wireframes/mockups. 

  • Mentor

    • Questions:​​​

  • • The record audio/video feature is getting tough, what should we do about that?

      • What are some good resources for learning ReactNative?

      • Is the format of the .js file too busy? Would it be easier to break each function up into multiple files?

      • What do we do about the style sheet that's at the end of the code?

      • How do we deal with data storage?

    •  

    • Answers/Feedback:

      • (considering Aileen as our mentor for this round) Aileen recommended that we should probably start to make each function into its own .js file so that would be the only file to update. Everything would run from the App.js file, and then there would be a corresponding file for each function. The style sheet should be placed at the bottom of each function, but only the styles that the function specifically uses. Aileen also brought up that we would probably have to add the line of code at the very bottom of each file that exports the function. As for the audio and video troubles, Aileen recommended that if we need to move into Xcode and Android Studio in order to get those things to work, then we should do that. Once we feel as though we got as far as we could in ReactNative, we should then move into XCode and Android studio to finish up the last couple of features/components. Then we talked about Firebase and its functionalities. It seems like a good options since Soapbox will be integrating a web platform as well, which Firebase supports. Then lastly Aileen found some sources for us to use in order to learn ReactNative in a different way (rather than just the tutorials on the Native website), which included some books and YouTube channels.​

  • Summary of Feedback

    • Overall, I felt like we got some useful information regarding the actual building of the application, to the more conceptual things. Since we only had a very rough app to show, there wasn't much feedback that we weren't expecting, but we will take things like the user flow and the way some components work into consideration. Moving on from here, I expect that we figure out the audio/video portion, and format the one app.js file into multiple files. I also think we will start to consider aesthetics, so that interviewees can focus more on functionality and less on how bare it looks.​

​

• Lessons Learned

  • Based on the feedback, I learned that we need to reformat our files and organize them so it will eventually be easier to understand, navigate, and update. We also might need to consider making some small tweaks when it comes to components as well as user flow.

  • Something that was unexpected was the comment about the user flow, because we were just following the flow of the wireframes, but it was something to consider and bring up with our sponsors. 

  • Building a super basic app wasn't exactly simple, but we got the hang of it and got the basics done. However, the recording part of the coding was pretty difficult and now it's something that we're going to have to research more and make sure that it something that works in the future.

  • We accomplished a basic app, which aligns with our timeline (it might even be ahead of what we said previously).

  • Changes to be made include the file structure as well as some of the components (possibly), as well at whatever additions our sponsors recommend.​