group
“We need an app.” We hear it regularly at the start of a project, sometimes rightly, more often out of reflex. At the other end, some businesses wear themselves out processing by hand orders that an online store would handle on its own.
The right format follows from three things: what your customers need to be able to do, what your team can manage day to day, and how your business is going to grow. Technology comes afterwards. Here’s how to think it through.
Start from what your visitors mainly need to do
One simple question guides the choice: when someone lands on your site, what do they need to do? Understand your offer and get in touch, buy without talking to you, or use a service again and again, with an account and their own data?
Many projects combine two answers. That’s fine, as long as you know which one comes first: it shapes the site, the budget and the timeline.
- Understand, feel reassured, get in touch or book: business website
- Choose, pay, get it delivered: e-commerce site
- Log in, manage, track, come back often: app or PWA
The business website: present, reassure, get the call
A business website suits most service companies, tradespeople, independent professionals and businesses that sell to other businesses. Its job is to answer the questions a prospect asks before calling you: what exactly do you do, for whom, how, with what track record, and how can they reach you?
It can go further than a simple presentation. A booking module, a detailed quote form or a download area all fit in without turning it into an e-commerce project. We design these sites, online booking included, as part of our website design service.
E-commerce: when selling online is the heart of the project
An online store makes sense when your customers need to choose, pay and receive without you stepping in. For a small or mid-sized store, Shopify is a solid choice: payments, stock, shipping and taxes are built in, and its app store covers most everyday needs.
Yet the site is only the visible part. A store that works needs complete product pages, consistent photos, solid terms and conditions of sale, a process for preparing orders and someone to answer customers. That work, more than the technology, is what separates a store that sells from a store that waits.
- How many products and variants, and how often do they change?
- Who prepares the orders, and how quickly?
- How do you handle returns and the customer’s right to cancel?
- Do you also sell in a shop or on marketplaces?
App or PWA: for repeat use
An app makes sense when your users come back often, log in to an account and take actions: book, track an order, manage documents, run an activity. A customer portal, an advanced booking tool or internal management software all fall into this category.
Before thinking about app stores, consider a PWA, or progressive web app. It opens in the browser, installs on the phone’s home screen, works partly offline and can send notifications. A single codebase serves every device, with no app store review to go through. For a first version, it’s usually the right choice.
A native app is still the right call when you need deep access to the phone’s features, high performance or a presence on the App Store and Google Play. In return, it takes more development and maintenance. It’s a trade-off we weigh case by case in app development.
The questions that tip the balance
Once the main action is clear, a few practical questions sharpen the choice. Above all, they stop you underestimating what happens after launch.
- Who will update the content, products or data, and with what tool?
- Do your users need a personal account?
- Does the service need to work in the field, offline?
- Which tools need connecting: calendar, till, accounting, CRM?
- What annual maintenance budget can you take on?
- How is your business set to grow over the next few years?
The most common wrong choices
Bad choices rarely come down to technology. They come from a poorly defined need, or from ambition running ahead of actual use.
- Commissioning a native app when a well-designed website would do
- Opening a store without sorting out logistics and customer service
- Choosing a technology before describing how it will be used
- Forgetting the admin interface, the one your team will use every day
- Building everything at once instead of launching a useful first version
Start small, on solid foundations
The wisest route is to launch a first version focused on the main action, then add features as real usage becomes clearer. A business website can take on online booking, then a small store. A PWA can come before a native app if usage justifies it.
That progression depends on sound foundations: a tool you control, a platform or codebase that can evolve, data that belongs to you and that you can export. Be demanding on these points from day one, even for a small project.
- The format follows from your visitors’ main action: get in touch, buy or use.
- A business website covers most presentation needs, online booking included.
- A Shopify store makes sense when the catalogue, logistics and customer service are ready.
- A PWA makes a good first version of an app, before going native.
- Start with the essentials, on foundations that let you grow.
Frequently asked questions
What’s the difference between a PWA and a regular mobile app?
A PWA is a web app: it runs in the browser, installs on the home screen and can partly work offline. A native app is downloaded from the App Store or Google Play and has freer access to the phone’s features. The first is simpler to build and maintain, the second more powerful for demanding uses.
Is Shopify right for a small store?
Yes, it’s one of its strengths. The platform handles payments, stock and shipping with no development, and your team can add products on its own. Do factor the subscription and paid apps into your running costs, though.
Can a business website be turned into an online store later?
It can, but rarely by just adding a plugin. If selling online is part of your plans, choose a platform that allows it from the start, or plan a clean migration when the time comes. Your initial choice should take that growth into account.
Tell us what your customers need to be able to do. We’ll recommend the right format, and what can wait for a second version.
