Static export vs server build: where does your API key end up?
One Next.js config, two build targets. The only difference that really matters is who can read your API key: your server, or every visitor.
Notes on web, mobile, and backend engineering, from shipping secure software in regulated products
One Next.js config, two build targets. The only difference that really matters is who can read your API key: your server, or every visitor.
A build that only works on one machine is a liability. Moving release builds into a pipeline makes them repeatable, auditable, and safe to hand to anyone on the team.
A fingerprint prompt feels like security, but it only unlocks something. What matters is what it unlocks, and where that thing lives.
When two financial institutions want the same product with different brands and rules, the answer is configuration, not branches.
Rejections are rarely a surprise. A short, boring checklist run on every release removes most of them.