Find, Feast, Favorite - Jump into delicious discoveries!
A smart dining companion that helps you discover nearby restaurants, build your foodie favorites, and find the shortest path to your next great meal.
Everything you need
Find food fast. No hassle.
Looking for nearby dining options has never been easier. Search, save, and find your favorite places all in one lightweight app.
- Chain Chomp.
- Find the nearest dining places based on multiple locations. Add several points and see restaurants ranked by distance to any of them.
- Google OAuth.
- Quick and secure login with your Google account. No need to remember another password or create a new profile.
- Warp Pipe.
- Save your favorite restaurants and easily find the closest ones from your current location. Add, list, and remove favorites with ease.
- API Powered.
- Leveraging Google Maps API to provide accurate location data and comprehensive restaurant information at your fingertips.
- Lightning Fast.
- Extremely lightweight design ensures the website remains snappy and responsive, even on slower connections.
- Usage Tracking.
- Each account includes 1000 API calls, with clear indicators to help you monitor your remaining usage.
Frequently asked questions
Have a different question and can't find the answer you're looking for? Reach out to me via this website and I'll get back to you as soon as I can.
- Why are certain establishments visible at some times but not others?
- This occurs because the system only displays establishments that are currently open for business.
- Why am I unable to access certain features after using the app for some time?
- This is likely due to reaching your API call limit. Each user account is limited to a maximum of 1000 Google Maps API calls with no automatic renewals. Once you've reached this limit, certain features that require API calls (such as finding nearby restaurants or ranking favorites by distance) will no longer function. This limitation exists because the app is primarily a demo project, and Google Maps API usage incurs costs. If you find the app particularly useful and need continued access beyond the API limit, you can contact the author to request an exemption from the API limitations. The creator may consider your request and potentially grant you unlimited API calls similar to what they have access to.
- Why did you create this website?
- I created this website to help track the dining recommendations I frequently come across online, as I'm passionate about exploring new food options. Additionally, it serves as a showcase of my full-stack development skills.
- What is the tech stack?
- The app is built using SvelteKit as the framework with TypeScript for type safety. It leverages Tailwind CSS for styling and Shadcn for UI components. Data management is handled through Drizzle ORM, with tRPC and TanStack Query for API communication. The infrastructure runs on Cloudflare Pages for hosting, with Cloudflare D1 as the SQL database. Upstash Redis is used for rate limiting through a token bucket system. Location features are powered by Google Maps API, while authentication is managed through Lucia Auth which integrates with Google OAuth. PostHog is implemented for web analytics.
- Why did you choose Google OAuth for user authentication?
- Google OAuth was chosen because it provides a seamless login experience for users who are already familiar with Google services. Since the app relies heavily on Google Maps API, using Google OAuth creates a consistent ecosystem and simplifies integration. This approach eliminates the need for users to create yet another account and password, improving adoption rates. Google's robust authentication system also offers stronger security than building a custom solution would. The implementation saved development time and allowed the app to maintain its lightweight, snappy performance while still providing secure user authentication.
- Why is the website so snappy?
- The website delivers exceptional speed thanks to its SvelteKit foundation, a framework renowned for performance efficiency and minimal overhead. Significant effort has been invested in backend optimization to ensure seamless operation throughout the system. What's particularly impressive is that despite these powerful capabilities, the project incurs virtually no hosting costs ($0) through extensive use of serverless technology. These technical decisions collectively create the lightweight, responsive experience that makes the app remarkably snappy and quick to respond.
- I am getting a place not found error message after pressing the search button even after selecting the place from the autocomplete.
- This issue stems from how Google Maps API operates. This system uses two separate APIs: one that generates autocomplete suggestions based on your search terms, and another that converts those terms into actual place identifiers. These two systems don't always sync perfectly with each other. If you encounter this problem, try slightly modifying your search term or wording to help the system recognize the location correctly.
- Why are the feature names Mario themed?
- The Mario-themed naming wasn't originally planned. I started with "Chain Search" (a reference to restaurant chains), but my mind made the connection to "Chain Chomp" from the Mario games. Once that happened, I decided to continue the theme by naming all features after Mario characters and elements. While I do enjoy Super Mario RPG, I wouldn't consider myself a major Mario fan - the naming theme was more of a spontaneous creative decision that stuck.