FlourPower.app

Status: Active and maintained Last updated: May 2026 Live at: flourpower.app

What it is

A recipe app that started at a kitchen counter, not in a boardroom. Designed around the moment you're actually cooking — not browsing or scrolling. Built for families who cook together (up to 5 members per household, with shared cookbooks and shopping lists), with AI-powered enrichment that automatically extracts cooking timers, difficulty scoring, ingredients, tools, and substitutions from every recipe you import. Available on web, iOS, and Android.

Why I built it

My family's recipes started in overstuffed binders — handwritten cards from my grandfather, magazine pages, printouts from early food blogs. Organized chaos, but ours. One of those cards was my grandfather's Stollen recipe, which only told half the story; it took four Christmases of calling him to ask "how much is a little?" before we landed on a version that worked without him standing next to us. That experience taught me a recipe isn't a list of ingredients — it's knowledge worth preserving properly.

When we went digital, we tried Cook'n until the subscription costs kept climbing, then Copy Me That, which I genuinely liked. But the more I cooked with these apps, the more I noticed the gaps. They were designed for browsing recipes, not for actually cooking them. Standing at the stove with floured hands, you'd scroll past a photo gallery, an ingredient list you already prepped, and three paragraphs about someone's trip to Tuscany before getting to step four. Every recipe app I tried treated the kitchen like a reading room.

I wanted something built around the moment you're actually cooking — one step at a time, timers built in, no scrolling past intros to find the next instruction. And I wanted the data to be ours, exportable to open formats anytime, with no strings.

The longer origin story is on flourpower.app/about.

What it actually does

AI-powered recipe enrichment — this is the differentiator. Every imported recipe gets parsed and enriched automatically:

• Cooking Timers detected from the recipe text (no manual setup)
• Difficulty Scoring so you know what you're getting into
• Ingredient Parsing — quantities, units, and ingredient names extracted cleanly
• Tools & Equipment detected from the instructions
• Nutrition Estimation (Premium)
• Ingredient Substitutions (Premium)

Family features — built around households with up to 5 members:

• Family profiles with distinct user identities and Roles & Permissions (different members can have different access)
• Shared Cookbooks — curated collections everyone in the family can see
• Shared Shopping Lists — generated from the recipes you're cooking
• Public Family Profile (optional, for sharing your collection more broadly)
• Easy invitations to bring family members in

Recipe import — broad coverage:

• URL import — paste any recipe URL (Food Network, NYT Cooking, Serious Eats, anything with structured data)
• File import — direct support for Paprika, CopyMeThat, Pepperplate
• App migration — broader format support via my converter, MoveMyRecipes
• Photo & PDF import — take a picture of a recipe card or upload a PDF

Cooking + cookbook tools:

• Serving Scaling — scale recipes up or down without manually recalculating
• Unit conversions built in
• Tags & organization — categorize, tag, search
• Public Sharing — share individual recipes with people outside your family

Data and trust:

• Data Export — full export to standard formats anytime, no premium tier required
• No ads, no tracking, no data selling — foundational, not a feature
• Two-Factor Auth and Passkeys — modern account security

Platforms:

• Native iOS and Android apps plus a responsive web app, with Dark Mode throughout

Plus:

• A blog — short posts on recipe management, data portability, and why I'm building Flour Power the way I am

What it doesn't do

• No social features. No public profiles, no recipe ratings, no follower/follow systems. Flour Power is for your family, not for an audience
• No grocery delivery integrations with Instacart, Walmart, Amazon Fresh, etc.
• No ads, no tracking, no data selling. Not a feature — a foundational design choice.

Privacy and data ownership

You can export your full recipe collection anytime to standard formats (JSON, PDF, CSV, Markdown — the same formats MoveMyRecipes outputs). If you ever want to leave Flour Power, you walk out with all your data. No lock-in, no proprietary export-only formats, no "premium tier required to export."

Pricing

Free tier covers individual and small-family use. Premium adds [Andrew to confirm: list specific premium features here]. No ads or upsells in the free tier.

Technical foundation

Built on Laravel (PHP). Recipe parsing reuses the parser library from MoveMyRecipes — same parser engine, different product. Transactional email runs through Mailgun (sending domain m.flourpower.app); apex flourpower.app mail goes through Google Workspace. Self-hosted infrastructure for full control over data handling.

Related projects

• MoveMyRecipes — the standalone web converter I built so people leaving any recipe app (Paprika, CopyMeThat, Cook'n, MasterCook, etc.) can keep their data. MoveMyRecipes is intentionally neutral about destinations; Flour Power is one of several options I'd point users toward depending on their needs. The two share a parser library and a worldview about data ownership, but they target different things — converting vs. managing.

Contact

If something's broken, missing, or you want a feature added, get in touch via judd.dev/contact. Direct feedback is the fastest way to get something fixed or prioritized.