Website or Mobile App? Deciding in the Right Order

Most businesses that ask me "website or mobile app?" want to know something else: how to reach their customers more easily. The two do that job in different ways. A website lets someone who doesn't know you yet search on Google and find you. A mobile app speeds things up for the customer who already knows you and keeps coming back.

So the first thing I look at is how often people will use it. Thinking about how many times a customer will open the same screen comes before any talk about budget or features. If a customer deals with you once or twice a year, persuading them to download an app is hard and expensive. If they order, book or check a status several times a week, the app earns its place on their phone.

1. 1How do most of your customers find you? Google search, word of mouth or social media?
2. 2How many times a month does the same customer do business with you?
3. 3Do you need to notify customers at the right moment? Order ready, appointment coming up, parcel on the way.
4. 4Is there work that has to happen without an internet connection? A field, a warehouse, a building site.
5. 5Do you need deep access to phone features such as the camera, location or Bluetooth?
6. 6Does your budget cover both the build and the maintenance in the first year?

If your answer to the first question is "Google", you need a website. If you give a strong yes to the second and third, an app comes into the picture. The fourth and fifth decide whether a PWA is enough. The sixth tells you whether you can do both at once.

For me, the most important row in the table is the steps to reach the user. Someone who lands on your website can call you within a minute. With an app, the same person has to download it, open it and often sign up first. If you don't give them a reason worth those steps, the app gets downloaded and then left unused.

A PWA (progressive web app) is a website that can be added to the phone's home screen and opens like an app. It isn't uploaded to a store, doesn't wait for review, and runs on every device from one codebase. If your budget is tight and your needs match the points below, a PWA can be a good middle step:

• Most of your users are on Android, or notifications are a secondary concern for you.
• The main job of the app is to show information, collect forms, or record orders and bookings.
• You don't need the phone's camera, Bluetooth or background location tracking.
• Being visible in the stores isn't essential for your marketing.

Where a PWA falls short is also clear: reliable notifications on iPhone, background location tracking, working offline for long stretches, and the trust that comes with a store listing. If these needs weigh more, building the iOS and Android app together with React Native is the better choice.

Below are four business types that are common in Adana, and in most Turkish cities. The scenarios are written around the general needs of each sector and don't describe a specific client. Every business is different, but they work as a starting point.

• Restaurant and café: a website covers the menu, location, opening hours and reservations, and gets you found on Google. Once frequent, repeated jobs such as takeaway orders and loyalty points grow, an app is worth considering.
• Clinic and private practice: patients search on Google first, so a website with service pages and an online booking form comes first. If there's a recurring process such as regular check-ups, test results or treatment follow-up, an app gains value.
• Real estate office: people looking for listings search mostly on the web. A website with search and filters is step one. An app makes sense when you want to send notifications for saved searches.
• Manufacturer and wholesaler: a website with a product catalogue to find new dealers and customers. If existing dealers order regularly, or a field team tracks stock or deliveries, a mobile app saves a lot of time.

In the Tüfekli Arıcılık project, a brochure site and a mobile app work together: the site introduces the business and its products to new visitors, and the app strengthens the relationship with existing customers. In the Wingardium agriculture app, real-time tracking in the field was the main need, so the mobile app sat at the centre of the work.

For some businesses the answer is "both". In that case, the biggest saving comes from the two products sharing the same backend and the same admin panel. The product list, user accounts, orders and bookings live in one place, and the website and the app become two shop windows for that data. Change a product's price in the panel and it updates in both.

Sharing is possible on the technical side too. When I use React and Next.js for the web and React Native for mobile, I can share parts such as data models, validation rules and the API layer between the two products. The same business rule isn't written twice, and a bug gets fixed once.

• What can be shared: backend, database, admin panel, authentication, business rules.
• What has to be built separately: screen design, mobile navigation, store publishing, push notification setup.
• Suggested schedule: instead of starting both at once, launch the website first and add the app on the same backend in a second phase. That splits both the budget and the risk.

1. 01

   Start with a website

   Get found on Google, explain your business and services, and start receiving enquiries or orders. This step needs a smaller budget, and it produces data that shows what your customers are looking for.

2. 02

   Watch the repeated tasks

   Which customers come back and how often, what they call you about, where time gets lost? The scope of the app comes out of these observations.

3. 03

   Test with a PWA if needed

   Making one part of the site installable on the home screen can be a low-cost way to test whether there's demand for an app.

4. 04

   Release the app as an MVP

   Start with the most used flow of the repeated task. Leave the other features for later versions, based on usage data.

If you're about to make this decision for a business in Adana, or anywhere in Türkiye, I can listen to how you work in a free discovery call and tell you plainly which one to start with. Sometimes the answer is "you don't need an app yet", and I say that too. Prices are starting ranges, and the final figure comes in writing based on the scope.