NearBuy

Thumbnail!

A mobile app designed to reduce the monopoly of third-party food apps on local restaruants currently operating. NearBuy encourages the support of local businesses directly.

Alternative Accessible reading format:

NearBuy - Stay Safe. Support Local.

INSPIRATION - Is the only way to get take-out food through a third party app?

Third-party food delivery apps, Uber Eats, DoorDash, Skip the Dishes, have undoubtedly gained momentum within the past couple of years. Out of convienence, of course. Sure, it might be slightly more expensive than take-out, but it was worth it for many.

And businesses were getting more traffic. Why else would they agree to the 25% cut most companies demand?

But with most cities imposing strict restictions against dine-in operations, signing up for apps like these were no longer optional. How else were local family restuarants going to get exposure? Even if it meants potential losses when the apps experience glitches, and your business is marked ‘closed’ for days. Even if it means your profits are further dwindled.

At the same time, consumers much rather use an app too. The use of the telephone seems foreign for most of the younger generation. And nobody wants to visit a restuarant only to find they aren’t available for taakeout.

Third-party delivery seems so easy, for consumers and restuaranteurs. There was only ever the illusion of choice.

Introducing NearBuy.

A map that offers consumers choices on how to support local. Businesses can list their restaurant status, which are validated by users. Users can choose if they would like to use a third party delievery app, or choose an ordering method that supports the business directly.

FEATURES

Track user location using Radar API
Display local businesses and offerings
Redirect users based on ordering option

APP STRUCTURE

MongoDB + User typed query --> Display on Map --> user redirects based on selection

CHALLENGES & LEARNING POINTS - What the experience was like for each of us

Jeff Suitor (Focus: React Native) Challenge: One issue I realized late last night was the incompatibility of the React Maps API with registering our user button clicks. Good thing we caught it sooner than later! Learning Point: Time management. We shouldn’t have taken on more than we could handle.

Zack Ren (Focus: API Mangement) Challenge: I faced issues with setting up the Radar API, but with the help of our team, we got it resolved quickly. Learning Point: I think setting up the environment in advance would be a great way to ensure the rest of the event runs smoothly

Longxi Lin (Focus: Design & Marketing) Challenge: TOHacks was arguably shorter than any hackathon in my experience. It was difficult to balance sleep and productivity. Learning Point: I think going into an event and deciding roles and a game plan is key to know who is responsible for what aspect.

WHAT'S NEXT FOR NEARBUY - What we hope to implement in the future