Skip to content
Interface language: English
Design / Signal

Should you offer to install a website? First find a reason to return

Choose when to offer installation by mapping a recurring task, the return from an icon and a useful path for people who decline.

Article language: English

A person holds a red comb against a long dark braid beside a bright window.
In this article

No one knows yet whether the rehearsal room has space for a drum kit, but the website is already offering an app installation. The customer came to check Thursday's availability. Instead, they are asked to decide whether to give a new resident space on their phone. The offer can be technically correct and still arrive at entirely the wrong moment.

An installable web application, often called a PWA, can make regular returns to a service easier. It cannot create a reason to return. First identify an action a person will repeat and the place the icon should open. Only then can you design a meaningful installation invitation.

Consider a fictional studio that rents music rehearsal rooms. A band books a session, later checks the time and equipment, and looks for another slot a week later. A new customer may visit only once to compare prices. Both use the same website, but installation means something different to each. They do not need an identical welcome.

Map an ordinary return first

At our studio, the recurring task is checking the next booking and finding another available time. The launch screen should support it. If the icon opens the brand history every time, customers still have to navigate through the menu. Installation has saved them typing an address, but it has not shortened the route to their rehearsal time.

Before creating a banner, map three specific entry points: a first-time customer comparing rooms, a returning user with a booking, and a band member opening a shared link. Each starts somewhere different. A common screen can offer routes to the calendar and bookings, but it should not pretend everyone has already booked something. First use and an empty state (in Polish) still matter after installation.

Improving the ordinary website is often the first useful change. Can people find the calendar through the mobile menu? The guide to mobile menus (in Polish) discusses how to design it. Does the confirmation message lead to the correct booking? Does its name distinguish the studio from a similar business? Installation should not be a condition for fixing these paths. A person who declines should still be able to complete the task efficiently in a browser.

Not every icon on a screen means the same thing. MDN distinguishes a bookmark, a shortcut to an ordinary website and an installed PWA; the installation method depends on the browser and platform.

When talking with the team, describe the intended result instead of stopping at "let's add an app". For the studio, that might be a direct return to a booking, clear navigation in its own window and a recognisable name on the device. Each needs separate confirmation in the working solution. A new icon alone does not prove the entire promise has been fulfilled.

A one-off visit leads to a different decision. Someone rents a room for a Saturday recording and later needs only the address and entry instructions. A well-prepared message may be enough. They should not have to install the service to read a paid booking. The design team should also be able to identify a situation in which it deliberately does not offer installation. The invitation then does not compete with more important information about opening hours or a room change.

A good moment is not a visit number

After the first booking is confirmed, a small invitation might say: "Coming back to rehearse? Add the Studio to your device to open the calendar more easily." The customer has just experienced the service, understands a future use and need not interrupt data entry. The ordinary route to booking details remains beside it. They can skip the invitation and read the confirmation immediately.

Do not assume every first booking should end with the same prompt. Someone may already have installed the service in another environment or be using a borrowed device. They may also be booking a room once for a workshop. A brief "Not now" should close the matter for the moment without making further work harder. There is no need to ask again every time booking details are opened.

The web.dev guide to installation prompts describes beforeinstallprompt, a browser event that enables a custom installation offer. It also notes that not all browsers support it. A custom button does not provide a universal way to invoke the system prompt.

The design therefore needs several real variants. Where installation can be launched, the button should lead to the appropriate flow. Where manual instructions are available, they should explain the steps for the recognised environment. Where installation is unavailable, or the correct way to offer it is unknown, the basic website remains useful. A dead "Install" button accompanied by a long repair guide does not help someone get back to rehearsal.

Instructions should end in a recognisable result. Name the icon the user should look for and show what opens when it is selected. Do not use one menu screenshot as instructions for every phone. Differences in command names and positions can be the very source of the problem. Record the configuration for which each variant was prepared in the project documentation.

Leave a way to find the offer later, for example in the service's help. Closing the banner need not mean rejecting installation forever. The person may not have had time or may have been using the wrong device. The later route should be available without pressure: it should still name the benefit and lead to a current method, rather than ask the user to undo a previous decision.

Review the custom message and the browser prompt together. Do they use the same studio name and recognisable icon? Does the promised feature follow from what the customer has just seen? If the site uses the room's name but installation shows an unfamiliar technical project name, a person may abandon even a simple process. Use the final identity elements for the test, not a temporary square with a letter. The audience does not know the team's internal names.

Aeneia Design

Aeneia conceptual photography

