App or website: does your idea need an iPhone app? (2026)

By Sigsten Gustavii· 25 September 2026· Updated 27 October 2026· 8 min read

"Should this be an app?" is one of the most common questions behind an idea, and "it depends" is no help. It does depend, but on a short list of things you can check in ten minutes. This guide walks through them, with a decision table, what each route costs, and how people find each one.

The quick decision table

Go down the list and count which column your idea lands in more often.

If most of your answers land in the App column, read on for what an app takes. If they land in the Website column, a good mobile website may be all you need, and you can add an app later for the people who use it most.

Five questions to ask about your idea

1. How often will one person use it? Daily or weekly use is where an app earns its place on the Home Screen. A once-a-year task is a website.
2. Where will they be? A gym basement, a train, a festival field, a shop floor: anywhere the signal is weak, an app that keeps its data on the phone just works.
3. Does it need the phone itself? The camera, Face ID, the Calendar, Apple Maps, the motion sensor and haptics are where apps clearly beat the browser.
4. How will people find it? If they will search Google for it, you need a website. If they will search the App Store, or you hand it to a known group, an app works.
5. How will it make money? Digital extras inside an iPhone app usually go through Apple's in-app purchase. Physical goods and services, and anything on a website, use your own payment provider.

What an app does that a website can't do as well

Websites have come a long way on the iPhone, and our PWA vs native post covers what Safari allows today. Still, a native app reaches parts of the phone directly, through Apple's own frameworks:

• Working offline. A native app saves its data on the phone, so it opens instantly and works in airplane mode. See offline data.
• The camera and scanner. Apple's VisionKit reads text and codes live through the camera. See camera and scanning.
• Face ID. A journal or budget that stays hidden until the phone sees you. See Face ID.
• Reminders on time. The iPhone schedules them itself, so they arrive on the lock screen even with the app closed. See reminders.
• The Calendar and Apple Maps. Add an appointment to the phone's calendar in one tap, or open directions. See calendar and maps.
• A place on the Home Screen. Being one tap away is what keeps a daily habit going.

What a website does better

• Being found. Search engines index every page, and anyone can share a link that opens instantly.
• No install. A visitor can read, book or buy in seconds without a download or an Apple ID.
• Every device. The same address works on iPhone, Android, Windows and Mac.
• Instant changes. No review: you save, and everyone sees the new version.
• Long reading and big forms, which are easier on a computer screen.

What each one costs

The gap has narrowed a lot. Hiring a developer for a native app used to cost far more than a website; with an AI app builder, the app side is a monthly plan plus Apple's yearly fee. Our post on what it costs to make an iPhone app breaks it down further.

How people find a website, and how they find an app

Discovery is the part people forget. A website is found through search engines, links and social posts, and a visitor can use it the moment they land. An app is found through App Store search, its product page, ratings and links from your other channels, and the visitor has to install it before trying it.

That is why apps suit people who already know they want you: members of a club, regulars at a café, a team at work, or anyone who searched the App Store for exactly what you made. Our guide to App Store optimization covers how to be found there.

Why many ideas end up with both

For a lot of businesses, clubs and creators, the answer isn't one or the other. The website does the finding: it ranks in search, explains what you offer and links to the app. The app does the keeping: the loyalty card, the booking, the daily log that lives on the phone of people who come back. A café might have a website for opening hours and a loyalty card app for regulars; a salon might have both a site and a booking app.

If you already have a website, an app should do more than repeat it. Apple's guideline 4.2 asks apps for "features, content, and UI that elevate it beyond a repackaged website", so a wrapper around your site often gets sent back. Build the app around what the phone does well. Our page on turning a website into an iPhone app shows how.

Signs you don't need an app (yet)

• People would use it a few times a year at most.
• Everything it does is reading pages and filling in a form.
• Your audience is mostly on desktop computers.
• You haven't yet found the people who want it; a website or a simple landing page is a cheaper way to test interest. Our guide to validating an app idea helps here.

How to make the app side with Borel

If the table pointed to an app, Borel makes a native iPhone app from a plain description, written in Swift with SwiftUI and built on Borel's own Mac, so you need neither a Mac nor code. It is a real app, not a website in a box, which is what Apple's reviewers look for.

1. Sign up free at borel.one; the free plan gives you 5 credits a day.
2. Describe the app, or paste your website's address and ask for an iPhone app on its brand.
3. Try it on a live iPhone in the iOS Simulator in your browser, free for everyone.
4. Add the phone's features by asking: offline data, the camera, Face ID, reminders, Apple Maps, the Calendar or in-app purchases.
5. Install and publish with Pro, from $20 a month: Borel Companion puts it on your iPhone, and Publish uploads it to the App Store under your own Apple Developer account.

Make an iPhone app for regulars at my café, Bean There. A stamp card that fills up with each coffee and gives the tenth one free, scanned by staff at the till. Show our opening hours and directions in Apple Maps. Use our colours: dark green and cream.

Borel also writes and hosts the privacy policy and support pages Apple asks every app for, so you can publish without a website of your own.

The bottom line

Choose an app when people will use your idea often, on the phone, and it needs the phone's own abilities: offline data, the camera, Face ID, reminders or in-app purchase. Choose a website when people visit rarely, find you through search, or use a computer as much as a phone. When it is both, start with whichever reaches your people sooner, and add the other. To try the app side today, describe your idea on Borel and see it running on a live iPhone in minutes.

I would rather you build the right thing than an app for its own sake. If the table points to an app, describe it to Borel and see it on a live iPhone today.

– Sigsten

Make your iPhone app in Borel

Describe the app you want and see its first screens before you pay anything.