The engineering behind the systems we build. These deep dives are for developers: the Frappe framework behind ERPNext, why we build on it, offline-first web apps, adding AI to existing applications, and Vue 3 on a Frappe backend.
Browsers cannot reach a Bluetooth Classic thermal printer, but a native WebView host can. This is how to build a safe JavaScript bridge, generate ESC/POS, and keep the printer connection alive.
Forwarding an SMS to a webhook looks trivial until real conditions hit it: dropped networks, reboots, battery killers, duplicate messages and forgery. This is how to engineer a gateway that survives all of them.
Frappe is the full-stack, metadata-driven Python and JavaScript framework that powers ERPNext. Here is what it actually is, how its core pieces fit together, and when it is the right foundation to build on.
How to put a modern Vue 3 single-page application in front of a Frappe or ERPNext backend: authentication, the REST API, the frappe-ui resource layer, routing, and shipping it as a bundled custom app.
A pragmatic engineer's guide to adding AI to software you already run: choosing a use case that pays off, using hosted APIs and retrieval over your own data, and building for cost, latency, and graceful failure.
The engineering case for starting from ERPNext and Frappe rather than an empty repository: what you get for free, what it costs, and how to build custom software on top without painting yourself into a corner.
How to build web apps that keep working when the network does not: service workers, IndexedDB, a durable sync queue, and conflict resolution, drawn from shipping software for real Kenyan connectivity.
Not sure where to start? Tell us how your operation works and we will point you to the right system.
Talk to us