## Our idea(s) <img src="https://media.giphy.com/media/yoJC2IEW8GthBApfd6/giphy.gif" height=400> --- ### What do WE want? What apps have we used in the past that we've not been satisfied with / stopped using - Making friends Bumble, Meetup - Language exchange Ask Amy --- #### Existing apps | Language Exchange | Making friends | |---|---| | Bilingua | Bumble BFF | | HelloTalk | Friender | | Hello Pal | Hey! VINA | | Tandem | Peanut | | Idyoma | ATLETO | | Italki | Meetup | | Speaky | REALU | | NiceTalk Tutor | Nearify | | Conversation Exchange| Skout | | HelloLingo| Nextdoor | --- ### We need to make our app different. <img src="https://media.giphy.com/media/kiSkRi88Ip3mqQLf0s/giphy.gif" height=400> ### How? --- #### Narrow down our demographic <img src="https://media.giphy.com/media/JqyZW7UvddGro62DJa/giphy.gif" height=200> - People who have immigrated to this country and want to learn English / broaden their social circle - People who live here and want to learn other languages / broaden their social circle - People who are visiting and want to meet local people / take part in local events --- #### What would they need? - Safety - Learning - Comfort - Location --- #### Define our app's purpose - Combine learning and social - Keep UI as simple as possible - Make the message clear --- ## What we've got - Social language app with an emphasis on learning and safety. - A demographic of under-representated groups. - Encouragement to meet in person / attend local events to create meaningful, longer-lasting connections. --- # Process Very similar to yours, probably. --- ## Decisions - ideas and frameworks We decided to create an app using Next.js, styled components, authentication, and cookies. We floated a lot of ideas but kept coming back to the exchange of language and culture. --- ## Post it issues <img src="https://i.imgur.com/e1gQ92o.png" height=500> --- ## Issue template We would love to see yours to get THE ULTIMATE TEMPLATE.  --- ## Estimations We started using the velocities we're used to, then moved on to using the PERT method to estimate our issue timings. We prioritised issues for sprint one by using the needs/wants chart and assessing which issues would be needed to progress later in the application. We are a little behind and so haven't planned as well as we'd like. But we're on the way! <!-- So far: | Issue | P | O | M | E | |---|---|---|---|---| | Homepage | 3 | 1 | 1.5 | 1.5 | | Homepage | | | | | --> --- # Usability Testing  --- - Complete sign up process - Navigate through pages - Send a message to someone - What do you think the website is for? ---  --- - Users all had confusion about the NEXT button - One user mentioned they dont feel comfortable not having log out button and delete account - Terms and Conditions agreement (they like somes of them but not all) - Our users were not able to guess what our website is about - They liked simplicity - They wanted to see decription about our web app purpose on the home page - They were not happy to see blogs in an web app so we changed it to events - we had review section and on euser mentions that having review about people is not pleasant --- # Challenges - Personal commitments - Conflicts: Having different opinions lead us to not going in the same direction. - Technical issues: Slow connection, Cut offs. - Design Architecture (miro's terminology: blueprint): connecting the dots in between back-end and front-end. --- # What went flawless: - High engagement - Thoughtful and considerate communication. - Role assignments ---