Peasy
One calm path from recipes to a shopping list you can depend on.
Peasy
Plan well. Shop once.
Overview.
Meal planning breaks down when recipes, household needs, and the grocery run live in separate places. Peasy connects them in one flow: save what you want to cook, choose who is eating, and create the shopping list from those decisions.
I designed and built Peasy as one product across iOS and the web. Both apps share the same accounts, calculations, and product rules. Each interface follows the patterns that make sense for its screen and context.
Product flow on iOS.
Web app.
The web app adds a workspace for larger screens. Persistent navigation keeps recipes, plans, and shopping lists close while wider panels make comparison and detailed list work faster.
Click through the web app
Follow the pointer from the recipe library to the meal plan and into a shopping list.
Collect recipes
The recipe library brings web links, photos, files, social posts, and manual entry into one starting point. Imported recipes stay reviewable before they join the library.
Build the plan
The wider workspace keeps the selected day, meal, recipe details, nutrition, and household participants in view. Servings follow the people included in the plan.
Work through the list
Saved lists and the active checklist sit side by side. A list stays stable after it is created, so later recipe or preference changes do not rewrite a trip already in progress.
Product decisions.
Use AI for the messy work. Use regular code for prices, payments, and anything the app must get right every time.
Remove the paywall from onboarding
What: I removed the paywall from onboarding. New accounts finish setup and enter a 14-day Pro trial on iPhone and the web without a card. The trial ends on the same date on every device, and checkout appears only after it ends.
Why: A paywall asks people to make a payment decision before they have felt the product's value. That extra step can make them leave before finishing signup. Letting them save a recipe, build a plan, and make a shopping list first lowers onboarding friction, then asks them to pay after they understand what Peasy does.
Limit the expensive work, not people's recipes
What: Free accounts can save 50 recipes and use 3 imports that need AI help each month. Pro removes the recipe limit and gives 100 assisted imports each month. The trial includes 100 total. If someone returns to Free, Peasy keeps every recipe and only pauses new saves until they are under the limit.
Why: AI imports cost Peasy money each time, while keeping an old recipe is cheap. The limits focus on the costly action and never erase work a person already saved.
Set a competitive price to grow Peasy
What: I set Peasy Pro's US web launch price at $5.99 a month or $49.99 a year. In a September 2026 price check, that was close to Plan to Eat ($5.95 a month, $49 a year) and below Samsung Food+ ($6.99 a month, $59.99 a year).
Why: Peasy is prelaunch, so gaining users matters more to me right now than maximizing profit. A familiar price makes it easier for people to keep using Peasy after the free trial.
Use AI only where it is worth the cost
What: I use AI only when a messy recipe page, photo, or file needs help becoming a draft. Serving math, unit conversions, grocery totals, and package amounts use hand-written calculations and reviewed rules. Peasy does not pay for an AI call to do math the app already knows how to do.
Why: That matters in an MVP because every AI call costs money and can return a different answer. Regular calculations are faster, cheaper, and give the same result every time. Saving AI for the messy work lets Peasy test the product without paying for it everywhere.
AI makes the draft. People make the decision.
What: Anything AI creates stays a draft. Peasy checks where the details came from and whether the draft has the right fields. The person can edit it and must press Save. AI never decides an unclear serving size, paid access, package amounts, or whether to send a cart to a store.
Why: Those choices can change someone's bill, food amounts, or saved data. They need the same answer every time and a clear choice from the person using the app.
Let shared recipes bring in new people
What: Every saved recipe automatically gets a public page that anyone with the link can read. Peasy explains this before Save, so sharing from a recipe card or detail page does not need another publish step. If a visitor taps Save recipe, Peasy takes them through sign in or sign up when needed, then returns to save their own copy. The page also shows how many different Peasy accounts saved it.
Why: A useful recipe can introduce someone to Peasy without feeling like an ad. The Save button gives them a clear next step after they see the value. The save count adds social proof and gives sharing a small sense of progress, but views, failed attempts, and repeat saves do not raise it, and no names are shown.
One product system.
iOS and web use different interface patterns, but the product promises stay the same. Shared contracts keep recipes, plans, quantities, and saved shopping lists consistent across both apps.
What I learned
Cross-platform design gets stronger when the shared layer is the product's behavior. The interfaces can respond to their devices while the important promises stay exact.




Let's make something users will love!
If you're looking for a product designer who can bridge the gap between design and code, I'm here to help!







