Insight / Web and apps
Published
Install a page as an app or create a shortcut: what actually changes?
An icon can open a browser tab, a dedicated web window or a purpose-built PWA. Learn what each route changes and when the extra work earns its place.
An icon on a phone or desktop tells you where to start. It tells you much less about what will happen next. A website shortcut, a site installed in its own window and a progressive web app (PWA) can look similar in a launcher. Their capabilities come from the website and the browser, not from the icon alone.
If you need the menu steps for a particular device, use our guide to saving a website as an app. Here, the question is what kind of experience you are creating for people once they tap it.
A shortcut is a route back
A shortcut points to a web address. It saves someone from searching, typing a URL or finding a bookmark. Depending on the browser and device, it may open the site in a normal tab and carry a browser badge. The site still has the same content and features it had before the shortcut was made. A shortcut is often enough for a menu, reference page or occasional customer task.
It is easy to confuse convenience with capability. A shortcut does not download every page, preserve form entries or make a server available without a connection. If those outcomes matter, the product needs explicit offline and recovery work.
A site can open in its own window
Some browsers let people install an ordinary website as an app, giving it a launcher entry and a dedicated window. Microsoft Edge, for example, distinguishes a “site as app” from a PWA: the site can open separately while lacking the richer PWA capabilities. On iPhone, Safari’s Add to Home Screen flow includes an Open as Web App option. Browser labels and the resulting launch experience vary by platform.
That separate window can help with a task someone returns to throughout the day. It can also make an ordinary site feel more like a complete application than it is. Check the actual behaviour on the devices your audience uses, including links that leave the site, sign-in, updates and what appears when the network drops.
A PWA is a product decision
A PWA adds installation metadata through a web app manifest. That can define its name, icon, start page and preferred display mode. Browsers apply their own installability rules, so an install prompt is not identical everywhere. A service worker can cache chosen pages and assets for offline use, but one is not automatically required for installation, and its presence does not make every feature work offline.
The useful capabilities are built separately: locally available content, a reliable way to keep user changes, notifications where supported and permitted, and a clear update process. In fact, offline caching can work in a browser tab without the visitor installing anything. Installation changes how a person returns to a product; engineering determines what the product can do.
Choose the smallest experience that serves the task
Start with how often the person returns and what must work when they do:
- Quick access to information: make the website responsive and easy to bookmark or save as a shortcut.
- A repeated, focused workflow: consider a dedicated app window, then test its real browser and device behaviour.
- Essential work during poor connectivity: design the offline tasks, local data and recovery rules first. Add PWA installation when the dedicated launch experience helps people use them.
- A need for platform-specific features or store distribution: compare a web route with a native or cross-platform app against the required capabilities and ongoing delivery work.
Whichever route you choose, describe it accurately. “Add this icon for quick access” is a clear promise. “Works offline” is a larger one that should be tested with a disconnected device, a slow connection and a failed update. The best choice is the one that makes the user’s important task dependable after the first tap.