Status-react: Update Beta alert

Created on 1 Feb 2019 · 12Comments · Source: status-im/status-react

Problem

When I create a (new) account on Status Beta, I receive an alert that:

informs me about the Beta state
informs me to manually select Mainnet if I'm upgrading an existing account
warns me that the app is on Mainnet and transactions are real, and transfers to testnets

The message is long, obtrudes the UI and the number of users still upgrading from pre-beta likely has decreased.

The warning needs to be updated and potentially differ between recover and create account.

Copy will be iterated on in the comment thread of this issue.

Current implementation

mainnet alert android
mainnet alert ios

Acceptance Criteria

UI same as current warning, but with updated copy.

warning shown when I create an account
warning shown when I recover account
warning shown when I create the account in release and upgrade
warning shown when I recover account in release and upgrade to this build

Notes

This is the issue created in June to support Beta release https://github.com/status-im/status-react/issues/4718

Future Steps

Create new account
Upgrade existing pre-beta account?

bounty-xs

Source

hesterbruikman

All 12 comments

Proposed copy

Disclaimer
Status is in Beta and on the Ethereum Mainnet. Use it wisely. Don't store more crypto than you need for testing and only share data with people you trust. By using the app you assume full responsibility for all risks concerning your data and funds.

beta alert

hesterbruikman on 4 Feb 2019

Like the copy. Waiting on a design update?

cc @dmitryn who I think added the first beta warning. Dmitry, might be useful to have your eye on this if future bounty contributor needs any help.

rachelhamlin on 5 Feb 2019

Pinged @andmironov to take a look. Don't think we have much design control over native modals, but just in case.

hesterbruikman on 5 Feb 2019

👍1

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

__This issue now has a funding of 40.0 DAI (40.0 USD @ $1.0/DAI) attached to it as part of the Status-im fund.__

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
- Want to chip in? Add your own contribution here.
- Questions? Checkout Gitcoin Help or the Gitcoin Slack
- $56,851.33 more funded OSS Work available on the Gitcoin Issue Explorer

gitcoinbot on 11 Feb 2019

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

__Work has been started__.

These users each claimed they can complete the work by 11 months, 1 week from now.
Please review their action plans below:

1) zeddee has been approved to start work.

Hey there,

I'm a tech writer; you can find my writing samples here: https://zeddee.com/cv

At first glance, I can probably:

structure the notice better (bullet points)
cut the copy by ~30%

Learn more on the Gitcoin Issue Details page.

gitcoinbot on 13 Feb 2019

@StatusSceptre I don't think I have the ability to manage this on Gitcoin, but we are looking for someone to implement the copy change Hester suggested in the existing modal, so it's a code requirement not a copy one :)

rachelhamlin on 14 Feb 2019

hey @rachelhamlin ; sorry about that — somehow mis-parsed the ticket. I can do the implementation; quick grok tells me it's a change to the /translations/en.json file.