A mobile marketplace where the product is a file, not a parcel

The challenge

Selling a digital good moves all the interesting work to after checkout: entitlement, protected access to the machine-ready asset, and a share path that matches how these files actually travel between workshops - which is WhatsApp and Telegram, not a download manager. The second problem was presentational. An embroidery professional buys on stitch count, needle and colour count, and design code. Bury that specification and the screen is useless to them; lead with it badly and it reads as a spreadsheet.

Our approach

Sharing was treated as a first-class delivery channel rather than something bolted onto a download button. The technical specification went directly under the design preview - on the primary product surface, because it is the purchase criterion, not supporting detail. The catalogue was modelled with typed response models per endpoint instead of untyped maps, so an API change fails at compile time rather than in a customer's hands.

What we built

• Categorised catalogue with banner carousel and per-category design rails
• Product detail leading with stitch count, needle/colour count and design code
• Razorpay checkout, with direct purchase and pack-based redemption
• Downloads library with device save and direct WhatsApp/Telegram sharing
• Firebase push notifications and Crashlytics stability reporting

The results

Shipped to production on both stores and versioned past its first major release. Built inside a shared team repository alongside other developers.