// Yazılım Geliştirme — 2026-11-06 — 8 min

Web App or Mobile App? Which One Should a Small Business Build First

Web UygulamasıMobil UygulamaKüçük İşletmeYazılım Geliştirme

If your budget only covers one, which should you build first — and does the platform even matter? A practical breakdown by usage pattern and real cost.

Say you run a gym chain with three locations. Members want to book classes, reschedule personal training sessions, and check their payment history. Your budget this year covers exactly one build — a web app or a mobile app, not both. You search 'web app or mobile app for small business' and usually land on one of two answers: 'mobile is always better' or 'a web app is enough, mobile is an expensive vanity project.' Both are wrong, because the right answer isn't about an abstract 'better' — it depends on how your customer will actually use it.

##The Real Question Isn't 'Web or Mobile' — It's 'How Will Your Customer Use It?'

The thing you actually need to decide isn't the platform, it's the usage habit. A mobile app only earns its cost if the customer puts it on their home screen and opens it several times a week — think delivery apps, social media, banking. But if the customer visits you once or twice a month for a specific task — booking an appointment, checking an invoice, tracking an order — convincing them to download an app is already the biggest friction point in the whole flow. A meaningful share of users who reach the 'download' button on the App Store drop off right there; clicking a web link has no such barrier. On top of that there's update speed: fix a bug in a web app and everyone is instantly on the new version; on mobile, users stay on the old version until they approve an App Store update — some never update for months.

##Where a Web App Wins

A web app gives you faster, cheaper validation, especially early on. You write one codebase, it runs in the browser on desktop and phone alike, and you skip App Store or Play Store review entirely (usually 1–7 days, sometimes rejected and resubmitted). Being findable in search is its own advantage too — a mobile app doesn't show up in Google results, but a properly built web app can show up for searches like 'nearest appointment in my city.'

  • One codebase: no separate development and maintenance for iOS and Android
  • No App Store/Play Store review cycle; an update reaches every user within minutes
  • Discoverable in Google search — mobile apps don't get this
  • No download required, just a link click — the lowest possible friction
  • Development cost usually starts from a lower baseline than mobile

##Where a Mobile App Wins

Mobile earns its place where the job needs hardware or habit. Push notifications (appointment reminders, promotions, order status), reliable access to the camera, location, Bluetooth or NFC, and true offline mode — continuing to work from the last synced data without internet — are all limited or impossible on the web. A PWA (Progressive Web App) closes part of this gap, but it still lags behind a native app on things like reliable background push or full offline sync. And an icon on the home screen means the customer sees you every day — that's a behavioral advantage, not just a technical one.

  • Push notifications reach the customer directly (reminders, promotions, status updates)
  • Reliable access to camera, location, Bluetooth, and NFC
  • Full offline mode with background sync
  • A home-screen icon builds a daily or weekly habit
  • Being on the App Store/Play Store signals trust in some industries (finance, healthcare)

##It's Not Really 'Either/Or' — It's 'Which One First'

Most growing businesses end up with both eventually, so the real question isn't 'which one is permanently enough' — it's 'which one do I build first so the second one costs less.' The practical answer lives in the architecture: if you build the backend — database, API, payments, business logic — API-first from day one, meaning both the web interface and the mobile interface you'll eventually build consume the same API, most of that backend carries over when you move to mobile. The only real extra cost is the native UI layer and the notification infrastructure; you don't write the database and business logic twice. That's how you answer 'which one first' without turning it into a real sunk-cost risk.

##A Real Scenario: A Three-Location Gym Chain

Back to the gym example. The owner has a budget of roughly 150,000 TL and needs to decide within six months. The first question: how often will members open this app per day? The real answer is 'two or three times a week' — to book a class, cancel one, or check the PT schedule. That's not frequent enough to force a mobile app, but not rare enough to make a web app insufficient either. So they build a web app first — really a PWA, one that can be added to the home screen and send notifications — covering booking, payment, and the PT calendar, live within six weeks. In the first three months: over 400 active users and a visible drop in booking no-shows. Nine months in, with real usage data — how many users, which feature gets used most, which hours see the most traffic — they decide to build the native mobile app, because the data now shows that push-notification class reminders would cut no-shows even further. Because the mobile app reuses most of the web app's backend, the extra cost isn't the full budget a mobile build from scratch would have taken — just the native UI and notification layer on top.

