Mobile app development in Türkiye: iOS and Android apps from idea to store release
Pan Innovation House is a software company headquartered in Gaziantep, Türkiye, with a second office in London. If you want a mobile app built, we work through the idea with you, then design, develop and publish your iOS and Android app on the App Store and Google Play. We work remotely with businesses across Türkiye; the source code we write and your data are handed over to you as defined in the contract.
- Source code handover written into the contract
- A written scope and a firm price
- A reply within one business day during office hours
What kind of mobile app do you want built?
Every app does a different job. These are not ready-made packages but the needs we meet most often; yours may combine several of them. We work out the scope together in discovery.
-
E-commerce mobile app
Products, basket and payment on the phone. If your platform's API allows it, the app uses the same stock and orders as your existing website, and you announce campaigns to your customers with push notifications.
-
Ordering and delivery app
For a grocery, restaurant or takeaway business, the customer app, the business panel and the courier screen are designed together. Orders are tracked live and delivery zones are defined.
-
Appointment and booking app
For a clinic, hair salon, gym, restaurant or rental business. Customers see free slots and book them themselves; a reminder notification goes out, and cancellations and changes follow set rules.
-
Field, service and warehouse app
Sales rep orders, technician service forms, warehouse counts and delivery records. With no connection the record waits on the device; when the connection returns it is synced and written to your ERP.
-
B2B dealer ordering app
Your dealers see their own price list, stock and account balance on the phone and enter their orders themselves. Orders land directly in your system instead of arriving by phone and message.
-
Loyalty and customer app
Points, a digital card, campaigns and personal offers. A café, store chain or service business talks to its customers through its own channel, without depending on an intermediary platform.
-
MVP for a start-up idea
A first version that tests, with the fewest features, whether the idea finds demand. We decide together what goes into the first version and plan the next step from user data.
-
From website to mobile app
Your existing website or e-commerce platform is carried into an app. Rather than wrapping the site in a shell, we add features that bring value, such as notifications, quick sign-in and a saved basket.
Apps for factory, warehouse and field teams
In-house apps such as warehouse counts, quality and maintenance records, sales rep orders and service forms have different requirements: recording with no connection, reading barcodes and QR codes, and passing the record to the ERP when the connection returns. We describe these apps separately on our industrial mobile apps page.
Industrial and enterprise mobile apps →Native, React Native or Flutter?
The right technology depends on what the app will do, who will use it and who will maintain it. For most business apps a single cross-platform codebase is enough; we give the reasons for the choice in writing during discovery.
-
Native iOS (Swift)
- When it is the right choice
- If the app is aimed only at iPhone and iPad users, or depends closely on the hardware of Apple devices.
- Keep in mind
- If an Android version is also needed, it is written as a separate project; two separate codebases then have to be maintained.
-
Native Android (Kotlin)
- When it is the right choice
- In field and warehouse projects that use handheld terminals, special scanners or Android devices only.
- Keep in mind
- If iOS is also needed, that means a separate codebase and separate maintenance.
-
React Native
- When it is the right choice
- In most business apps that reach iOS and Android from one codebase and use the same language as the web side.
- Keep in mind
- Special needs that work very close to the device may require separate native modules.
-
Flutter
- When it is the right choice
- In apps with heavily custom interfaces, where the screens must look exactly the same on both platforms.
- Keep in mind
- It uses the Dart language; keep this in mind when choosing the team that may take over the app later.
What drives the cost of a mobile app
The price is set by the job the app does, not by the number of screens. Once the six headings below are clear, we give a written scope and a firm price after discovery.
-
User roles and flows
An app used only by customers and a system with customer, business and courier screens are not the same job. Each role brings its own flow and permissions.
-
Admin panel and server
Managing products, orders, users and content needs a web panel and a server side. This part does not show on screen, but in most projects it is a significant piece of work.
-
Integrations
ERP, e-commerce platform, payment provider, courier, SMS and map services. Whether the other side has a ready API directly affects time and cost.
-
Working offline
An app that records with no connection and syncs later needs conflict rules, so it takes more work than an app that is always connected.
-
Design depth
There is a clear difference in effort between a plain interface built from standard components and screens and animations drawn specifically for your brand.
-
Platform and technology choice
One codebase for iOS and Android, or two separate native apps? The second adds load to both development and maintenance after release.
The mobile app development process
- 01
Discovery
We talk about who the app is for and what job it should do. We map the target users, your existing systems and the services that need to be connected.
- 02
Scope and price
We pick the features for the first version and clarify the main flow with rough screen sketches. At the end of this step you receive a written scope and a firm price.
- 03
Design
We design the screens around your brand and the habits of iOS and Android users, and test them with a clickable prototype. We get your approval before any code is written.
- 04
Development
We build the app in working releases. You install each release on your own phone and follow progress in the app itself rather than in a presentation.
- 05
Testing
We test on real devices across screen sizes and operating system versions. We open the app to your team first, through TestFlight on iOS and closed testing on Android.
- 06
Store release and handover
We manage the App Store and Google Play submissions, the store texts and the review process. The source code we write, access details and set-up documents are handed over to you as defined in the contract.
Releasing on the App Store and Google Play: what to know in advance
Store release is not a step to think about on the last day of the project. Whose name the developer account is opened in, and which type of account it is, directly affects the release schedule.
-
12 testers on a personal Google Play account
On personal developer accounts created after 13 November 2023, an app needs a closed test in which at least 12 testers take part continuously for at least 14 days before it can go to production.
-
Organisation accounts are exempt
Google Play accounts opened as an organisation are exempt from the closed-testing requirement; this account type also requires a D‑U‑N‑S number. That is why we recommend publishing from an account opened in your company's name.
-
Apple organisation enrolment requires D‑U‑N‑S
To publish on the App Store in your company's name, you enrol with Apple as an organisation; this requires a legal entity and a D‑U‑N‑S number. Sole traders enrol as individuals. We start this at the very beginning.
-
Every release goes through App Review
Every version submitted to the App Store goes through Apple's App Review. We build the release schedule with this step in mind and prepare the information the review needs together with the submission.
Source: Google Play Console Help: testing requirements for new personal developer accounts
We stay with you after release
- Maintenance Bug fixes and small improvements, with the scope set in a written maintenance agreement
- Operating system updates Compatibility with new iOS and Android versions and with the stores' current technical requirements
- Version releases New features sent to both stores together in planned releases
- Monitoring Crash reports and usage data tracked so that problems are caught early
Six questions to ask when choosing a mobile app company
When comparing quotes, ask for written answers to these six questions as well as the price. You can ask us the same questions.
-
How is the source code handover written into the contract?
The source code, admin panel, server access and set-up documents to be handed over should be listed one by one in the contract. If the handover is not written down, continuing with another team later becomes difficult.
-
In whose name are the developer accounts opened?
If the App Store and Google Play accounts are opened in your company's name, the app and its user reviews stay with you. Taking over an app published from the developer's own account later needs a separate transfer process.
-
Are the admin panel and server included in the price?
The web panel and server side needed to manage products, orders and users do not show on screen, but in most projects they are a significant piece of work. If the quote lists only app screens, ask where these items and the server hosting fee sit.
-
Are the cost and scope of maintenance written separately?
New iOS and Android versions every year and the stores' technical requirements mean the app has to be updated regularly. Which of bug fixes, version compatibility and new features are covered by maintenance should be set out in a separate written agreement.
-
How is the ERP or payment connection built?
Confirm that the connection will be built through the routes the ERP vendor or payment provider supports (API, service layer or an approved import) and that nothing will be written directly into the ERP's database tables. If a connection is not possible or is risky, that should be said before the project starts.
-
Can they show a similar app working during the discovery call?
Seeing a working app rather than a presentation or screenshots is the most direct way to tell whether the company has done similar work before.
Our head office is in Şehitkamil, Gaziantep
We work remotely with businesses across Türkiye; you can reach us by phone, WhatsApp or email. If you are in Gaziantep, we can also meet at our office.
- Address
- Mücahitler Mah. 52078 Nolu Sok. No:2 Okan Towers Kat:13 Daire No:160, 27090 Şehitkamil/Gaziantep, Türkiye
- Office hours
- Weekdays 09:00–18:00, Türkiye time (UTC+3) · phone and WhatsApp every day
Questions people ask before having an app built
How much does it cost to have a mobile app built?
Quoting a single figure would be misleading; a simple app used only by customers and a system with customer, business and courier screens are not built on the same budget. Six items set the cost: user roles and flows, admin panel and server, integrations, working offline, design depth, and platform and technology choice. We give the firm price item by item and in writing after discovery. The first 30-minute call is free. What drives the cost
What are mobile app prices based on?
The price is set not by the number of screens but by needs such as user roles, the admin panel, integrations and working offline. So in the first call we listen to the scope and share the budget frame and timeline in writing; we give the firm price in writing once the scope is clear.
How long does it take to build a mobile app?
Depending on scope, it ranges from weeks to months. A simple app that does one job and a system with payment, couriers and an admin panel do not finish on the same schedule. Store review and, where needed, Google Play closed testing are added to the schedule; we give the firm plan in writing after discovery.
Are separate apps written for iOS and Android?
In most projects, no; we build for both platforms from a single codebase. A fix is then sent to both stores at once and maintenance stays in one project. Where the app has to work very close to the device hardware, we recommend native development and say so during discovery.
Should I choose Flutter, React Native or native?
For most business apps a cross-platform solution such as React Native or Flutter is enough. React Native stands out when you want to use the same language as the web side; Flutter stands out with heavily custom interfaces that look exactly the same on both platforms. We recommend native development with Swift or Kotlin when the app depends closely on device hardware.
Who owns the app's source code?
The source code we write and your data are handed over to you as defined in the contract; third-party and open-source components remain subject to their own licences. At the end of the project, the source code we write, the admin panel, server access and set-up documents are handed over as defined in the contract; if you want to continue with another team later, you are not dependent on us.
Who publishes the app on the App Store and Google Play?
We manage the store release; we recommend that the developer accounts are opened in your company's name (for sole traders the Apple account is opened as an individual). Store texts, images, privacy details and the review process are handled on our side. Owning the account means the app and its user reviews stay with you, with no transfer to deal with later.
Does Google Play's 12-tester requirement affect us?
Only if you will publish from a personal developer account; organisation (company) accounts are exempt. On personal accounts created after 13 November 2023, a closed test in which at least 12 testers take part continuously for at least 14 days is required before going to production. Because an organisation account requires a D‑U‑N‑S number, we start that application at the beginning of the project.
Can you turn our website into a mobile app?
Yes, we can carry your existing website or e-commerce platform into a mobile app. Rather than simply wrapping the site in a shell, we add features that bring value to an app, such as push notifications, quick sign-in and a saved basket. This difference matters because Apple's review guidelines expect an app to go beyond a repackaged website. Guide: PWA, WebView or a separate app
Do you build apps for warehouse and field teams in factories?
Yes. We develop iOS and Android apps for teams that count stock in the warehouse, walk the floor for quality checks, log machine maintenance or track deliveries. In production areas with weak connectivity the app works offline; the record waits on the device and syncs with the server when the connection returns. Barcode and QR reading with the camera, records with photos and the ERP connection are core parts of these apps. Industrial mobile apps
Will the app connect to our existing ERP or e-commerce site?
In most cases, yes; our aim is for the app to use the same data as your existing system. With ERPs such as Logo, Mikro or Netsis (widely used in Türkiye), or with your e-commerce platform, we first examine which route the connection will take. The connection is built through the routes the vendor supports (API, service layer or an approved import) and does not write directly into the ERP's database tables; your existing ERP is not removed and stays in place. If a connection is not possible or is risky, we say so clearly before the project starts.
Do you provide maintenance and updates after release?
Yes, after release we continue with maintenance, bug fixes and new version development. New iOS and Android versions every year and the stores' current technical requirements mean the app has to be updated regularly. We set the scope and cost of maintenance in a separate written agreement; because the source code is handed over to you as defined in the contract, you can also have this work done by another team.
Let's clarify your app idea in a short initial call
Write in two sentences who the app is for and what job it should do; we will work out the right scope and the first step together. We work remotely with businesses across Türkiye, and if you are in Gaziantep we can also meet face to face.
- We reply within one business day during office hours
- Source code handover is written into the contract
- There is no per-user licence fee for the app we write; third-party services excluded