Service specification 4 sections Part of bespoke software
Web Development
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.
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.
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.
We test the page, the phone view and the work behind every button.
Web applications we build
A bespoke web application starts with a task. These are six common jobs that belong in a browser.
-
01
Customer logins and accounts
Customers sign in to see their profile, orders and information in one place.
-
02
Booking and scheduling
People choose a service, date and group, then send the details you need.
Built for Cornish Wave - online booking, group bookings and participation forms -
03
Quoting and calculators
Rules turn the answers on a form into a clear quote or next step.
-
04
Dashboards and reporting
Live records become a useful view instead of a report built by hand.
-
05
Document handling
The right user can find, read and download the right file.
Built for Adviser Hub - gated content and media library -
06
Integrations with what you already run
The application can share records with your existing tools. That might be a CRM, Xero or Sage, a payment provider or a courier. Check what each supplier allows, which fields can change and how failed transfers are handled.
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.
| 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. |
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.
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
-
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.
-
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.
-
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.
-
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.
Common questions
What is bespoke web development?
What is the difference between a website and a web application?
Do you build mobile apps?
Can a web application work on a phone?
Do you build SaaS products?
Who owns the code?
The applications we are asked for most: customer portal software, ecommerce website development and website support and maintenance.
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