Skip to main content

Service specification 4 sections Part of bespoke software

Web Development

01

Website or web application?

The word app causes most of the confusion. Start with the job, then choose the right type of build.

Bespoke web application development builds a system for one business. It does not force the work into a fixed product. A website tells people about you. A web application does a job. It can take bookings, hold accounts, run quotes or handle orders. It runs in a browser, so nobody has to install it.

You want a website

People need to understand, trust and contact you.

  • Service pages and case studies
  • News, guides and company information
  • Enquiry forms and contact details
  • Content your team can edit

Verdict: choose web design when the main job is to explain and sell.

You want a web application

People need to log in and complete a task.

  • Accounts, bookings and order histories
  • Quotes, calculators and forms with rules
  • Dashboards built from live business data
  • Work shared between customers and staff

Verdict: choose bespoke application development when the browser needs to do real work.

Developer and business owner reviewing a website across desktop and mobile
Review the real journey

We test the page, the phone view and the work behind every button.

02

Web applications we build

A bespoke web application starts with a task. These are six common jobs that belong in a browser.

A booking application we built

Cornish Wave takes bookings for surf lessons and other outdoor activities through one system. It also handles group bookings and collects participation forms up front. A visitor has a task to complete, not just a page to read. The booking and the forms are parts of that task.

If your project links forms to bookings, decide who can read them. Test access with more than one account. These are useful checks when scoping your own booking system. See Cornish Wave in our software portfolio.

We use PHP and Laravel on the server. MySQL or PostgreSQL stores the data. JavaScript with Vue or React runs in the browser. If customer records are the main job, a bespoke CRM system may fit better. That page covers software shaped around customer data and staff work.

Benefits and limits of web applications

A web application asks nobody to install anything. That convenience has a price, and it is worth naming.

General to this kind of project rather than to any one product. No prices, because none are ours to publish.
What to weigh What the browser gives you What it costs you
Getting it to people Users open a link rather than downloading an app from a store. Agree which browsers and devices you need to support, then test them.
Making changes You publish once and everyone has it immediately. Everyone also has your mistakes immediately, so releases need care.
Working offline Modern browsers can hold data and keep going for a while without signal. Offline work needs its own scope, including what happens when the connection returns.
The device The same screens work on a laptop, a tablet and a phone. Camera, location and notification support varies by browser and device.
Who can use it Anything with a browser can reach it, including machines you do not control. The server must check who can read or change each record.
The long run No app store sits between you and your own users. Browsers change on their own schedule and occasionally break things.
03

Web application access, delivery and support

A web application opens from a link. Staff and customers can use it on a phone without visiting an app store. Their account follows them between devices.

Updates happen in one place. The next time someone opens the application, they use the current version. Nobody has to download a new release.

This is what many businesses mean when they ask for a bespoke app. They need an application that works well on a phone. They do not need a native mobile app.

Some projects need an app on the phone, not a site in the browser. The choice depends on camera access, offline use or push notifications. Our mobile app development page explains when a phone app fits better.

Before launch, check keyboard use, zoom and mobile reflow. Our website accessibility checklist sets out the main tests.

One place to log in

The same web address, account and data work across each device. That keeps support simple and the record in one place.

From a user task to a tested release

  1. 03.1

    Define the browser journey

    Show us how a customer or staff member completes the task now. We map the screens, the records they need and what each role can change. Include failed steps, such as a form sent twice or a lost connection.

  2. 03.2

    Review the screens early

    We agree screen layouts before the full build. Review a phone form as well as the desk view. Check field names, error messages and the steps needed to finish. A screen review can expose a missing rule before it becomes code.

  3. 03.3

    Test the task and its limits

    Agree the expected result for each key task. Test it with safe sample records and the user roles in scope. A customer must not see another account by changing a link. Check the server refuses that request, not just that the screen hides it.

  4. 03.4

    Check the release and support plan

    Test the agreed browsers, connected records and key forms before release. Decide who approves launch and how to return to the last working version. Agree who checks the live release and who handles faults after it.

