Mobile app development is turning an idea into a published, updatable and secure product in the store. I develop native apps for iOS and Android, cross-platform apps with Flutter, and enterprise field applications. ERP/CRM integration, offline operation and secure data are at the centre of this work.
Mobile app development covers turning an idea into user flows, a data model, an interface and a working product. The work is not just writing code: store rules, device permissions, security, integrations, release management and post-release maintenance are all part of it.
There are two main paths. Native development is done with Swift for iOS and Kotlin or Java for Android. In cross-platform development, a framework such as Flutter ships to two platforms from a single codebase.
| Criterion | Native (Swift / Kotlin-Java) | Flutter |
|---|---|---|
| Initial cost | Two separate codebases, higher | Single codebase, lower |
| Hardware access | Broadest and most current | Sufficient for most needs; a native module is required only in very specific cases |
| Interface control | Full platform compliance | Same look on both platforms, full control |
| Maintenance | Maintaining two separate versions | Maintaining a single version |
| Where it fits | Heavy hardware, AR, platform-specific products | Business apps, MVP, multi-platform products |
The page where I explain the Flutter side in more detail: Flutter expert.
At E-Veri Bilişim I led the team that built products such as Turkcell Müzik (Fizy), Hürriyet E-Gazete, Mikro mobile accounting, ERP mobile and an FMCG survey app.
As CTO at Açık Deniz Bilişim I set up the architecture of enterprise B2B products. For FMCG field teams we developed Flutter, native Android (Java) and iOS (Swift) apps: task, survey, location-based reporting and ERP integration. End-to-end encrypted communication and secure file storage were also part of this product family.
At DoktorAsistan I built the mobile and web side end-to-end for patient and doctor communication; AI-assisted question-and-answer, notifications and CRM flows run in the same product.
I explained what costs depend on in my article mobile app prices.
The price is determined by the number of screens, integrations, design status, security needs and the number of platforms. Giving a single figure would be misleading. After the discovery phase I provide an itemised quote broken into stages.
A small, clearly scoped MVP usually ships within 4-8 weeks. The timeline extends as enterprise integration, multiple roles and offline scenarios are added. Store review time should also be accounted for.
Yes. I have previously built mobile apps integrated with ERP and CRM systems. The integration method (API, middleware, direct database) is decided according to the existing system's capabilities; permissions and error scenarios are designed separately.
Apple review usually takes 1-3 days; Google Play review takes from a few hours to a few days. A rejection may come from a missing privacy policy, permission explanation or test account; that is why I apply a pre-release checklist.
Yes. Operating system versions, store policies and third-party services change constantly. It can also be handed over without a maintenance agreement, but without regular updates the app will eventually run into store or device compatibility problems.
Yes. Usually a shared backend and admin panel are set up; mobile and web both use this service. This structure lowers cost and lets the data be managed from a single source.
