¿Puedo vibecodear Pestle?

SÍ · se arma en una sentada

precio $2.99/mesahorrarías $35.88/añotiempo de build una sentadacategoría 🏠 hogarreemplazada por 0 personas

The core loop is small enough for a capable coding agent to produce a useful local version in one sitting. For Pestle, save recipes, guide cooking steps, plan meals, and share a household list. The hard boundary is native apple polish, recipe import, hands-free mode, sync, and family sharing, plus sync, integrations, and household adoption.

el prompt

Build a personal replacement for Pestle in an empty repository.
Use Next.js 15, TypeScript, SQLite, Drizzle ORM, and a local-first PWA; do not offer alternative stacks.
The core loop is: save recipes, guide cooking steps, plan meals, share or print a household shopping list, and keep data portable and owner-controlled.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create household members, shared lists, calendar items, recipes or inventory records, and assignments.
Provide fast mobile-first capture with large controls, offline queueing, and conflict-safe sync to one server.
Support recurring chores or events, reminders, completion history, and printable views.
Add CSV or JSON import and export plus photo attachments with clear size limits.
Allow private and shared items and make every change attributable and undoable.
Add backups, household export, member removal, and a simple invite code.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out retailer ordering and proprietary product catalogs.
Deliberately leave out broad smart-home integrations.
Deliberately leave out large public recipe libraries and polished native mobile clients.
Finish by running the tests and listing the exact commands used.

$ ábrelo en tu agente (prompt listo, tú das enter) o cópialo crudo · este prompt se genera del plan de build · mejorarlo con un PR

por qué la gente sigue pagando

People still pay for Pestle because household apps survive when every family member actually uses them and the data stays current across devices. The recurring cost buys multi-user conflicts, reminders, notifications, imports, barcode data, smart-home APIs, backups, and long-term maintenance, not just the visible interface.

qué pierdes

xnative Apple polish, recipe import, hands-free mode, sync, and family sharing

xfrictionless family sync

xretailer and smart-home integrations

xlarge recipe or product database

xmobile polish

arte previo · úsalo en vez de construir, si prefieresMealieActive open-source recipe manager and meal planner for households.↗

compartir en X ↗"Acabo de reemplazar Pestle ($2.99/mes) con un prompt"

los números

Precio de Pestle

plan	mensual	anual (por mes)	qué incluye
free	$0	$0	Up to 15 recipes; includes website import, shopping lists, guided cooking, scaling, and unit conversion.
pestle pro	$2.99	$2.08	Unlimited recipes, device sync, household sharing, meal planning, and image/PDF recipe import.
pestle pro lifetime	a medida	—	Same Pro feature set without recurring billing.

plan gratis15 recipes; no published numeric caps for shopping lists or guided-cooking sessions.

facturaciónmonthly + annual + lifetime; 14-day trial

costos ocultosThe App Store lists more than one lifetime SKU ($39.99 and $49.99), so the price shown in-app can differ from the $39.99 official-shop offer.