How to2 min read
How much does an app cost in 2026?
There is no single number, but there is a method. Here is how we turn a rough idea into a range you can plan around, and what makes that range move.
- Pricing
- Process
Blog
What we have learned building things
Occasional, specific and written by the people doing the work. If you would rather see it applied, read our case studies or estimate a project.
Subscribe via RSSHow to2 min read
Native or cross-platform: how we actually choose
We default to Flutter for cross-platform work and go native when the project earns it. The decision comes from constraints, not fashion.
- Mobile
- Engineering
How to2 min read
What an MVP should actually contain
Most MVPs fail because they are either too small to prove anything or too large to ship. Here is how we decide what goes in.
- Product
- Startups
Tech2 min read
Integrating mobile money: what actually breaks
Card-shaped assumptions are the reason mobile money integrations fail. What changes when the wallet, not the card, is the default way your customers pay.
- Fintech
- Engineering
How to2 min read
Build, buy or adapt: choosing a learning platform
Most organisations do not need a custom LMS, and the ones that do usually know why. A decision framework from a team that builds and runs one.
- Product
- Education
Tech2 min read
Why offline-first is not optional in our markets
If your product assumes a stable connection, it will fail exactly when people need it. Designing for intermittent networks changes the architecture, not just the UI.
- Engineering
- Mobile
Tech2 min read
The API security checks we run on every build
Not a survey of every threat that exists — the specific, unglamorous checks that catch most of what we find in real reviews.
- Engineering
- Security
How to2 min read
How we estimate software, and why we quote ranges
A single number implies a certainty nobody has before scoping. Here is the method behind our estimator and what makes an estimate move.
- Process
- Pricing
How to2 min read
The accessibility checks we run before release
Accessibility fails in the same few places on almost every project. Catching them costs minutes during the build and days afterwards.
- Design
- Engineering
From our founder
More writing on kapolbrondon.com
Longer-form pieces published on kapolbrondon.com, pulled in automatically.
kapolbrondon.com
Oracle Development When the Model Needs Verified Data
When AI workflows depend on structured data, the database layer cannot be an afterthought. Here is how Oracle development discipline kept a production AI product correct under real load.
kapolbrondon.com
Next.js Development When the Model Has to Be Right
A technical breakdown of how structured outputs and human-gated workflows made AI reliable enough to ship in production, drawn from real constraints across multiple AI products.
kapolbrondon.com
Technical Due Diligence Is What Keeps Teams Shipping After You Leave
A decision guide for founders who need to know whether their engineering team will hold together once the build gets hard. Covers what technical leadership actually requires and why the wrong choice stalls growth.
kapolbrondon.com
What Fintech Demands from SaaS & Product Software Development
Correctness in financial systems is not a quality attribute you can defer. This essay lays out the working principles that separate fintech-grade product engineering from ordinary SaaS builds.
kapolbrondon.com
Firebase Development When the Market Has Its Own Rules
Building for Cameroon means navigating payment rails, compliance requirements, and connectivity constraints that most Firebase tutorials never mention. Here is how an engagement actually runs.
kapolbrondon.com
Components Are a Contract in Full-stack Product Engineering
A component library nobody can read is a liability. Here is how Storybook documentation and visual regression testing kept a design system alive when the second team arrived.