Services
Four areas I take on, each one tied to a project already in the Work section so you can check the result before starting a conversation.
Mobile App Development
Cross-platform apps built from the navigation structure and state layer up to the screens people actually use. The work runs through to a release build on Android and iOS, not a prototype that stops at the design file.
Who it's for
Teams with a defined product who need it built as a shippable app by someone who will own the structure, not just the screens.
See it in action
28 screens and 12 flows across loan, repayment, profile and complaint journeys, published on Google Play as Safco eCredit.
SAFCO E-Credit · Google Play
MVP Development for Startups
A first working version with the core journey complete — authentication, the primary flow, and a real backend behind it. Scope stays on what has to exist before the product can be put in front of users.
Who it's for
Founders validating an idea who need something functional to test with, rather than a click-through mock.
See it in action
Built to a functional MVP: 13 screens covering service center browsing, booking, appointment tracking and profile, on Supabase auth and tables.
QueueLess · GitHub
API Integration & Backend Connectivity
Connecting an app to the services behind it: REST endpoints, authentication, persisted sessions and third-party gateways. Integrations sit behind a centralized service layer so they stay readable as the API surface grows.
Who it's for
Teams with an existing backend or third-party provider that needs to be wired into a mobile client reliably.
See it in action
A service layer of 30 methods against the SAFCO APIs, with JazzCash, EasyPaisa, HBL Connect and PayPro payment flows through WebView redirects.
SAFCO E-Credit · Google PlaySupabase auth with automatic session restore, over profiles, centers, center_services and appointments tables.
QueueLess · GitHub
App Maintenance, Bug-Fixing & Performance
Continued work on an app that is already running: fixing defects, tightening slow screens, and reducing the structural mess that makes each change harder than the last.
Who it's for
Teams with a live or in-development app that needs steady upkeep and targeted improvement rather than a rebuild.
See it in action
Maintained as a live Android release at version 1.16, with reusable form controls and persisted language and theme state.
SAFCO E-Credit · Google PlayMemoized filtered lists, SQLite caching and skeleton and empty states introduced to keep browsing responsive.
FoodApp · GitHub
How I work
The order a project usually moves in, from the first conversation to release.
Discovery & Scope
We agree what is being built, in what order, and what is out of scope, so both sides are working from the same picture.
Planning & Architecture
Navigation structure, state layer and the way the app talks to its backend are settled before screens are built, so the foundations do not need reworking later.
Build
Built in small, reviewable steps in Git, with progress shared as it lands so feedback arrives while changes are still cheap.
Test & QA
Checked on Android and iOS, with defects fixed and the loading, empty and error states covered before anything is released.
Deploy & Handover
A release build goes out through the store, then the code and the context needed to keep working on it are handed over.
Think one of these fits?
Send the project type, budget and timeline and I will tell you honestly whether I am the right person for it.
Every example above is covered in more detail in the Work section.