---
# System prepended metadata

title: T1 Summary and User Testing

---


# T1 Summary and User Testing
![](https://i.imgur.com/ZraEjVX.jpg)

## Summary
*Summarize your user testing and any feedback you got during demos.*
- During demos, we got a decent amount of positive feedback as well as some good constructive criticism. Our users seemed to be most impressed by the auto generation of the terms list, but the main point of criticism was that we only support one relation symbol, `::`. On the UI/UX front, we got some great feedback and observed that many users found our buttons/page navigation to be unintuitive. Overall, we're confident that the user feedback we gathered during our demos will help us build a more intuitive and better product this winter.

#### Observations
*Record your observations and any insights/conclusions you may have about them. Identify top patterns and write them up. Record the number of email signups you got.*

* The majority of peopinle who took our survey say they take notes on google docs
* People also said they liked their note taking platform for convinience 
* Most people felt somewhat but not totally loyal to their current platform
* People felt getting all the information and having organized notes were the most important things when it comes to taking notes
* People felt our platform was mostly easy to use
* People felt our language was somewhat easy to use -- most respones were 4/5 with 5 being very easy
* A lot of people found the auto-save feature to be really important
* People thought we could make our note-taking interface more intuitive & clean (ie, color coding, smaller tabs)
* Users needed a fair amount of instruction as to how to properly use the app (maybe an onboarding flow or template for a new note that includes instructions would help)
* most people were not familiar with Markdown
* People wanted us to flesh out flashcard functionality -- a few saw that as the main draw to the platform
* They also wanted a hover for the definitions

#### Analysis
*Is there any analysis you can do of the testing - what percentage of users claimed X or Y.  If you had numerical answers was there any statistical significance to the answers?*
* How easy was the langauge to use? 
    * average $3.5/5$

* Do you find the featurelos helpful?
    * averafe $4.3125/5$

* How likely would you be to use our product in the future?
    * average $3.875/5$


#### Notes To Future Us
*Leave notes to yourself for next term - what should your next steps be?*
* let the flashcards allow for muli-line definitions (like bullet points)
* format the term and definition defined by the `::` in a specific/different way on the right side of the editing view (this will also tell people that they used the special character correctly)
* make the flow back and forth from editing view to study guide view to terms/flashcards more intuitive

## TeamWork
*Reflect on how your team is working together*

- We feel that we are doing really well working together. We have been doing a good job of communicating between and within the "teams" that we have split into. Everyone has been super helpful getting the others up to speed on what they have been working on. 

#### What has been working well?
*give kudos and shoutouts, comment on communication techniques that have worked, pr review practices, etc*
- We think we did a good job of breaking up the team into frontend/backend and balancing working in those small groups and also coming togetheras a big group 
- Meeting consistently & talking through overarching product decisions has been really helpful. 
- Everyone's been showing up and doing their work!
- 
#### What has not?
*try to discuss any problems openly and respectfully. communication breakdowns? are some teammembers taking others tasks for themselves? is anybody ghosting? etc*
* We discussed the time constraints that arose with pivoting ideas so late in the term and how this led to rushing a lot of things without everyone understanding exactly what was being done in a huge pr for example
* In the winter we will have the time to talk things through more and all understand what is in each pr
* We need to have clean, wholesome team bonding activities


#### Steps
*if there are problems, think of some ways to resolve them, go back to your team contract from last term to see what you said you would do for resolution*
- Phoebe: wants to take on more of the load, especially on the backend, will be working on project over winterim, and is interested in learning front-end to help.
- Gwen: I want to learn more frontend especially if there is more work to be done there than the backend. I also want to frontload work since I will not have as much time in the winter with ski travel and training.
- Georgia:  I want to get better at front-end dev, but also make sure I understand the backend and the connection between the two.
- Jacob: Will be taking a different 3A in the winter, which may cause logistical issues. So will be as flexible as I can setting up alternate meeting times to make sure we can still meet with everyone as needed.
- Nick: Happy to continue working mainly on the backend just because I don't know the frontend stuff and want to be most efficient with my use of time. Also happy to step in on the frontend though if there's not enough backend work.
- Giorgie: I want to take some time to better understand how things are working on the backend so that I can do more full-stack work, and also keep learning more about best practices/what's possible with react. 

#### Next term/Winterim
* Frontend
    * Flashcard functionality
    * Collaboration
        * invite people by email to share
        * maybe generate a link & share? 
    * Change flow for termslist/study view to be a third icon on the top 
    * image upload

* Backend
    * Alternate hosting (render?)
    * Collaboration (sockets?!)
    * NoSQL DB (MongoDB)
    * Revisit if Flask is our best/fastest option
    * More relational symbols!!!

* Fullstack
    * Real-time saving and collaboration

* Design
    * how can we make the flow from editing -> study guide -> terms more intuitive?
    * button for terms list shouldn't look like the action buttons (back, save)
    * back button on study guide page seems like it's going to take you back to editing, not home
    * maybe we make the toggle have 3 options instead?