Web apps

Software in the browser.

Portals, dashboards, booking systems, membership areas and internal tools.

A web app is not a brochure site. People open it in Chrome or Safari and use it: log in, book a slot, see their jobs, or run a dashboard. It lives on a URL. It is not an iPhone app you install from the App Store — that is a different product. iMake builds this kind of software for businesses across the UK and remotely.

Custom quote

Who it’s for

When a page to read is not enough.

Buy a web app when people must log in or do a job in the browser. If they only need to understand you and send a message, buy a website. If the product must live as an icon on a phone, buy a mobile app.

  • Customers need an accountThey sign in on a laptop or phone browser and see their own bookings, files or orders.
  • You run a diary or a job listStaff open a URL and update times or status. No app store install.
  • You have an idea for a toolA first version people can use in the browser, quoted after we understand the idea.
  • The team already works on computersA portal or internal tool in the browser is usually faster to start than a phone app.

What iMake can build

Browser products, not phone apps.

Each of these is a web app: it runs in the browser. They are capabilities — not a list of finished client projects.

01

Customer portals

A signed-in area on a URL for orders, documents or messages.

The customer bookmarks the site. They do not install anything.

Custom quote
02

Dashboards

The first screen after login: what needs attention today.

Built for a laptop or a wide browser window, and usable on a phone browser.

Custom quote
03

Booking systems

Times, staff or rooms, managed in the browser, with a confirmation.

A request form on a website is not this. This is the diary itself.

Custom quote
04

Membership platforms

Accounts, plans and content that only members see in the browser.

Courses, resources or a gated library — still a URL, not an App Store listing.

Custom quote
05

Internal tools

Job lists, handovers and small systems your team opens at a desk.

If the same tool must work in a pocket all day, look at a mobile app.

Custom quote

Use-case examples

What it looks like in a browser.

Interactive mocks of browser software. Not client products. Concept websites with a booking path sit underneath so you can see a related interface.

app.yourbusiness.com

Customer portal

They sign in and see their own records. This is a browser product.

Job #104In progress
InvoiceReady
MessageYou

Features and inclusions

What a web app build covers.

  • Product designScreens and flows first, so you can see how someone uses it in the browser.
  • Accounts if neededSign in, roles and the pages that sit behind the login.
  • The core jobPortal, dashboard, booking, membership or the tool — the thing people came for.
  • Works in a phone browserUsed in Safari or Chrome on a small screen as well as a desktop. That is still a web app, not a mobile app.
  • Testing and launchWe try the real paths, then put the URL live.
  • A fixed quoteAfter we understand the scope. No invented starting price.

How the project works

Understand the job. Then quote. Then build the URL.

01

Discover

Who uses it in the browser, what they must do, and what can wait. Then a quote.

02

Design

Screens and the path through the product, before we write the build.

03

Build

The working app in the browser, on real devices.

04

Launch

Test the important paths, then put the address in front of people.

Pricing

Quoted after we understand the idea.

Custom quote

A booking diary and a full customer portal are different jobs. Send the idea as it is. You get a fixed price before work starts. We do not invent a starting figure for web apps.

FAQ

Before you start a web app.

Start

Request a web app quote.

Send the idea as it is. We’ll help place it. Or look at pricing and concept work.