How we built and launched RecipeGo, a recipe app.

The goal

People keep recipes in screenshots, bookmarks and notes apps. We wanted one place where a recipe from any source becomes something you can actually cook from: ingredients that scale, steps with timers, a weekly plan, and a grocery list that adds itself up.

What we built

• Import from a website address or a YouTube video, with a review screen where you check and fix anything before saving.
• Cook mode with large step text, a screen that stays awake and built-in timers.
• A servings scaler, a weekly meal planner and a grocery list grouped by aisle that combines duplicate items.
• Cookbooks, favorites, private notes and search across ingredients and steps.
• A free plan that doesn't expire, and an optional Pro subscription.

How it is built

The app is one React Native codebase, built with Expo, so the iPhone and Android versions behave the same and ship together. Accounts, the recipe database and the import logic run on Supabase, which gives us a Postgres database with per-user access rules and server functions. Subscriptions go through RevenueCat. The website, recipego.app, also serves shared recipe pages, and the app opens those links directly.

Timeline

What we'd tell a client

• Design the free path first. A paywall that leads nowhere is a bad moment for a new user. In RecipeGo, typing a recipe in by hand always works, so the free plan never hits a dead end.
• Plan for review time. Both stores review every version. We submitted two weeks before launch and chose the release day ourselves.

Get the app

Free to download. See also RecipeGo on our products page, or how we build apps for clients.