From a saved recipe to cooking it.

01 / The problem.

In Dishfolk, I am connecting the recipe people browse with the steps they follow while cooking. The current Flutter build has discovery, saved recipes, discussions, and a cooking view with a checklist and timer. It runs against a local backend with synthetic accounts; it is not a launched food community.

02 / My role.

I am building Dishfolk as a personal product using Flutter and Dart, with a Node.js, TypeScript, Fastify, and PostgreSQL local backend. The current foundation includes browsing, contributions, saves, discussions, and a cooking flow with a checklist and timer. It uses synthetic local accounts and data: it is not a launched consumer service or a production-ready mobile app.

My contribution

Product direction and implementation across the native Flutter interface and the local backend foundation.

Shared scope

Development uses a bounded local backend and synthetic accounts. Production authentication, personal uploads, hosting, and phone/iOS runtime verification remain unfinished.

What changed

An in-development product foundation with native content, cooking, and contribution flows, not a claim of release readiness or user traction.

03 / Implementation details.

• Keeping browsing, recipe editing, and the cooking checklist in a native Flutter app rather than a WebView.
• Checking current access before showing protected media.
• Recovering a submitted action without treating an old receipt as the current contribution state.
• Finishing production authentication, personal uploads, hosting, and device verification before claiming launch readiness.

04 / What exists so far.

• Built native Home, Explore, Create, Saved, and Profile surfaces rather than a WebView wrapper.
• Connected recipe and contribution views with cooking checklists and a timer.
• Implemented local contribution editing, saves, likes, comments, and replies.
• Developed access-aware media handling and submitted-action recovery in the local environment.