Projects
Projects
How one of my products is put together, and why.
3 pages in this section. Each one opens with a short answer, goes deeper, says where the advice does not apply, and ends with the questions people ask next. Written by Sachin Sharma. See the editorial policy.
Read these if you want to see how a product is thought through before it is built: the problem, the one decision that mattered, and what the product includes. They describe my own products, from their own documentation.
- 01Aashwasan: architecture, decisions, regretsAashwasan uses Flutter and Firebase for real-time agreement workflows. Learn about access rules, offline sync, and common failure modes in production.
- 02Loopin: architecture, decisions, regretsLoopin's offline-first design with Google Drive sync. UUIDv7 keys, last-write-wins conflicts, and why no server is needed. Real-world setup and failure modes.
- 03Wally: architecture, decisions, regretsWally uses local caching and adaptive loading to feel fast on 2G and 3G. Learn the design choices, risks, and what I’d change today.