Privacy by Architecture
Why local AI changes software architecture, not just privacy policies. When data never leaves the device, an entire category of risk disappears with it.
Read the article
Real engineering. Real lessons. Real products.
FarmakoMed as the practical case study.
A health-specialized model looked like an obvious upgrade. It took a missing off-ramp, two false leads, and a rigged test before we got an honest answer about whether it belonged in the app.
A real performance investigation that started with the obvious suspect, the inference backend, found a lifecycle bug one layer up, then found a second reload nobody had questioned, and put real device numbers behind GPU and NPU.
The industry is obsessed with parameter counts. But model size is only one dimension of quality, the real engineering challenge is choosing the right model for the task.
We spend enormous effort protecting how data enters a system, and almost none designing how it leaves. Why outbound paths are the trust boundaries that matter.
How Small Language Models and Edge AI could make artificial intelligence accessible to billions of people.
Why using an external AI model doesn't make FarmakoMed beholden to its vendor, and why sovereignty lives in the architecture, not the components.
Why building seamless on-device AI forced us to redesign our application architecture instead of our machine learning models.
How tokens quietly became the currency of artificial intelligence, and why on-device AI offers a different vision.
Why local AI changes software architecture, not just privacy policies.
Why selecting the "best" open model matters less than understanding your product's constraints.
Debugging on-device AI when you can't rely on server logs or remote sessions.
Why battery life should be treated as a first-class feature, not an afterthought, when building AI-powered mobile applications.
Why the future of artificial intelligence should be measured not only by intelligence, but also by its environmental footprint.
Why keeping an app alive should never make it slower, treating a long background stay as a health check instead of waiting for a restart.
Every article is tagged. Filter by topic to find exactly what you need.