##Cost and Timeline Comparison

The numbers vary by project, but looking at freelancer and small-agency rates in Turkey, you're roughly in these ranges. Building both platforms (iOS + Android) at once takes almost twice as long as a single platform — because even with a single cross-platform layer (React Native/Flutter), you still need platform-specific testing and store submission processes.

Simple web app (MVP)

80,000–250,000 TL, 4–8 weeks

Mobile app (single platform)

150,000–400,000 TL, 8–14 weeks

Mobile app (iOS + Android)

250,000–600,000+ TL, 12–20 weeks

Annual maintenance (mobile, incl. OS updates)

roughly 15–25% of total budget

Maintenance differs too: a web app's upkeep lives in one codebase, while mobile needs new testing — and sometimes small code changes — every year when Apple and Google ship OS updates. That's why mobile's annual maintenance budget usually runs higher than web's. Then there are store commissions: if you take payment inside the app, Apple and Google typically cut a share of the sale as commission — an easy cost to overlook depending on your business model. If bookings or service fees are collected through an outside payment flow, this commission doesn't apply, but if there's in-app digital sales, it needs to be in the budget from the start.

##Which One, When? A Decision Checklist

  • Customer opens it more than a few times a week (delivery, chat, daily tracking) → lean mobile
  • Customer comes for a specific task once or twice a month (booking, invoices, order status) → web/PWA is enough, often better
  • Being found on Google matters a lot to your business (local search, SEO) → start with web
  • Hardware features — camera, location, offline sync — are central to the job → mobile, or at least test the limits of a PWA first
  • Budget covers only one and you want fast validation → start with web/PWA, move to mobile with real data
  • Trust signaling matters a lot in your industry (finance, healthcare, where being on the App Store means credibility) → prioritize mobile earlier

##FAQ

>Can a PWA (Progressive Web App) actually replace a mobile app?

Partially. A PWA is a technique that makes a web app installable on the home screen, able to work offline, and able to send notifications. On iOS, Apple's restrictions keep push notifications and offline support more limited than on Android — which means a PWA isn't a full mobile-app substitute for a business whose users are mostly on iPhones. But for Android-heavy or platform-agnostic, simple use cases, a PWA can deliver a very similar experience for a fraction of a native app's budget.

>Does building web first and mobile later mean extra cost?

Yes, but less than it looks. The backend — database, API, payment integration, business logic — is largely reusable; the real extra cost is the native UI layer and the store submission process. In total it won't come out cheaper than building both from scratch together, but it cuts the risk substantially: you never rebuild a feature nobody used on mobile, and you move to mobile with real usage data instead of a guess.

>Is being on the App Store and Play Store actually an advantage for a small business?

Yes, but it depends on the industry. In 'trust-sensitive' sectors like finance, healthcare, or subscriptions, being in the store is a credibility signal — reviews, official store approval. For a barbershop booking app, that signal matters much less; the real value there is sending a reminder notification. So what matters isn't the store itself, but which of the two things it provides — the trust signal or the notification infrastructure — is more critical to your business.

>Does it make sense to start with just one platform — only iOS or only Android?

If budget is tight, yes — but choose based on where your actual target audience concentrates, not an assumption. Android has the larger overall user base in Turkey, but your specific customer profile (age, income, industry) can flip that; customers of a premium or enterprise service often skew more toward iPhone. Looking at your existing web traffic's device stats is a far more reliable starting point than guessing. The hidden risk of starting with one platform is that you shut the other platform's users out entirely, so 'how many users am I giving up for now' belongs in the budget decision too.

Whichever side you land on, keeping the first step small and measurable pays off — real usage data draws a far more reliable roadmap than a guess ever will. If you want the realistic timeline for a web app build, there's a related post worth a look; if you'd rather talk through the scope of your own project, reaching out directly works too.

// LET'S WORK

Planning a similar SaaS product?

We can define scope, MVP milestones, and a realistic delivery timeline together.

> CONTACT