Why offline-first matters in Android products
Whether it is a travel app, a sales tool, or a field workflow, Android users still hit weak signal and dead zones. Offline-first design keeps the experience useful when the network is not.
Read article
Back to Portfolio
THOUGHTS & NOTES
TECH ARTICLES
A few essays on product, Android, and modern product engineering.
Working better with Android architecture, NFC, and hardware integrations
Good architecture makes it easier to connect Kotlin, Compose, BLE, NFC, and device integrations without creating brittle app logic that breaks under pressure.
Read article
How payments really work when you tap your phone
Behind every tap is a secure flow of tokenization, checking, and network approval. Here is what actually happens in a modern payment interaction.
Read article
Android Kotlin, NFC, and Bluetooth in real products
These technologies solve different problems, and product teams do better when they treat them as distinct flows with different limits and failure modes.
Read article
Why payment apps fail when the network is weak
Most product failures are really state and connectivity problems. The better product is the one that recovers clearly when the signal drops.
Read article
Bluetooth in Android POS and device workflows
Bluetooth is persistence, pairing, and recovery. Real device products need to design around those states instead of assuming perfect connections.
Read article
What NFC is really doing behind a tap
NFC is a deliberately limited and secure interaction pattern designed to reduce fraud and accidental reads.
Read article
Queueing retries and trust in payment flows
If the state is unclear, the product starts to feel unreliable even when the system is trying to help.
Read article
Thamani: understanding the real cost of mobile money
A project walkthrough of how Thamani turns SMS transaction data into clear fee insights, better decisions, and a more trustworthy mobile money experience.
Read article