---
title: "Web experiences: send a link, no app or headset needed"
description: "Browser-based experiences that open from a link on desktop or mobile with no download: what PTR builds on the web, live Labs demos, and how to start a build."
canonical: https://peopletechrevolution.com/fast-builds/web-experiences
---

<!-- Machine-readable copy of https://peopletechrevolution.com/fast-builds/web-experiences. The HTML at that URL is the
     canonical document; this file is the same words without the markup. -->

[Fast Builds](https://peopletechrevolution.com/fast-builds)

# Web experiences

Send someone a link and the experience opens in their browser, on desktop or mobile, with nothing to install and no headset required.

A scroll-driven story, moving as the reader scrolls.

## One link is the whole rollout

A web build lives at an address. The people it is for open it in the browser they already have, on the phone in their pocket or the laptop on their desk, and nobody installs anything.

The published Fast Builds timeline applies: [rapid prototypes](https://peopletechrevolution.com/fast-builds/rapid-custom-builds) from two business days, full builds up to eight working weeks.

[How Fast Builds run](https://peopletechrevolution.com/fast-builds) [Try the browser demos](https://labs.peopletechrevolution.com/play)

## What you bring, what you get

A web build starts with the problem you already have and ends with something your people can open today.

Reviewing a web build across two screens.

### Any screen, the same build

You bring the brief: who the experience is for, what they need to do, and what it has to prove. PTR builds the working page, puts it in front of the people who matter, refines it and ships it.

What comes back is a link you can share the day it is ready, and a build that keeps evolving after launch.

### Where a web build gets used

The browser is wherever the work is: a warehouse aisle, a kitchen bench, a table with three devices on it.

A picking aid, opened between the racks.

A tablet plan, checked at the bench.

Comparing the build across devices.

Trying the build on a large touch screen.

### Reach over depth

A browser build trades some depth for reach. It opens from a link on a device someone already has, which suits a fast prototype, a low-friction first touchpoint, or a demo shared before committing to a larger build.

It is the weaker choice when the experience needs a headset's sense of presence, an app's offline access or device sensors, or processing better handled outside a browser. Those needs shape the platform choice, and PTR says so in the brief.

> "In a world where much of our learning has moved online, the human element is often lost. VR can help bridge this gap, allowing people to practice real-world interactions in a controlled, immersive environment."

Simon Lowe
CEO, People Tech Revolution. [The Cusp of a Revolution, Global Best Practice Group, October 2024](https://globalbestpracticegroup.com/airevolution/)

## Try one now

PTR's browser builds are live on Labs Demos. Open them on a phone or laptop; nothing installs.

[AR Business Card. An augmented reality business card that runs in the browser on a phone or laptop.](https://labs.peopletechrevolution.com/play/ar-business-card)[The Pissing Game. The camera tracks your hands and you aim without touching the mouse; the video never leaves your device.](https://labs.peopletechrevolution.com/play/the-pissing-game)[Immersive Learning Wall. Stand back and move: full-body pose tracking lets your hands push, gather and burst the ideas on the wall.](https://labs.peopletechrevolution.com/play/immersive-learning-wall)

### Every step, visible

You see working builds in sprints, not a single reveal at the end.

The same page tested on every screen.

### Brief, Build, Test, Refine, Ship

Brief pins down what the page has to prove. Build turns it into something people can use. Test puts the working build in front of the people who matter. Refine changes what they showed you. Ship deploys it and keeps improving it.

The five steps are the same on every Fast Build; the detail of each is on the [Fast Builds](https://peopletechrevolution.com/fast-builds) page.

The first wireframe block, nudged into place.

The same block, one revision later.

## When the brief needs more than a browser

Some experiences need hands in the scene or a room around the person. PTR builds those too, through the same steps, and the web build is often where they start.

Turning a component above the lab bench.

A cook tests a mould at the bench.

A footwear designer checks a shoe last.

A page laid out before the words arrive.

### The shape of the page comes first

Before a line is written, a web build already has a shape: what a person meets first, what they are meant to do next, and where the one thing that matters sits. Get that order wrong and better sentences will not rescue it.

So the empty structure goes in front of the people who will use it early, in the same five steps as everything else, and it changes while it is cheap to change.

Two people choose speech tiles beside a display.

### Words are part of the build

A web experience is read as much as it is used. The copy on the page, the labels on the controls and the line that tells someone what to do next are shaped with the client's team, in the same sessions as the layout.

When the page carries a conversation, the words get tested with the people who will read them, not written once and left.

## Where to go next

The other routes a browser build can take, and the pillar page that explains the process behind all of them.

[Mobile experiences. iOS and Android apps, and AR on the phone, when a browser is not enough.](https://peopletechrevolution.com/fast-builds/mobile-experiences)[Augmented reality. A printed page gains a layer, seen through a phone held over it.](https://peopletechrevolution.com/xr/augmented-reality)[Custom AI experiences. An experience built around one organisation's own approved knowledge.](https://peopletechrevolution.com/ai/custom-ai-experiences)

Need a web build your team can start using quickly?

[Open the contact form](https://peopletechrevolution.com/fast-builds/web-experiences#contact)
Ask our CEO Simon Lowe’s Digital Twin a question

Related PTR work

- [Fast Builds overview](https://peopletechrevolution.com/fast-builds)
- [Games and interactive experiences](https://peopletechrevolution.com/fast-builds/games-interactive)
- [Rapid custom builds](https://peopletechrevolution.com/fast-builds/rapid-custom-builds)
- [Labs Demos](https://labs.peopletechrevolution.com/)
