Case studies

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 a whole project told in order, from the brief to the result. Numbers about a client's business are the client's own and are labelled that way.

• 01How Loopin syncs offline data to Google Drive without losing a writeLoopin offline sync client outcome: what it means for your project. What changes in the plan and what I will need from you. Verdict first, then the detail.
• 02Why MojoDocs runs 1,100+ tools in the browser, not on a serverMojoDocs runs 1,100+ tools in your browser using WebAssembly. No uploads, full privacy, and 4.8/5 rating. But it needs a modern device with enough RAM.
• 03Paper to platform: brief, delivery, resultA multi-tenant platform can cut lead-to-delivery time from weeks to days. Based on real project data. What you can expect and when it applies.