return

Sakosha

Sakosha is my current deeper product/building exercise: a shared grocery app centered around collaborative spaces, invite flows and clear role-based actions. I wanted something bigger than a UI experiment — something that forced me to think about product boundaries, architecture, auth, data modelling and deployability from the beginning. It is still in progress, but that is part of the value: it shows how I think when a project is still evolving, not only when it is already polished.

Next.jsTypeScriptTailwind.NET (EF Core)PostgreSQLDockerWork in ProgressNext.jsTypeScriptTailwind.NET (EF Core)PostgreSQLDockerWork in ProgressNext.jsTypeScriptTailwind.NET (EF Core)PostgreSQLDockerWork in ProgressNext.jsTypeScriptTailwind.NET (EF Core)PostgreSQLDockerWork in Progress

The challenge

Collaborative grocery planning with invite links, roles and list lifecycle (WIP). The aim is to enable small groups to coordinate shopping around shared events and hubs with clear role-based permissions and minimal friction. This involves designing simple invite flows, resilient offline-friendly list syncing, and a domain model that keeps lists and spaces composable as the product grows.

The process

  • Documenting architecture early helps keep scope aligned
  • Scaffolding FE + BE with Docker and local dev scripts improves iteration speed
  • WIP: core domain model (spaces/lists/items) and RBAC

Stack

Next.jsTypeScriptTailwind.NET (EF Core)PostgreSQLDocker

Future ideas

  • Complete auth and invite flows
  • Finish core CRUD and lifecycle features
  • Polish mobile UX and ship an MVP

Other projects