Let us map the route from an ordinary website to a repeated task in an installed service. The design will cover when to offer installation, how to decline and how to return from the icon, with variants based on the agreed device capabilities.

Design a return to the service from its icon

Installation finishes outside your screen

Pressing a custom button is not confirmation that installation succeeded. The user may close the next window, interrupt the process or lose their bearings after entering the browser menu. Separate those moments in the design. An "Installed" message should follow a recognised event, not merely a tap on the invitation.

There is no need to leave someone on an empty screen while installation happens elsewhere. Booking details should remain available. If a previously entered time selection disappears after returning from the menu, the invitation has caused extra work. Do not place it between choosing a time and confirming solely because a graphic happens to fit there.

At acceptance, distinguish what you can actually determine. MDN explains that display mode does not uniquely establish installation status. An installed service can still be opened in a browser tab.

This affects the wording. A page in a tab should not unconditionally announce, "You do not have our app." It is safer to describe an available action or the current way the page was opened. Custom copy need not guess the device's entire history. Before using detection to show repeated invitations, the team should understand the difference between no installation signal and confirmed absence of an installation.

The first launch from the icon is a separate design task

A customer installs the studio's service on the confirmation page for a Thursday rehearsal. A week later, they tap its icon. Will it open the same confirmation, the current list of bookings or the calendar? Each decision can be justified, but the default start should not follow accidentally from where the invitation appeared.

The MDN description of start_url identifies a suggested starting address in the manifest, the file describing the application. The documentation notes that browsers have discretion in how they handle it.

The studio's design might use a "Your rehearsals" screen, showing the next booking and a route to new times. When there are no active bookings, it does not present an old Thursday as current. Someone who is signed out understands how to sign in or browse availability. A date change between installation and return is part of the task, not an exotic test case.

Also establish navigation without the browser's usual surroundings. A customer opens room details, moves to equipment and wants to return to choosing a time. They need a visible route within the service if the display mode does not show familiar browser buttons. The same applies to help and leaving for an external site. Do not assume someone will discover a hidden gesture just because the designer uses it instinctively.

An icon does not solve authentication. If access needs to be confirmed on return, explain why and preserve the intended destination. When a session expires (in Polish), the customer is still looking for the specified booking. Do not send them to an arbitrary home page after a successful sign-in. With passkeys (in Polish), identifying the method and what happens after a device change need separate attention. Installing the service and accessing a particular account remain different matters.

If a phone is sometimes lent to other musicians, the launch screen must not equate the icon with a person. After sign-out, there should still be a clear route to the calendar, while private booking details require appropriate access. In the test, sign out the first user and then open the icon again. Record which information should appear and why. Do not infer identity from whoever once installed the service.

Treat a lost connection similarly. An installed icon is not a promise that an available time can be booked without contacting the calendar. If you show a previously saved booking, indicate which state it comes from. Offline work and sending changes later (in Polish) need their own rules. At our studio, a reasonable choice might be viewing saved information without confirming new times.

Also prepare for a booking changed by another route, such as by studio staff. On returning from the icon, the customer should recognise the current room or a notice that no fresh read is available. An old confirmation screen must not pose as a new check. In the acceptance material, distinguish what should be refreshed from the booking system from information retained for viewing. The design then describes the view's specific responsibility instead of assuming installation keeps data current.

Return by a different route from the one just used

Prepare at least two entry paths for the test: the icon and a link in a message to a specific booking. The second should not lose its destination merely because a general launch screen also exists. The user wants to see that particular rehearsal. Whether it opens in a tab or a separate window must be tested in an actually supported configuration.

Also complete an ordinary task after declining installation. Can someone change a time, find help and read the confirmation without being prompted again? Then check the return with an empty account, expired access and no connection. Record the device configuration, browser and entry method in the acceptance notes. A screenshot of an icon alone describes none of these flows.

Separate interest in installation from an assessment of usefulness. You can count offer openings, but answering our question requires observing the return: did the customer find the next rehearsal and start looking for another time? Record whether they returned from the icon, a message or an ordinary bookmark. Do not attribute every later successful task to installation. Without that distinction it is easy to polish an invitation that wins acceptance while leaving an awkward calendar.

At Aeneia Design, this scope can become a design for screens and interactions with specific conditions for displaying them. The starting point is a map of return journeys, not an order for a universal banner. At the end of our test, the customer should find the current booking and know where to look for another time. Installation is useful when it helps them return to that work after the project presentation has ended.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear