Opened 5 months ago

Last modified 4 months ago

#30540 new enhancement

Give TBA alpha users a link to stable

Reported by: sysrqb Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-mobile, ux-team
Cc: steph Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

GeKo mentioned we should tell current Tor Browser alpha users on Android there is now a stable version they can use. This seems wise.

Should we add this into the onboarding panels or should this be included on about:tor? It seems we should use the same download links here as discussed on #29955.

Child Tickets

Attachments (2)

2.png (48.6 KB) - added by antonela 4 months ago.
1.png (58.4 KB) - added by antonela 4 months ago.

Download all attachments as: .zip

Change History (7)

comment:1 Changed 5 months ago by antonela

Keywords: ux-team added

Changed 4 months ago by antonela

Attachment: 2.png added

Changed 4 months ago by antonela

Attachment: 1.png added

comment:2 Changed 4 months ago by antonela

Cc: steph added

Based on what we talked last week, I made two options to handle this issue.

  1. Dialog Box - https://www.material.io/design/components/dialogs.html

https://trac.torproject.org/projects/tor/attachment/ticket/30540/1.png

hellais suggested to do it in two steps by first asking users if they are developers and if they reply NO, then recommend them to download the stable app. I approached this version to solve this with one step. In this way, when users click [download stable], we open the Tor Browser stable download page.

  1. First Screen

https://trac.torproject.org/projects/tor/attachment/ticket/30540/2.png

If we consider that we should block the entire screen for this action, we could use a full-screen option. It should show before the onboarding on new users and one/two times on recurrent users.

We should update the description at Google Play too, so we don't have new users downloading the Alpha version by error. It is most urgent, imo. I'm adding steph because we need wording for this.

Also, Google Play calls developer versions as Beta. Should we attach to gplay standards and replace Alpha for Beta in mobiles?

We need a funnel for this and define which releases will contain this prompt. Also, what is the % of users we expect to move? Will we remove the prompt once we achieve it?

If we succeed on the moving, users will still have two versions of TBA installed in their devices. Can we do something to prevent users to successfully download the stable app but still use the alpha one as default?

comment:3 Changed 4 months ago by clash

Do you just want to target developers with the alpha or anyone who wants to try out the newest features/fixes before they're added to the stable version and give feedback? If users who want to live on the bleeding edge and are happy to provide early feedback are a target too then just the 'developer' terminology may not be as apt.

Also, removing alpha might be cool since right now it reads "Tor Browser (Alpha) (Beta)" on the Play Store :)

comment:4 in reply to:  3 Changed 4 months ago by gk

Replying to clash:

Do you just want to target developers with the alpha or anyone who wants to try out the newest features/fixes before they're added to the stable version and give feedback? If users who want to live on the bleeding edge and are happy to provide early feedback are a target too then just the 'developer' terminology may not be as apt.

It's anyone that wants to help us find issues in features/fixes that might make it to the (next) stable release. At least until we have a proper nightly channel set up. Once we are there we could think about splitting up that group further and tailor the series even better.

comment:5 in reply to:  2 Changed 4 months ago by gk

Replying to antonela:

Based on what we talked last week, I made two options to handle this issue.

  1. Dialog Box - https://www.material.io/design/components/dialogs.html

https://trac.torproject.org/projects/tor/attachment/ticket/30540/1.png

hellais suggested to do it in two steps by first asking users if they are developers and if they reply NO, then recommend them to download the stable app. I approached this version to solve this with one step. In this way, when users click [download stable], we open the Tor Browser stable download page.

  1. First Screen

https://trac.torproject.org/projects/tor/attachment/ticket/30540/2.png

If we consider that we should block the entire screen for this action, we could use a full-screen option. It should show before the onboarding on new users and one/two times on recurrent users.

Thanks. I like option 1, I think. I am not sure about he full-screen option. Is that a thing an Android user would expect?

We should update the description at Google Play too, so we don't have new users downloading the Alpha version by error. It is most urgent, imo. I'm adding steph because we need wording for this.

Agreed.

Also, Google Play calls developer versions as Beta. Should we attach to gplay standards and replace Alpha for Beta in mobiles?

I am not sure yet, but we could think about it. Nevertheless, this would be a new ticket and we should not try to solve that here, too.

We need a funnel for this and define which releases will contain this prompt. Also, what is the % of users we expect to move? Will we remove the prompt once we achieve it?

I don't know what % we would expect. I think we should ship it for quite some time and we should design the feature in a way that the user gets prompted after the first update to a version with the feature under discussion here. Subsequent updates should not trigger it. I think users that download the alpha now-ish should not get it either given that we have the stable around for a while now.

If we succeed on the moving, users will still have two versions of TBA installed in their devices. Can we do something to prevent users to successfully download the stable app but still use the alpha one as default?

Good question. Maybe, I guess?

Note: See TracTickets for help on using tickets.