Made by Don’t Stop Beerlieving
Review your brew!
All team members came up with an idea and we narrowed it down to a winner following a vote. The winner was Brew Review which is an app that allows users to view information about beers and breweries, to post reviews on existing beers in the Brew Review database, and to add beers that they try to the database. It also allows beer newbies and enthusiasts to connect with each other and share their beer interests.
The Team
George Harper
A python enthusiast (and he isn’t talking about the…
snakes), a hobbyist video game creator, and is looking to become a Software Developer who has expertise in Java Script.

Morgan Hewitt
Inspired by the use of technology to make a positive impact…
(hence the beer related app of course). Enjoys climbing, tennis and piano.
Nicole Raymond
An aspiring Software Developer from London who is switching…
careers from Advertising and Marketing.

Katherin Bennett
Curious, driven, and adaptable professional with a global…
mindset and a passion for continuous learning.
Tech Stack

We used Firebase, Expo, React Native, NativeWind, Java Script, Figma, Jira, GitHub / Git, React Native Components, Android Studio Firebase – to gain experience in a no SQL database and to have the opportunity to use authentication. Expo – for the emulation and routing capabilities. React Native – to gain experience in a popular framework which allowed mobile development. Native Wind – to allow us to use Tailwind CSS within react native. Java Script – it is the language we have the most experience with collectively and it is easily compatible with react native. Figma – this was used to brainstorm ideas, and then create wire frames and a component tree, as well as to plan our app generally. Jira – used for project management, creating tickets and keeping track of our progress and what needs to be done. GitHub / Git – used for version control, and applying a rule set to manage pull requests within the team. React Native Components – toast, drop downs etc Android Studio – for emulation.
Challenges Faced
Merge conflicts – working in a group and managing how to deal with lots of separate pull requests but we overcame this by creating a rule set of 2 approvals per pull request and learning Git more deeply to understand it better. Spiking Technologies – learning new technologies and implementing them very quickly took some getting used to but we have all learned invaluably from that process. Android Studio – this took a heavy toll on some of our devices and emulation proved complicated but we found ways around this using Expo and XCode for those of us with Mac OS. Compatibility issues – across different operating systems, web, and mobile.