Mobile app development
I build iOS and Android apps from a single Flutter codebase. Store account setup, the release process, the update pipeline, ads and in-app purchases are all part of the job.
What I lean on when saying this is not a portfolio mockup: I wrote the word game Kelimely from scratch, and it is live on both stores.
Scope — what's included
-
App development
One Flutter codebase for iOS and Android. Interface, state management, offline behavior and platform-specific details (notification permissions, back button, safe areas).
-
Store release
App Store Connect and Google Play Console setup, certificates, signing, store copy and screenshots. If review rejects the build, resolving the reason and resubmitting is included.
-
Revenue model
AdMob ads or in-app purchases. I built both into Kelimely, so subscriptions, one-off purchases and remove-ads flows are familiar ground.
-
Server side
If the app needs data, I write the API too: Go or Java/Spring with PostgreSQL. When app and server come from the same hands, the mismatch problem disappears.
-
Release pipeline
Version numbering, test distribution (TestFlight / internal testing) and the update flow. Shipping a new version becomes routine instead of an event.
-
Store visibility
App name, subtitle, keywords and description — so you get found in store search. Same logic as web SEO, different rules.
How we proceed
-
1. Scope
What genuinely belongs in version one, and what can wait. The most common mistake is inflating the first release with everyone’s wishes.
-
2. Design and flow
Screens and the transitions between them get drawn. We agree on the flow before code is written.
-
3. Development
The app ships in pieces; you can install intermediate builds on your own phone and try them.
-
4. Store process
Accounts, certificates and store copy are prepared and the build enters review. Apple review can take several days, so we plan around it.
-
5. After launch
Crash reports get monitored and a fix release follows the first round of user feedback.
Why me
- Kelimely — a Turkish word game. Written in Flutter; live on the App Store and Google Play, with AdMob and in-app purchases.
- The game’s web side, kelimely.com, is mine too: Vue 3 front end, Go server.
- 9 years of engineering: fintech payment flows, a NATO command-and-control interface, radar data analytics.
- Because the same person writes the app and the server, the "is it the app or the backend" argument never starts.
Frequently asked
Are iOS and Android priced separately?
No. Since it is a single Flutter codebase, both platforms are priced as one project. Platform-specific extras (say, an integration that exists only on iOS) are discussed separately.
Whose name are the store accounts in?
Yours. You own the Apple Developer and Google Play Console accounts; I work with developer access. The app is always your property.
What if Apple rejects the app?
It happens often and counts as part of the process. The rejection reason gets read, the gap gets closed, the build gets resubmitted. I went through all of it shipping Kelimely — there is no extra charge.
Is maintenance needed after launch?
Yes. Apple and Google change rules a few times a year, and staying in the store can require an interim release. I can keep doing that, or you take the code and continue with your own team.
I already have an app — would you take it over?
If it is written in Flutter, yes. If it is another technology, I look at the code first and tell you plainly whether taking it over or rewriting it makes more sense.