Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overlapping banners on Android mobile web #37021

Open
rachelmcr opened this issue Oct 24, 2019 · 5 comments
Open

Overlapping banners on Android mobile web #37021

rachelmcr opened this issue Oct 24, 2019 · 5 comments

Comments

@rachelmcr
Copy link
Member

rachelmcr commented Oct 24, 2019

There are two banners that overlap in Calypso on Android mobile web:

  • Mobile app promo banners
  • Progressive Web App banner ("Add WordPress.com to Home Screen")

The PWA banner completely hides the “Open in app” and “No thanks” buttons on the app promo banner.

Steps to reproduce

  1. Go to WordPress.com in Chrome on an Android device.
  2. Log in or sign up for a new account.
  3. If you don't see the PWA banner (if you previously dismissed it) go to History -> Clear browsing data (make sure that the option to clear Cookies is ticked) then click the Clear Data button.

Browser / OS version / Device

Confirmed on Chrome / Android 8.1.0 / moto e5 play

Screenshot

Left: Overlapping banners
Right: App promo banner with visible buttons after dismissing PWA banner

image

h/t @theck13 for reporting this for investigation (internal ref: paaHJt-hO-p2)

Context

Related work:

There was some discussion/review of the app promo banners (internal ref: p9OQAC-g7-p2) that led to a proposal that we move those banners to the top of the screen (internal ref: pauD4L-iZ-p2). If we move that proposal forward, it would resolve this issue by having the app promo banners at the top and the PWA banner at the bottom. However, moving the app banners to the top would create a double banner on iOS (app promo banner + iOS system smart banner) — that might require us to take a different approach to any changes to the app promo banners. cc @mattmiklic @osullivanchris

@mattmiklic
Copy link
Member

Just from some quick searching it looks like it may be possible to prevent the PWA banner from appearing in Chrome -- this seems like the best option as it doesn't make much sense to promote both a native app and a PWA at the same time, at least given what I know.

We’ve been listening to our community and what we heard was that developers want more control over when to ask users to install a PWA. We heard you!

Starting in Chrome 76, you can prevent the mini-infobar by calling preventDefault() on the beforeinstallprompt event.

https://developers.google.com/web/updates/2019/05/mini-infobar-update

Maybe a developer could look into this and let us know if this is indeed an option?

@rachelmcr
Copy link
Member Author

Just from some quick searching it looks like it may be possible to prevent the PWA banner from appearing in Chrome

Great to know we have more control over how the PWA is promoted! When the PWA banner was added (#26494) the idea was to promote it to e.g. Pixelbook users. If we remove that default PWA banner we probably want to replace it with something targeting those users (who won't see the native app banners), rather than removing it entirely.

cc @gravityrail - just a heads up about this issue/discussion.

@osullivanchris
Copy link

@mattmiklic @rachelmcr I'll also follow up on the work we did for these banners mid next week when I've a couple of other things over the line, and see if we have a clear proposal to improve them.

@mattmiklic
Copy link
Member

If we remove that default PWA banner we probably want to replace it with something targeting those users (who won't see the native app banners), rather than removing it entirely.

👍 It sounds like in that Google documentation that that's what's recommended. Though I think Pixelbook users can install Android apps now as well, for what it's worth, so maybe it'd be worth discussing whether the PWA or the native app is what we'd prefer to promote.

@github-actions
Copy link

This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants