Reinhard BonkeTricreta
Service

Software Development in Kenya

I build mobile and desktop applications for businesses whose workflow does not fit off-the-shelf software — including apps that keep working when the connection does not.

Custom software is worth building when the alternative is bending your operation around a product that was designed for someone else's. The apps in the case studies exist because nothing on the shelf did the job: a monitoring system for a fleet of devices, a savings tool, an SMS operation, an agent sales app that passed 5,000 downloads.

Offline-first matters here more than it does in most markets. An app used by a field agent in Kisii cannot assume a connection, so state is held locally and reconciled when the network returns rather than failing in front of a customer.

Where a mobile app is part of a larger system — payments, dashboards, automations — it gets built as part of that system rather than as an island with an API bolted on afterwards.

What this fixes

  • Manual processes
  • Disconnected workflows
  • Generic software

Work that proves it

See all case studies

Tools and platforms

  • Flutter
  • Dart
  • Android
  • Kotlin
  • Java
  • Firebase
  • SQLite
  • Supabase
  • REST APIs
  • Offline-first
  • Push Notifications
  • Play Store

Common questions

Do you build for Android and iOS?
Yes — cross-platform with Flutter where a single codebase serves both, and native Android with Kotlin or Java where the job needs deeper platform access.
Can the app work without internet?
Yes. Offline-first is the default for anything used in the field: the app holds state locally and reconciles when the connection returns, rather than failing at the moment someone is standing in front of a customer.
Do you publish to the Play Store?
Yes, including store listing, assets and the review process. Several of the apps in the case studies are live on Google Play.

Other things I build