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

Prevent Brave from prompting user to add Brave Search Widget if the user already has the Brave Search Widget; only display notification 1x #27895

Closed
lukemulks opened this issue Jan 19, 2023 · 6 comments · Fixed by brave/brave-core#18159
Assignees
Labels
bug OS/Android Fixes related to Android browser functionality QA/No release-notes/exclude

Comments

@lukemulks
Copy link

Description

1. Brave notifies user to add Brave Search Widget, even when the user has already added the Brave Search Widget.

Screenshot_20230118_213524_Brave

  • I received an in-app notification with a message regarding adding the Brave Search Widget to my device homescreen.

  • This is a great prompt for feature discovery and tying Brave UX to homescreens.

  • in my case, I already have the Brave Search Widget installed and in active use.

If possible, we should have the browser run a check in advance to determine if the user has already added the Search Widget to their homescreen, in advance of notification.

Ideally, a boolean that follows that initial Widget check.

  • Brave locally checks for Brave Search Widget on client.

  • If detection determines user has not installed the Search Widget; then notify the user about the Brave Search Widget (as we already do).

  • If user has Search widget installed; then do not notify the user about the Brave Search Widget.

May only apply currently to a small cohort of lead users that dug into the homescreen widgets to discover Brave Search Widget a while ago, but would be good to have the proactive check to avoid folks claiming that the UX could be more locally tuned into client settings.

2. Only notify the user about the Brave Search Widget 1x/day (maximum).

  • While opening this issue, I was prompted a second time to add the Brave Search Widget that I had already added months ago.

  • When a user qualifies as not having the Widget already installed, only prompt them once about the Brave Search Widget feature.

  • 2x prompts within 30min of each other is pretty interruptive and jarring in UX, and users who already have installed the Widget may become even more frustrated with repeated notifications.

Steps to reproduce

Haven't attempted this; had installed the Search Widget months ago, so not sure on cadence and ability to force the notification.

  1. From homescreen, Select Widget options > Brave > Brave Search Widget > add Widget to homescreen
  2. Wait for Brave to notify about Brave Search Widget
  3. Receive in-app notification about adding Brave Search Widget

Actual result

Expected result

If I have Brave Search Widget already installed and active, do not notify me to add Brave Search Widget.

Issue reproduces how often

Version/Channel Information:

  • Can you reproduce this issue with the current Play Store version? Tbd
  • Can you reproduce this issue with the current Play Store Beta version?na
  • Can you reproduce this issue with the current Play Store Nightly version? Y

Device details

  • Install type (ARM, x86):
  • Device type (Phone, Tablet, Phablet): Samsung Fold3
  • Android version: Android OS v13

Brave version

1.47.175 Chromium: 109.0.5414.87 (Official Build) (64-bit)

Website problems only

  • Does the issue resolve itself when disabling Brave Shields?
  • Does the issue resolve itself when disabling Brave Rewards?
  • Is the issue reproducible on the latest version of Chrome?

Additional information

@lukemulks lukemulks added the OS/Android Fixes related to Android browser functionality label Jan 19, 2023
@lukemulks
Copy link
Author

Note: I am receiving the notification consistently each time I do the following:

  • Open new tab
  • switch to another tab
  • return to new tab
  • receive Search Widget notification prompt again
  • don't select either option (yes | no)
  • switch to another tab
  • switch back to new tab
  • get new prompt about Widget again
  • repeat steps above

I have counted 4 notification prompts for Widget within the past 30min, and could continue triggering more via steps above.

Since this is more than just an occasional prompt, going to assign and tag @anthonypkeane for visibility - feel free to reassign, but seems like potentially a misconfig for the notification.

@timchilds
Copy link

timchilds commented Jan 19, 2023

@lukemulks does the widget prompt still appear after selecting not now ?

Also, there are 3 Brave widgets:

  • Search Widget
  • Quick Actions Widget (the prompt adds this one to home screen. It now contains top sites - it didn't before)
  • Bookmarks

@deeppandya we should also decide if we want to suppress the prompt when:

A: User already has ANY Brave widget on the home screen.
B: User already has the Brave Quick Actions widget on the home screen.

We might want to update the copy also:

Try the Brave quick actions widget
Access your top sites and private, independent search right from your home screen.

cc @rmcfadden3

@deeppandya
Copy link

@lukemulks @timchilds we added the promo mainly for new quick action search widget. So if you don't have that widget on your home screen, it would show the promo but as soon as you click on not now, promo would go away for the user

@tapanmodh
Copy link

@timchilds @deeppandya do we want to update the promo copy as well?

@deeppandya
Copy link

@timchilds @deeppandya do we want to update the promo copy as well?

We don't need to update any copy here.

@kjozwiak
Copy link
Member

Labelling the above as QA/No & release-notes/exclude as the above isn't valid anymore due to removing the widget promo via #30618 which was uplifted into 1.52.x via brave/brave-core#18643.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug OS/Android Fixes related to Android browser functionality QA/No release-notes/exclude
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants