household.roles()People with different jobs
Owner, member and helper roles sit on top of server-side permission checks and household-scoped access.
visitor@sultaning:~/work$ open homechef-os
An operating system for the household kitchen. HomeChef OS connects recipes, planning, shopping, pantry state, people and guided cooking into one coordinated workflow.
open live beta ↗Most cooking products stop at finding or saving a recipe. HomeChef OS continues into the operational work around it: deciding what to cook, coordinating a household, buying what is missing, understanding what is already available, assigning the cooking and guiding the person who actually prepares the meal.
The core data model is household-scoped. Owners, family members and helpers can participate with different access, while shared state — schedule, pantry, shopping and cooking tasks — remains coordinated around one home.
household.roles()Owner, member and helper roles sit on top of server-side permission checks and household-scoped access.
schedule.week()A Sunday-based weekly planner supports multiple recipes, custom meal slots and operational changes across the week.
shopping.session()Categorized trips connect planned recipes with pantry state, price tracking, completion and guest Supply Links.
cook.assign()Cooking assignments persist across devices and move from queued to cooking to done through the guided flow.
Behind the consumer experience is an Arabic-first Content Studio and a canonical ingredient system. Recipes can be imported, translated, versioned, published as immutable locale snapshots and enriched with AI-generated metadata and media without turning the runtime product into an AI demo.
content.publish()Drafts become immutable published snapshots per locale, with rollback creating a new draft instead of mutating history.
ingredient.resolve()Multilingual aliases resolve into canonical ingredient IDs used by recipe, shopping and pantry workflows.
ai.gateway()Recipe parsing, translation, tagging, step generation and image creation flow through an AI gateway rather than leaking provider logic across the product.
localize()Arabic, English and additional household languages are handled as content and UI concerns, including RTL and server-resolved mobile display values.
The same Express REST API serves the React web product and the native React Native client. Authentication is stateless Firebase Bearer auth, household context is resolved server-side, PostgreSQL stores the operating model, Cloudflare R2 handles media and the mobile path has its own native build and TestFlight delivery pipeline.
HomeChef Mini was deliberately reduced to a sharp market entry: capture cooking content and turn it into a useful recipe. HomeChef OS solves the larger problem that begins after the recipe exists. The two are presented separately because their user promise, scope and runtime systems are intentionally different.
The work spans product direction, household workflow design, information architecture, backend contracts, AI-assisted content systems, multilingual UX, native mobile architecture, operational tooling and the decisions required to move a broad idea into a working beta platform.
HomeChef OS keeps web, native mobile, household operations, content and AI on one coordinated backend model. The technology is organized around shared household state rather than around individual screens.يبقي HomeChef OS الويب والجوال الأصلي وتشغيل المنزل والمحتوى والذكاء الاصطناعي على نموذج باك إند منسق واحد. التقنية منظمة حول حالة منزلية مشتركة، لا حول شاشات منفصلة.
The platform has many surfaces, but the household operates against one shared truth.للمنصة واجهات كثيرة، لكن المنزل كله يعمل على حقيقة مشتركة واحدة.