Re: <install> Element UX review

[Lia Hiscock]

+pwa...@chromium.org

---

From: Lia Hiscock <liahi...@microsoft.com>
Sent: Tuesday, January 6, 2026 10:41 AM
To: Yuchang Hu <yuch...@google.com>; Erin Ly <eri...@google.com>; Serena Chen <sere...@google.com>
Cc: Dan Murphy <dmu...@google.com>; Mike West <mk...@google.com>; Vincent Scheib <sch...@google.com>; Kristin Lee (EDGE) <krist...@microsoft.com>; Rob Paveza <Rob.P...@microsoft.com>
Subject: Re: <install> Element UX review

 

Hi folks, bumping this thread after the holidays. Also adding Serena who's been involved with some of our web install UX discussions.

Looking for guidance on next steps here — do we need to schedule a directional UX review?

Thanks,

Lia

---

From: Lia Hiscock
Sent: Thursday, December 18, 2025 3:52 PM
To: Yuchang Hu <yuch...@google.com>; Erin Ly <eri...@google.com>
Cc: Dan Murphy <dmu...@google.com>; Mike West <mk...@google.com>; Vincent Scheib <sch...@google.com>; Kristin Lee (EDGE) <krist...@microsoft.com>; Rob Paveza <Rob.P...@microsoft.com>
Subject: <install> Element UX review

 

Hi Yuchang and Erin!

 

Development for <install>, the declarative entry point to the navigator.install (Web Install API) functionality, is underway. There are no changes to any of the web app install or launch dialogs, which were already approved as part of the navigator.install review – Web Install UX review - Google Docs.

 

I’ve put together a UX Review doc as a jumping off point, is our next step here to schedule a directional UX review?

Google (Chrome) / Microsoft (Edge) Sync - Project Web Install - Google Docs

 

Feature request – [<install> Element] Enable Declarative installation of Web Apps from Web Content [454827186] - Chromium

 

I’ve also created a UX review task – [<install> Element] UX review [470131714] - Chromium

 

Thanks all!

Lia

[Dan Murphy]

As a side note (not sure how much this has been talked about) - I would love for the 'launch' button, if being shown in a web app context (in the standalone window), is changed to 'open in chrome', which would then reparent the page back to Chrome. This aligns with our strategic goal here to make transitions here more seamless.

e.g.:
 

On Wed, Jan 7, 2026 at 4:18 PM Erin Ly <eri...@google.com> wrote:

Hi Lia,

I spoke with Yuchang, and we can proceed with the UX review and approval via email.

Overall, the proposal looks good to me, and I see that all previous UX and UXW discussions that have been resolved. Regarding the recent comment on the edge case, I agree that clicking "Launch" within the app should not redirect the user back to the browser.

Additionally, we are currently working on an Install Dialog Refresh in collaboration with Serena. This project will account for the new declarative entry point and potential security risks. We have updated the flow to be more educational and better convey the permanence of the app.

Best,

Erin

[Dan Murphy]

(this can be a later iteration though, I don't want to block review here)

[Lia Hiscock]

Hi Erin -- Great to hear! We just touched base with Dan and we're on the same page about wanting "Open in Chrome". I've updated the section of the current UX review doc with new screenshots.

Let me know if you need anything else!

[Lia Hiscock]

Hey folks! If there's no further feedback here, we'll eventually need an SVG in the correct size created for the launch button. I believe @Yuchang Hu helped with this last time. Thanks!

[<install> Element] Generate launch svg in correct size [473847681] - Chromium

---

From: 'Lia Hiscock' via pwa-dev <pwa...@chromium.org>
Sent: Thursday, January 8, 2026 2:47 PM
To: pwa-dev <pwa...@chromium.org>
Cc: Dan Murphy <dmu...@google.com>; Lia Hiscock <liahi...@microsoft.com>; Yuchang Hu <yuch...@google.com>; Serena Chen <sere...@google.com>; pwa...@chromium.org <pwa...@chromium.org>; Mike West <mk...@google.com>; Vincent Scheib <sch...@google.com>; Kristin Lee (EDGE) <krist...@microsoft.com>; Rob Paveza <Rob.P...@microsoft.com>; Erin Ly <eri...@google.com>
Subject: [EXTERNAL] Re: <install> Element UX review

 

--
You received this message because you are subscribed to a topic in the Google Groups "pwa-dev" group.
To unsubscribe from this topic, visit https://groups.google.com/a/chromium.org/d/topic/pwa-dev/RquT5z8yaRs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pwa-dev+u...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/pwa-dev/dbc674f5-f909-48fe-88a2-cc008cc11af3n%40chromium.org.

[Dan Murphy]

(as another option) - this might be able to be done via css and the 'intent picker' icon today

[Dan Murphy]

I'm guessing that might be preferable for the text to be rendered in html/css, and the icon I think we have in our vector icons already as launch.icon or launch_chrome_refresh.icon.

When looking for those, you can search kLaunchIcon or kLaunchChromeRefreshIcon

example usage.

if you click the toggles menu, it's the icon next to site settings (on the right, not the gear)

+Mike West - how do you have other pepc elements styled? I'm guessing combination css/html/svg? Do they use the .icon icons at all?

[Lia Hiscock]

Ah interesting! I assumed it needed to be SVG as that's what Mike originally added in the initial prototype [<install> Element] Build a prototype. (7079238) · Gerrit Code Review

Which is then included here …/blink_resources.grd · Gerrit Code Review

and added to the element here …/html_permission_icon_element.cc · Gerrit Code Review

Open to alternatives though, I can add it to Thursday's sync agenda!

[Vincent Scheib]

In fugu sync the topic of the Install element behavior for already installed state came up. My take away from that discussion is that the install element, if already installed, displayed in a stand-alone window, should be an inactive button with text '✅ installed' (or similar) that doesn't invite user clicks. Preferably web developers will not show an install element in that situation. I don't think we should invite any behavior by clicking on that element, as it would need UX solutions, and potentially encourage developers to leave the element.  We had brainstormed several ideas, which I'll include in a follow up reply.

[Vincent Scheib]

brainstormed ideas from fugu sync chat:

• Discussing what should happen if the <install></install> element is in an already installed standalone window. Dan has proposed it should open the app in standalone.

• 

• Link to section of UX review doc – Google (Chrome) / Microsoft (Edge) Sync - Project Web Install - Google Docs

• Google chat review thread – Re: <install> Element UX review

• Tracking bug – [<install> element] Transform to "Open in Chrome" for <install></install> within a standalone window [475285741] - Chromium

• Discussed that web developers would expect. 

• Ideally web developers would not display the element when already installed.

• Make this configurable? 

• still need a default.

• Brainstorm of what happens if the element is still there?

• 'open in'

• new window

• new browser tab

• 'install' (same as below)

• '✅ installed' - on click.. 

• Nothing, not clickable. but needs the element to not look interactable

• (consensus that this is likely best solution)

• show custom dialog explaining what being installed means, similar to the install flow already.

• shows app info?

• open new instance

• hide element

Edge: