It is a truth universally known that eating food is much better when you’re eating with other people. If only it were that easy deciding where to eat, though — and unfortunately, it gets harder the larger your party is...

Problem statement

There is a lot of difficulty in deciding where to eat and where to go. Factors such as restaurant hours, dining options (which were particularly impacted after the pandemic), the location, and individual dietary restrictions come into play when deciding where to go when meeting up with friends and family over dinner. Planning a meetup over food results in long chains of messages exchanged being group chats.

Ray and I believe that sharing meals with the people you care about is one of the things that make life worth living.

We also believe technology should be used to make our lives a little bit easier, and there are few things more difficult than deciding where to eat.

Our solution Nommers!

What it does

Nommers is a web application that is responsive for both desktop and mobile breakpoints.

How do you use it?

  1. Designate a trusted individual in a group of diners to be your party owner. This party owner will make a lobby and filter restaurants based on location, price, star rating, available dietary restrictions, and so on.
  2. Once the party is created, the party owner will share a party code with everyone. This code is used to enter the lobby. Once everyone is in the lobby, the party owner will commence the voting period.
  3. Everyone in the lobby will be able to vote on the restaurants they would like to eat at by swiping through the options. Once everyone is in the lobby is done voting, the voting period ends.
  4. Lastly, the results are displayed! Nommers shows you the top restaurants that everyone voted on. This hopefully helps make the decision-making a lot smoother and easier.

How we built it

Christina: I started off by creating low-fidelity wireframes on Figma, carefully selecting a color palette and font choices, and brainstorming ideas for a logotype. While I did that, Ray was working on the backend and started by deploying the server. He had... some difficulty with it to say the least. He had a lot of success with writing the swiping animation during the voting process, though, and I was pleased with how it turned out! After I finished creating low-fidelity wireframes, I created all of the web pages with mobile responsiveness, and then proceeded to implement them with desktop responsiveness. While I was doing this, Ray was working on fetching data from the Google Maps API.

Technologies used

Figma, Adobe Illustrator, Adobe Photoshop, Svelte, HTML, CSS, JavaScript, GitHub, Postman, AWS Elastic Beanstalk, AWS S3, EC2, RDS, Elastic Cache, PostgreSQL, Redis, Django, Django Channels, Django REST Framework, Google Maps API

Challenges we ran into

Christina: Perhaps we bit off more than we could chew. I worked on developing the frontend of all the web pages and making them mobile and desktop responsive. This proved to be very difficult, especially since I had to make assets for the webpages, write copy, prepare the presentation, and make

Accomplishments that we're proud of

Christina: I learned Svelte for the first time; I made some very cute graphics on Adobe Illustrator and Figma and crafted the branding and personality of Nommers. I think it looks adorable and I am very proud of the work that I performed! Ray: Over all I am please with the backend deployment, depite the challenges.

What we learned

Christina: Svelte definitely! I have never used Svelte but Ray insisted it was the hot new JavaScript framework. I tried it out and unfortunately, I did not find it much enjoyable and prefer Next.js; however, it was worth a try and I am glad I had that experience! Ray learned that it was particularly difficult to work with setting up AWS servers... and all things web related in general

What's next for Nommers

Ray would like to smoothen the animations for the swiping. Ray would also like correct many of the server and webstite state management related issues.

Resources used

Freepik, Dafont, Unsplash

Share this project: