Custom web app vs website: when does your business need an app?

Custom web app vs website: what is the difference?

In the custom web app vs website choice, the line is simple. A website shows pages. A web app works something out for the person using it.

The same about page, the same product photos, the same contact form: that is a website, and every visitor sees it the same way. A web app keeps records for each user and applies rules to them. This buyer pays this price. This booking has two installments left. This assessor has five reports to mark.

So the question comes down to this. Are you publishing, or are you running part of the business through the browser?

When does a website stop being enough?

When the rules belong to your business and no plugin was written for them.

Here are three from our own custom web app development work, told the way our Work page tells them, without the client’s name:

• Event bookings paid in four installments. Clients enter the whole event themselves, from guest count and menus for adults and children to drinks, bar style and seating. Staff find any booking by name, contract number or date.
• A parts store with a price for each business buyer. Prices are set per customer organization, in Canadian and US dollars, with tax collected from Canadian-dollar clients only. Bulk orders arrive as quote requests that staff negotiate.
• A training platform for lift engineers. Learners file reports from jobs on site, quizzes mark themselves, assessors mark the longer tasks by hand and trainers answer questions in a live chat.

None of those is a page. Each one is a rule, and the rule decides what each person sees.

How far can WordPress and plugins go?

Further than people expect, and that is the honest place to start.

On 18 Oct 2026 we read WooCommerce’s own documentation against the training platform above. WooCommerce “adds two user roles, Customer and Shop Manager”. The platform needed four: learner, assessor, trainer and quality assurance, each with its own screens and its own view of the same records.

Payment plans and per-customer prices do exist for WooCommerce, as extensions. WooCommerce Deposits lets customers “pay for products using a deposit or a payment plan”. Dynamic Pricing covers wholesale and role-based prices.

So a store that needs one of those can stay a store. Add the extension, test it, done.

The trouble starts when a site needs three or four of them to cooperate. Each extension is another plugin to update, and each update can break the way it talks to the others. Our post on finding a WordPress plugin conflict shows what that looks like when it goes wrong on a live site.

What are the signs you need a custom web app?

Four tend to show up together:

1. More than two kinds of user. Customers and staff fit a store. Learners, assessors, trainers and auditors do not.
2. Prices or rules per customer. Not a coupon, but a price that depends on who is buying, in which currency, with which tax.
3. Staff screens that do real work. Finding a booking by contract number, approving a quote, marking a report. A plugin settings page is not that screen.
4. Data other systems need. Orders that have to reach the accounts system, or bookings that a mobile app reads too.

One of these on its own is often a plugin. Three of them is usually an app.

Turning rules like these into screens for each role, with a Laravel back end that keeps the records, is the work behind our web app projects.

Which stack do we build web apps in?

Laravel on the server, and React, Next.js, Vue or Nuxt for the screens people use.

Two of the web apps on our Work page, the event bookings and the training platform, have React screens over Laravel. On the Vue side we pick Nuxt over plain Vue when public pages have to arrive already built from the server, so search engines can read them. Screens behind a login usually need only Vue.

If you searched for React.js development services, that is the answer: React screens on a back end we also build, so the two are planned together.

When should you build a website instead?

When the job is mostly pages, forms and a standard store. A Squarespace, Wix or WordPress site does that well, costs less to build and costs less to keep running.

If a website will do, we say so. An app is worth its cost only when the rules it carries would otherwise live in spreadsheets, emails and somebody’s memory.

We have built websites and the software behind them since 2017, over 300 projects, and the two are not rivals. Many apps sit behind a website that stays exactly as it is.

Not sure whether you need an app?

Tell us what the app has to do: who uses it, and the three things each of them must be able to do on day one. We reply in writing with whether a website would do instead.

Want your current site looked at first? Send the address for the free site check, and a written reply comes within 2 business days.