Blog
Field notes on software that ships.
Practical, technical writing from the Appsarmy team — mobile, AI, fintech, and the engineering behind getting software into production. No fluff, no listicles.
Where an AI agent should stop and ask
Autonomy is the wrong axis. Sort actions by what you can take back, and the design falls out of the classification.
Read the articleiOS build infrastructure: it isn't about runners
Compute is a commodity you can buy today. Signing is a custody problem, and it is what stops releases.
Read the articleMobile banking app architecture: where the line falls
Every guide draws a different number of layers. The count is not the design — single ownership of each answer is.
Read the articleWhat a banking app is allowed to keep on the device
The dangerous storage is rarely the storage you wrote. Four channels put data on disk with nobody deciding to.
Read the articleThe EU Accessibility Act and your banking app
Your authentication flow is named in the directive, your copy has a reading-level ceiling, and the standard moved in September.
Read the articleThe release constraints nobody plans for in a bank app
Three gates stand between your fix and your customer. The bank controls none of them, and web habits assume otherwise.
Read the articleBuilding a custom Flutter client on OBDX
The API layer does not care which client calls it. The device-trust layer does, and that is the half you rebuild.
Read the articleIndia's DPDP Act for teams shipping software
Almost none of it is in force yet, the famous 72-hour rule least of all. The part that needs the full runway is erasure.
Read the articleWhat actually drives the cost of a fintech app
Five variables move the number by multiples, and screen count is not one of them. One button, seven subsystems.
Read the articleWhat an OBDX developer actually needs to know
Four skill layers stacked, and only two can be hired in the open market. The platform layer has no public learning path at all.
Read the articleOnboarding an external engineer onto a bank's stack
The delay is never the skill. The longest track is started last — and the start date is a fiction everyone agrees to.
Read the articleThe vision variables nobody budgets for
Your cameras were sited for human eyes, and humans are far more forgiving than models. Four of the five variables are physical.
Read the articleFlutter app size: where it actually goes
Three contributors, three different levers — and the biggest single win changes how you ship rather than what you build.
Read the articleHow many cameras can one GPU actually handle?
Published answers range from 4 streams to 100. Decode and inference saturate independently, and you are capped by whichever gives way first.
Read the articleWhen to retrain a vision model
You have no labels in production, so you watch proxies. And most apparent drift is a knocked camera, which retraining would entrench.
Read the articleMaking an OBDX mobile app feel fast
The client is rarely the bottleneck. Count the host calls per screen — six sequential ones cannot beat six times the core's latency.
Read the articleClassify before you extract
You cannot validate a field you cannot name. And a forced-choice classifier will label an unseen document confidently, and wrongly.
Read the articleOBDX for Islamic banking: what lives where
Murabaha and Ijarah are core concerns. The channel's job is presentation — and relabelling interest as profit is not a string swap.
Read the articleGetting extracted document data into a core banking system
The product hands you a JSON object. Five things have to happen before that is a customer record, and none of them ship in a product.
Read the articleA banking assistant on OBDX with Oracle Digital Assistant
The language model is the easy part. An assistant that can act is a channel, and it inherits every constraint the app has.
Read the articleField-level accuracy: the only OCR number that matters
A read that is 92% character-accurate can be 0% field-accurate. Three numbers get called accuracy, and only one predicts headcount.
Read the articleConnecting OBDX to a core that isn't FLEXCUBE
Core-agnostic means the interface exists, not that the connector is written. Four obligations per adapter, and your host has to answer all of them.
Read the articleOBDX mobile: remote UI or local UI
It looks like a performance trade-off. It actually decides who has to release before a customer sees a changed screen.
Read the articleOBDX Cloud Service or on-premise OBDX?
Pitched on cost, decided by data residency — and one question about extensibility the public material does not answer.
Read the articleAuthentication in an OBDX mobile banking app
Identity begins in IDCS, not OBDX. And the second factor resolves from segment, transaction and entity together — never one setting.
Read the articleOBDX architecture, for banks deciding whether to use it
It makes one real promise — that it does not care which core sits behind it — and that promise lives entirely in a single tier.
Read the articleWhy vision accuracy drops between the demo and the floor
The number did not drop. It was a measurement of someone else's dataset, and it never described your cameras.
Read the articleHow to choose a software development partner
Written by a vendor, with the disqualifiers included — the cases where you should not hire a firm like ours, stated plainly.
Read the articleLegacy modernisation vs digital transformation
One changes how a system is built, the other changes what the business does. The dependency runs one way, and that decides the sequencing.
Read the articleRunning an LLM on your own infrastructure
Weights are the easy part of the GPU budget. Context length times concurrency is what actually decides your hardware — and the model is the smallest part of the build.
Read the articleEdge vs cloud for video analytics
Cameras stream whether or not anything happens. That one fact inverts the usual cloud economics and normally settles the architecture.
Read the articleAdding AI analytics to CCTV you already own
You rarely need new cameras. What decides it is ONVIF and RTSP support, where the camera points and how the light behaves — not the age of the hardware.
Read the articlePPE and safety detection on a factory floor
Detecting a missing hard hat is the easy part. The zone and dwell logic between a detection and an alert is what decides whether anyone keeps using it.
Read the articleCore banking integration: what actually connects to what
Protocol translation is the easy part. Idempotency, ambiguous timeouts and the three reconciliations are what decide whether an integration holds.
Read the articleCustomising OBDX without breaking your next upgrade
Extension points per tier, what Oracle will not let you override, and why most upgrade pain is self-inflicted.
Read the articleSecuring a Flutter banking app: pinning, RASP and root detection
More banking apps have been taken offline by their own certificate pinning than saved by it. What each control buys, and the rotation mistake to avoid.
Read the articleHow to build a mobile banking app
Written for a bank, not a fintech startup. Compliance is not your constraint — the core's API surface, channel parity and migrating existing customers are.
Read the articleHow to write a software RFP
From the side that reads them. Why ambiguity gets priced rather than queried, and the questions that produce answers worth comparing.
Read the articleIs Flutter ready for a bank's app? An honest risk assessment
Not whether it can build the app — it can. The questions a risk committee actually asks: continuity, platform-version lag, hiring, and accessibility.
Read the articleHow to modernise a legacy app without a rewrite
Big-bang rewrites fail for reasons that have nothing to do with engineering skill. The incremental alternative, and the four-way decision to make per component.
Read the articleGDPR when you outsource development to India
Outsourcing moves the work, not the liability. What a DPA, standard contractual clauses and a transfer impact assessment have to cover — and the scoping question that removes most of the risk.
Read the articleSelf-hosted vs managed CI/CD: who keeps the source
Usually argued on cost and features. The decision that matters is where your source code executes — and there is a third option most comparisons leave out.
Read the articleOn-prem vs cloud AI inference: the real cost tradeoffs
Cloud inference is cheap to start and expensive to scale. A practical look at when on-prem or edge inference wins on cost, latency, and data control — and when it doesn't.
Read the articleFlutter vs React Native for enterprise apps
Both ship genuinely native apps. The honest decision comes down to your team, your existing codebase, and the kind of UI you're building — not a benchmark.
Read the articleHow to build a fintech app: compliance and architecture
The hard parts of a fintech app aren't the screens. A walk through the compliance and architecture decisions — auth, core integration, PCI DSS, KYC — that make or break it.
Read the article