Skip to Content

Apps

Native Android app development

I build native Android apps in Kotlin and Jetpack Compose that keep working without a connection and protect the data they hold. I wrote FYRA Finance, an encrypted offline ledger, and a GPS and camera field app for solar rooftop registration. I take apps through to Play Store release.

Updated

Problems this solves

  • Your field staff work in places with weak signal, and a web form that needs a connection loses their entries.
  • Your app is slow or crashes on the cheaper phones your users actually own.
  • The app stores sensitive records, and you worry about what happens if a phone is lost or shared.
  • Your last developer left a codebase nobody can update, and the Play Store keeps rejecting new builds.

What I build

  • Offline-first apps that save every entry on the phone and sync in the background once there is signal
  • Encrypted on-device storage for finance, health-adjacent or business records, using SQLCipher and the Android Keystore
  • Field apps with GPS, camera, QR scanning and photo capture
  • Clean Jetpack Compose interfaces that stay responsive on low-end phones
  • Sign-in, roles and server connections to Firebase or your own backend
  • Play Store setup, signed release builds and ongoing updates

How it works

  1. 1Define the essentials

    We list who uses the app, where they use it and what must work offline. You get a short plan and screen sketches before any code.

  2. 2Build the data layer

    I set up local storage and sync first, since that is where field apps fail. You get an early build to try on a real phone.

  3. 3Test on real devices

    I test on budget and mid-range phones and on poor networks, then fix what breaks.

  4. 4Release and hand over

    I prepare the Play Store listing and signed builds, then hand over the source and the accounts.

Work that shows it

Tools I use

  • Kotlin
  • Jetpack Compose
  • Coroutines & Flow
  • SQLDelight
  • SQLCipher
  • WorkManager
  • Firebase
  • ML Kit
  • Play Console

Working with clients abroad

I work remotely with clients worldwide from Assam, India, and in person across Assam and Guwahati. Quotes are in USD and paid by Wise or international bank transfer. Code lives in your GitHub from day one, and you get a staging link to try at every step.

Questions

Native code gives the best offline behavior, battery use and access to the camera, GPS and secure storage. If you need iPhone too, I will say honestly whether a shared approach fits your case.
Yes. I work remotely, so you can be anywhere: the US, UK, Germany, UAE and elsewhere, with scheduled calls and written updates. I test on real devices and send you builds to try on your own phone.
You do. The Google Play developer account, signing keys and repository belong to you, and I hand over the full source and documentation at the end.
Yes, if it is designed that way from the start. Data is saved on the phone and sent to the server when a connection returns, with rules for handling conflicts.
It depends on the features and how much data syncing is involved; you get an estimate after a first call, and a working version to try early. Quotes for overseas clients are in USD.

Tell me what you have in mind, and I'll tell you how I'd build it.