Use our software specification guide to write down the tasks and rules. Our user acceptance testing guide explains how staff can check the build against them. These checks sit alongside security and performance tests.

Where it runs, and who can see the data

A web application needs hosting. We can host it or review hosting you already use. Agree who holds the account, who can deploy code and who checks backups. Hosting access and code ownership are separate parts of the agreement.

If it holds personal data, the scope has to say what is stored, who can see it and how long it is kept. Agree account roles, checks on each record and which changes need a log. Set out how to close an account too. Your own lawful basis, privacy notice and retention policy stay with you.

What happens after launch

You own a new codebase built for you, along with its documentation. If the build uses our Zeus Laravel CMS, Dev Moves owns Zeus and licenses it to you. The project-specific frontend is packaged separately and belongs to you. Your data is yours throughout.

After launch we can provide web application support, fix faults and add to it. Handover does not create an unlimited support promise, so what is covered is set out in the agreement. We also choose tools another developer can support, so you are not tied to us to keep it running.

04

Common questions

What is bespoke web development?
Bespoke web development creates a web application for one business. It follows that business's own process instead of a product template. The result may handle bookings, customer accounts, quotes, orders or internal work through a web browser. It can read data from other systems and write approved changes back. Staff and customers use the same current version from a link. A bespoke build makes sense when a standard product cannot support a task that matters to the business.
What is the difference between a website and a web application?
A website explains what a business does and helps people get in touch. A web application lets someone complete a task. They might log in, book a service, run a quote or manage an order. Both use a browser, but their jobs are different. A website is often led by pages and content. A web application is led by data, rules and user accounts. One project can include both, but the scope should state which job each part must do.
Do you build mobile apps?
Yes, by all three routes. We build web apps that run in a phone browser with no download. We build cross-platform apps in React Native or Flutter, where one codebase serves iPhone and Android. We also build native apps in Swift or Kotlin. The task decides, not the device. A browser build is simpler to maintain when it can do the job. Offline working, deep camera or sensor access and push notifications are the usual reasons to go native. Our mobile app development page covers how we pick.
Can a web application work on a phone?
Yes. A responsive web application adapts its screens to a phone, tablet or computer. The same account and data work on each device. Users open a link and sign in, so there is nothing to install or update. Buttons, forms and tables still need to be planned for a small screen. We test touch targets, zoom and keyboard use before launch. Work that must continue with no signal may need a mobile app or a planned offline mode instead.
Do you build SaaS products?
Yes. We build and run QR Code Redirector, our own subscription product. A business can change where a printed QR code points without printing it again. The build includes self-serve accounts, scan tracking and subscription billing. For a new SaaS product, the scope needs to cover account access, billing rules and what happens when a subscription ends.
Who owns the code?
It depends on the build. A wholly new codebase belongs to the client. Dev Moves owns the Zeus Laravel CMS and licenses it to the client. The project-specific frontend is packaged separately and belongs to the client. Reusing Zeus lowers the build cost because the core platform already exists. The scope and handover state what belongs to you and what is licensed. Your data remains yours, and you can ask for it in a usable format.

Every question we get asked, in one place

Next step

Discuss your web development project

Tell us what a customer or member of staff needs to complete. We will tell you whether that needs a website, a web application or an existing product.

  • Pontefract, West Yorkshire
  • Building for businesses across the UK
  • Reply within 1 working day
Five clear questions

Outline your software or website project

No finished spec needed. Tell us what is getting in the way.

Question 1 of 5
What are we building?

Choose the closest fit. It does not lock you into anything.

What needs to work better?

Describe what happens now and what you want to change.

One or two clear sentences are enough.
Who will use it?

A rough answer helps us judge access, training and support.

What must it connect to?

Name any software, website, payment service or database that needs to stay.

Leave this blank if there are none or you are unsure.
Where should we reply?

A developer will read the brief and reply within one working day.

We use these details to reply to your enquiry. Read our privacy policy.