
Who this is for
- Founders whose app is live but whose developer has moved on, and who need someone to pick up the code and keep releasing.
- Teams with an app that has fallen behind: an old Flutter version, outdated packages, or a build the stores no longer accept.
- Products with real users that need crashes fixed and small features shipped steadily, without hiring a full-time developer.
- Apps I built, after launch support ends.
What you get
- A code review to start. Before taking over an app I read the code, build it for both platforms and tell you what state it’s in: what’s solid, what’s risky and what to fix first.
- Store releases handled. Builds, versioning, App Store Connect and Play Console, store listings, screenshots and review, so updates actually reach your users.
- Upgrades. Flutter, Dart and package updates, and the native Android (Kotlin) and iOS changes they bring, kept current so you’re not facing a big, risky upgrade later.
- Crash monitoring and fixes. Crash reporting and analytics set up if they’re missing, then the crashes that affect the most users fixed first.
- CI/CD. GitHub Actions or GitLab CI/CD pipelines that test and build the app, so releases are repeatable instead of done by hand on one laptop.
- Backend care. Firebase, Supabase or Node.js work: Auth, Firestore, Storage, push notifications, REST and GraphQL APIs.
- New features built the same way as a new app: scoped, designed if needed, and delivered as test builds you try before release.
How the work runs
- 01 · Review. Access to the code, stores and backend, a first build on both platforms, and a short written report on the state of the app.You get: a clear list of fixes and risks, in order
- 02 · Plan. We agree what to fix first and what new features matter, with a fixed quote for each piece of work.You get: a scoped plan and estimate
- 03 · Fix and build. Work in short sprints, with a TestFlight or Google Play test build for you to install before anything goes live.You get: tested builds
- 04 · Release and monitor. Store submission and review, then crash monitoring and analytics as users update.You get: the update live on both stores
Tech stack
- App: Flutter, Dart, Kotlin, Swift, Android SDK; Bloc, Provider and GetX codebases on Clean Architecture or MVVM.
- Backend: Firebase (Auth, Firestore, Storage, FCM), Supabase, Node.js and Express, Django, PostgreSQL, REST and GraphQL.
- Quality and delivery: unit, widget and integration tests, GitHub Actions, GitLab CI/CD, App Store Connect, Play Console, Postman.
Cleaning up an app’s data layer? The free JSON to Dart converter generates null-safe model classes from your API responses.
Apps I’ve released and maintained
I’ve owned App Store and Play Store releases in my work, including as a remote Flutter developer for Unique Solutions in Dubai from July 2024 to September 2025. These apps are live on the stores:
SheDrives: Ride-Sharing · Safety
A women-exclusive ride-sharing app connecting verified female drivers with female passengers — built around trust, with live tracking and one-tap SOS support. My part: Flutter developer in a team of 4: app enhancements, real-time tracking and bidding fixes (WebSockets), and QA. (10K+ downloads.)
DapUp: Social Networking
A real-time, location-based social platform that helps people discover nearby friends through mutual connections — with live maps, a moments feed and instant messaging. My part: Issue fixing in the Flutter app. (★ 5.0 on the App Store.)
Evoke AI: AI · Creative Tools
An AI creative studio in your pocket — generate, edit, restore and convert images and files with cloud AI pipelines, from background removal to text-to-image. My part: Co-built with one other developer: in-app purchases, ads, AI photo editing, web tools, file converters and QA. (★ 4.9 on the App Store.)
Questions
Can you take over an app another developer built?
Yes. I’ve worked in codebases using Provider, Bloc and GetX, on Firebase and on custom APIs. I start with a review so you know what you’re dealing with before you commit to more work.
My app was rejected or removed from a store. Can you help?
Send me the message from Apple or Google. Most rejections point to something specific: a missing permission explanation, a privacy detail, an outdated SDK level. I’ll tell you what it means and what the fix involves.
How is maintenance priced?
Each piece of work is scoped and quoted before I start, so you know the cost up front. Tell me what the app needs and how often you release, and we’ll agree what fits.
How do we work across time zones?
Lahore is one hour ahead of the UAE, so the working day is almost the same. For clients elsewhere we agree a fixed overlap for calls, and most maintenance work runs through written updates and test builds.
Do you sign NDAs?
Yes. Send yours with your first message and we sign it before you share access or code.
Need someone to look after your app?
Tell me what the app is, where it’s live and what’s going wrong. I reply within 24 hours with first questions, then we can do a free 30-minute call. Building something new instead? See Flutter app development.