Service
Mobile app development
Not every need requires a store app. First we settle one question: do you actually need an app, or is an installable web app (PWA) enough?
First decision: native app or PWA?
This single decision can double or halve the budget.
| Criterion | Store app | PWA (web app) |
|---|---|---|
| Installation | App Store / Google Play | Browser → “add to home screen” |
| Development cost | High | Low–medium |
| Updates | Store review required | Instant, from the server |
| Notifications | Full support | Supported (limits on iOS) |
| Camera, location, files | Full access | Most capabilities available |
| Offline use | Yes | Yes |
| Best for | Consumer-facing, frequently used apps | Field teams, dealers, internal use, fast launch |
For most internal corporate scenarios a PWA is sufficient and ships far sooner.
The kinds of apps we build
Field team apps
Location-verified check-in, task tracking, photo reporting and offline operation.
Customer apps
Ordering, appointments, loyalty and notifications, integrated with your existing systems.
Dealer and B2B
Account balances, order entry, price lists and document sharing.
Internal operations
Warehouse counting, barcode scanning, production tracking and approval flows.
Mobile front for existing systems
If you already run web software, adding a mobile face to it is usually the cheapest route.
Store publishing
Developer accounts, privacy policy, store assets and managing the review process.
Decide these before development starts
- Whose phone will run it? Company device or the employee’s own? This determines consent and data protection requirements.
- What happens without connectivity? If coverage is poor on site, offline operation must be designed in from the start.
- Are notifications really needed? Unnecessary notifications are the reason apps get deleted.
- How long will location be tracked? Continuous background location drains battery and creates legal exposure; verification at check-in is usually enough.
- Whose developer accounts? Apple and Google accounts must be in your company’s name — an app living in an agency account is not yours.
Market
Mobile app prices — 2026 ranges
The biggest saving is the technology decision: if a PWA can do the job, cost can drop to a third.
| Approach | Common range | Notes |
|---|---|---|
| PWA (no app store) | ₺20,000 – 80,000 | Usually enough for field teams and internal use |
| Cross-platform (one codebase) | ₺40,000 – 250,000 | Most common choice; markedly cheaper |
| Native iOS + Android separately | ₺100,000 – 400,000 | Unnecessary without hardware-specific needs |
| Enterprise / complex app | ₺200,000 and above | Payments, live location, multi-role panels, integrations |
| Annual maintenance | 20–25% of budget | Unavoidable due to store version requirements |
Source: agency price pages published in Türkiye, August 2026. These are not our prices — they are market ranges and do not constitute a quotation. Published Turkish agency prices usually exclude VAT; ask when comparing quotes. Development typically takes 8–20 weeks. Apple Developer (annual) and Google Play (one-off) fees are paid to the platforms and budgeted separately.
Publishing
App store publishing, step by step
Finishing the app is not the end. Store processes are where projects get the most surprises.
Developer accounts
Apple Developer and Google Play accounts are opened in your company’s name. Apple may require company verification (D-U-N-S number), which takes days.
Store listing
App name, description, keywords, screenshots and feature graphic. This copy determines in-store search ranking (ASO).
Privacy declaration
You declare what data is collected. A wrong declaration is grounds for removal; it must match what the app actually does.
Review
Apple review can take days and may be rejected. Most common reasons: incomplete privacy declaration, no test account provided, and being judged “just a website wrapper”.
Release and updates
After launch, version management begins. Expedited review can be requested for critical fixes.
Decisions
Seven decisions that set a mobile budget
These seven items are why the same idea is quoted anywhere between ₺40,000 and ₺400,000.
- Store app or PWA? The single decision that can cut cost to a third.
- Login and number of roles. One user type versus three is a substantial difference.
- Are there payments? In-app payment means development work plus store commission.
- Offline operation. If coverage is poor, design it in from the start; retrofitting means rewriting.
- Live location. Continuous tracking costs battery and legal exposure; check-in verification is usually enough.
- Admin panel. Who manages the app’s data? The panel is often as much work as the app.
- Number of integrations. Every external system is separate development and separate testing.
Frequently asked
Do you write separate iOS and Android apps?
Usually not. We use technologies that ship to both platforms from one codebase, which reduces cost noticeably. Separate development only comes up for graphics-heavy or hardware-specific requirements.
Do you publish the app to the stores?
We run the publishing process, but the Apple and Google developer accounts are opened in your company’s name. You own the app. Apps published under an agency account cause serious problems when you change agency.
Are developer accounts paid?
Yes. Apple Developer Program is annual, Google Play Console is a one-off fee. These are paid to the platforms, not to us, and are budgeted separately.
Do you build attendance apps?
We already have a product for that: our workforce management system runs on web and mobile with location-verified check-in. Starting there is faster and cheaper than building from scratch.
Does a published app need maintenance?
Yes. iOS and Android release new versions every year and the stores periodically require an up-to-date build. Unmaintained apps can be removed from the stores within a year or two — plan for this.
How much does a mobile app cost?
In the market, PWAs start around ₺20,000, cross-platform around ₺40,000 and native around ₺100,000 (table above). The items that inflate budgets most: payment infrastructure, live location tracking, multi-role permissions, a custom admin panel and third-party integrations. Keeping the first release narrow can halve the cost.
How long does it take?
Typically 8–20 weeks. Duration is driven less by screen count than by integration count; every external system needs its own testing time. Store review (particularly Apple) adds days to weeks.
Is annual maintenance really necessary?
Yes. iOS and Android ship yearly releases and the stores periodically require an updated build; an unmaintained app can be removed within a year or two. The market plans annual maintenance at 20–25% of the project budget.
Is a PWA really enough?
For most field, dealer, warehouse and internal scenarios, yes — and it ships far sooner, needs no store approval and updates instantly. For consumer apps used several times a day with heavy notification needs, a store app is the right answer. We tell you which side you are on in the first call.
Next
Pages people read alongside this one
Let’s scope your mobile need
Describe the scenario and we’ll tell you in the first call whether it needs an app or a PWA, and roughly what it involves.