Articles
How the systems behind commerce products are actually built - data models, real-time delivery, offline writes. Each piece compares the options and makes a call.
-
The team-extension model: how embedded engineers actually integrate
Team extension fails when it's run like outsourcing with a different invoice. It works when the engineer reports to your lead, owns outcomes, and the first month is designed rather than improvised.
-
PWA or native for a commerce app
The PWA-versus-native argument is usually fought over capability. For a commerce app it's decided by distribution and update cadence - and those point one way until a specific condition flips them.
-
Offline-first is a data problem, not a caching problem
A service worker makes an app open offline. Making it work offline - accepting writes it can't send yet - is a different problem, and caching doesn't touch it.
-
Real-time order tracking: polling, SSE or WebSockets
'Real-time' is not one requirement. An order-tracking screen usually has three different update streams, and each wants a different transport. Here's how to choose.
-
Where the tenant boundary goes in a marketplace
Multi-tenancy patterns are written for SaaS, where tenants never meet. A marketplace breaks that assumption - buyers cross stores, and the data model has to follow.