In short
  • Decide per audience, not per organization. The answer for customers may differ from the answer for staff.
  • An app earns its place with frequent use, a reason to sign in, the phone's own abilities, alerts people want, or work away from signal.
  • A better website wins for occasional visitors, people finding you for the first time, and anything done once or twice a year.
  • Websites can now do more than many people think, including Apple Pay and passkeys.
  • Many organizations need both, built on the same data.

Start with how often

The single best predictor of whether an app will be used is how often someone needs it. A dispatcher, a dealer or a patient in a six-week recovery program opens something daily or weekly. A policyholder renewing once a year, or a prospect comparing firms, does not.

People keep a small number of apps they actually open. Anything used a few times a year has to compete with that, and it usually loses. They search, land on your website and get on with it. For them, the quality of the website is the whole experience.

So the first question isn't "app or website?" It's "who are the people we serve or rely on, and how often do they need us?"

Five signs an app earns its place

They come back often. Daily or weekly use is the clearest sign. Staff, partners, dealers and members in an active program usually qualify. One-off buyers usually don't.

There's a reason to sign in. When the value is their own claim, orders, schedule or matter, staying signed in with Face ID beats hunting for a password every visit.

The phone itself does the work. Scanning a document, photographing damage, reading a barcode or capturing a signature on site is natural in an app and clumsy in a browser.

They want to hear from you. When the news is genuinely theirs, like a shipment arriving, an approval waiting or an appointment moving, an alert on the Lock Screen is the most useful thing you can send. Email is easy to miss.

Signal is unreliable. Basements, plants, job sites, rural routes and hospital corridors. An app can keep working and catch up later. A website that loses its connection mid-form loses the work.

One strong sign can be enough. A field inspection app is justified by working offline alone. Several weak signs usually aren't.

When a better website is the right call

Be honest about these, because an app built for the wrong audience is expensive to keep alive and quietly ignored.

  • People finding you for the first time. Nobody downloads an app to evaluate a firm. Search, referrals and links all lead to a website.
  • Tasks done once or twice a year. Renewals, annual forms and one-off requests belong in a portal that works well on a phone.
  • Audiences on every kind of device. If half your customers use Android or a work laptop, a good website reaches all of them at once.
  • Long reading or complex comparison. Contracts, reports and detailed pricing tables are easier on a larger screen, and people often do them at a desk.
  • Staff who live at a desk. A team that works in a browser all day may need a better internal tool, not a phone app.

A website that is hard to use on a phone won't be rescued by an app. If people struggle with the site, fix that first. It is still where most of them will meet you.

What websites can do now

Some reasons organizations used to give for building an app no longer hold. Apple Pay works on websites in Safari. Passkeys, which sign people in with Face ID and can't be phished, work for websites as well as apps. Since iOS 16.4, a web app saved to the Home Screen can even send notifications.

The catch is in that last sentence. Notifications from a web app only work once someone has added it to their Home Screen, which most people never do. So the web closes some gaps on paper more than in practice. Where an app still clearly leads is the combination: camera scanning, reliable alerts, Wallet passes, widgets, working offline and staying signed in, all in one place people already open. Our guide to what an iPhone app could do for your organization walks through those with examples.

Many organizations need both

The most common honest answer is "both, for different people." A logistics company might keep a mobile-friendly portal for occasional shippers and build an app for its drivers and its ten largest customers. A healthcare group might keep online scheduling for everyone and offer an app to patients in longer programs. A manufacturer might put product information on its website and give dealers an app for quoting and reordering.

SituationUsually lean toward
Prospects and first-time visitorsWebsite
Customers who check in a few times a yearMobile-friendly portal
Customers, members or patients who engage weeklyApp, with the portal as a backup
Partners, brokers and dealers who order or quote oftenApp, often released privately
Staff on the road, on site or on the floorApp
Staff at a desk all dayWeb-based internal tool
Leaders who want a few numbers and approvalsApp or Home Screen widget, backed by fuller reports on the web

When you build both, they should share one source of truth. A status that reads differently in the app and on the portal damages trust in both.

An app is a commitment, not a launch

A website can sit quietly for a while and still work. An app can't. Apple releases a new version of iOS every year, people expect the app to keep pace, and anything it shows has to stay accurate every day it's installed.

That isn't a reason to avoid one. It's a reason to be sure the audience is worth it. Before deciding, it helps to answer three questions honestly:

  • Who would open this every week, and what would they do in it?
  • What would they stop doing, like calling, emailing or retyping, once they had it?
  • Who on our side will own it a year after launch?

If those answers come easily, an app is probably worth a serious look. If they don't, a better website or portal is the safer first step, and it leaves the door open.

What most guides miss

The answer changes by audience. Most debates stall because people argue about "the organization" when the honest answer is yes for one group and no for another. List your audiences and decide each one.

A wrapped website is the worst of both. Putting your site inside an app frame keeps the website's weaknesses and adds a download. Apple's review rules also ask that apps go beyond a repackaged website.

Private apps change the math. Apple lets organizations release custom apps only to the people they choose, such as staff, clients, partners or dealers. An app for two hundred dealers can be worth more than one for twenty thousand casual customers.

Screens are the small part. Whether you choose an app, a portal or both, most of the value comes from what sits behind it: up-to-date orders, claims, schedules and documents from your own systems. Get that right and either option can be good.

How we do it

We look at who you serve and depend on, and tell you plainly where an app would earn its place and where a better website or portal would do. When an app makes sense, we build it and connect it to the systems you already run, and the code and accounts are yours. We stay on to support and extend it, and the first call is free.

Sources

  1. Apple Developer: Apple Pay (in apps and on the web in Safari)
  2. Apple Developer: Passkeys
  3. WebKit: Web Push for Web Apps on iOS and iPadOS
  4. Apple Developer: Wallet Passes
  5. Apple Developer: WidgetKit
  6. Apple Developer: Custom apps for organizations
  7. Apple: App Review Guidelines (4.2 Minimum functionality)