Functions of the app: Connect/communicate with others going to same events Browse event by name/location Have a custom profile and see others too. End goal: meeting people of similar interest. Reason we created it: People usually use other forms of social media to organise groups going to events Event Buddy was specifically only for organising this More anonymity because e.g. meeting strangers on facebook would mean they have access to your personal details. Other apps are more focused on selling and organising tickets whilst this is specifically for organising groups to go together Intended users: People who like to go to events (not alone) e.g. festivals, concert, gigs. People who want to make new friends People who want to travel to events and share fairs People going to events abroad, very unlikely you’ll know someone there already, Events Buddy helps you connect before buying tickets (less commitment).

We used: AWS, React Native, Expo, React Native Elements.

AWS: because it seemed beneficial for job searching since it trendy at the moment. React Native: because we were building a mobile app. Expo: because Expo is built around React Native and is advised to use together.

to use together.AWS (Amazon Web Services): console logs took on average 4 minutes to appear Figuring out lambda functions was time consuming updating the database If we could go back, we would research all the services more, and choose the ones free. We were using some but halfway realised some services would cost after 12 months free trial. React Native: We thought it would be mostly similar to React like in the front-end project, however each component needed searching up and learning from scratch was challenging. Styling was difficult to do because although there are dev tools out there, we didn’t get a chance to use them. So instead, we used the “Expo Go” app where once an edit was made e.g. font size change, it was immediately visible in the “Expo Go” app on our phones. If we could go back, we would set up some form of dev tools for styling at the start of the project. Decision making as a team: starting a project from scratch with a team you have only briefly worked with individually before meant some miscommunication. Over time we eventually got used to each other and catering to everyone's opinions during decision making. Choosing what project to do: since we were initially used to being given mini projects to do, being suddenly given the endless variety was overwhelming. Splitting the team into 2 and having 2 separate ideas created and then coming together to vote helped to overcome this hurdle.