Modernized hands-free recipe app for frustrated home cooks

What to build

A premium, subscription-based recipe-management app for serious home cooks, built around a hands-free voice-controlled cook mode (always-on screen, voice timers/navigation), multi-source recipe capture (link import, screenshot, and handwritten photo OCR), and an AI assistant for ingredient substitutions, unit conversion, and one-tap dietary rewrites.

Home cooks who already pay for recipe apps like Paprika and BigOven say those tools feel dated, suggesting room for a modern, AI-assisted alternative built around hands-free cooking and smarter recipe capture.

Demand

Home cooks who already have a habit of paying for recipe software are the target; the 'now' is AI making voice control, OCR capture, and ingredient-substitution reasoning cheap enough for a solo builder to ship, which incumbents built years ago haven't adopted.

• r/SideProject (Reddit)Anecdote

  Builder post: 'Every recipe app I've paid for felt dated, so I'm building the one I actually wanted' — describes having paid for multiple existing recipe apps and being dissatisfied enough to build a replacement

• Founder signal postAnecdote

  First-person account of paying for incumbents like Paprika and BigOven and finding them dated, implying existing willingness to pay in this category

• Internal scoring modelAnalysis

  Signal scored 0.52 with no historical match found, indicating this is an early, unproven pattern rather than a confirmed recurring opportunity

Stack

• Whisper or on-device speech recognition for voice commands
• OpenAI or Claude API for ingredient substitution and dietary rewrites
• OCR (Google Cloud Vision or Apple Vision framework) for handwritten recipe capture
• Readability/recipe-scraper library (e.g. recipe-scrapers) for link import
• Supabase or Firebase for sync and subscriptions
• RevenueCat for subscription billing

Solo + AI difficulty

The AI substitution/conversion assistant and link-based recipe capture are straightforward to build with existing APIs and could reach MVP in a few weeks; the hard parts are reliable voice control in noisy kitchen environments and handwriting OCR accuracy, which will take significant tuning and likely push a polished MVP to 2-3 months for one person with AI assistance.

Entry threshold

A solo builder with AI can ship a strong v1 (OCR/import pipeline, voice cook mode, LLM-powered substitution assistant) in a few weeks using existing APIs (speech-to-text, vision OCR, LLM); main effort is mobile UX polish and recipe parsing robustness, not novel tech.

Window

6-12 months

Where to find first users

• r/SideProject and r/cooking for launch feedback
• Product Hunt launch
• Food blogger and recipe-creator partnerships for content import demand
• Indie hacker communities (Indie Hackers, Twitter/X build-in-public)

Competitors

• Paprika
• BigOven
• NYT Cooking

Counter-signals & risks

• Recipe apps are historically a low-willingness-to-pay category; many home cooks default to free web search, social media, or ad-supported apps rather than subscriptions.

• Incumbents like Paprika and NYT Cooking benefit from high switching costs due to large saved recipe libraries and established habits, limiting migration even among dissatisfied users.

• General-purpose AI chat tools (e.g., ChatGPT) already handle substitution and conversion questions for free, which could commoditize the core AI-assistant feature before a dedicated app can monetize it.

• Reliable voice control in noisy kitchen environments is technically difficult and costly to get right, and existing smart speakers (Alexa, Google Assistant) already partially cover hands-free cooking use cases.