Enes E.

I build iOS and Android apps and get them live on the App Store and Google Play. 9 years in mobile, 6 of them freelancing: 44 projects, 100% Job Success Score, Top Rated, 4.9 across 33 reviews. Getting a screen working is the easy part now. Mobile projects stall at the end. An App Store rejection that cites a guideline number and explains nothing. Provisioning that expired on the one machine able to cut a release. A subscription your backend thinks is active and StoreKit thinks lapsed. A crash that only happens on a real device on a bad connection. The stretch between "it runs in the simulator" and "it's in the store with paying users on it" is where most of my work happens, and it's the part AI tools don't cross. I write native by default, Swift on iOS and Kotlin on Android, because that's where the platform stops fighting you: StoreKit, background work, camera and location, anything that has to feel right under the thumb. Flutter or React Native when the project calls for it, usually one team shipping both platforms on a startup budget, or an existing cross-platform codebase that needs someone who can drop into the Swift and Kotlin layer when a plugin breaks. What I build Finishing what someone else started. A prototype built with AI that runs on one laptop with the keys sitting in a file. A codebase from a developer who stopped answering. An app rejected twice with nobody sure why. I read the code before quoting anything and tell you what's worth keeping. Sometimes the answer is that a rewrite costs less than the repair, and I'll say so. Full builds from scratch. A Figma file or a rough idea through to a published app: architecture, native implementation, backend, payments, release. Fixed price against a written scope, so a bad estimate is my problem rather than your budget's. AI features that survive contact with a real app. Chat and assistant flows, document and image understanding, personalization. The hard parts aren't the API calls. They're what the screen does while tokens stream in, what the user sees when the model is confidently wrong, what it costs per active user, and what App Review asks once your app generates content. Backends and integrations. Firebase, Supabase, REST APIs, third-party SDKs, subscriptions through RevenueCat, StoreKit and Play Billing, maps and location, real-time features, analytics and crash reporting. Apps that got slow or fragile. Performance work, architecture cleanup, CI/CD and release automation, so the next feature doesn't cost double what the last one did. Stack iOS: Swift, SwiftUI, UIKit. Android: Kotlin, Java, Jetpack Compose. Cross-platform: Flutter, React Native. Backend: Firebase, Supabase, REST APIs, Node.js. AI: Claude API, OpenAI API, Gemini. Payments and subscriptions: RevenueCat, StoreKit, Google Play Billing, Stripe. Also maps and location services, push notifications, deep linking, analytics and crash reporting, Git, CI/CD, App Store Connect and Play Console release management. How I work I ask what the app is for before I ask what it should look like. I'll tell you when a feature isn't worth building, and occasionally that the thing you want doesn't need a native app at all. I price the project rather than the hour, which means working faster is in my interest instead of yours to pay for. Tell me where your app is stuck and I'll tell you what it takes to get it live, what I'd cut, and how long it takes. That part costs nothing.