"...by adding a cookie to your browser."

May I suggest that this detail might be a little confusing, and might not even be necessary to surface to the user.
The user's login state is indeed handled using a cookie, but the cookies in this case are entirely internal to the app, and are not shared with any browser.

Hi @cmadeo @Dbrant - there has been some initial improvements and changes to messages and UI for the unregistered -> temp account user based on initial usability research (see findings and recommendations linked on T328368). One notable change is removing a lot of the jargon associated with messaging. And no doubt it may still continue to change moving forward, but it may be helpful to review the latest figma mocks that shows the various messages and UI elements added for now, and identify what could re-use the same string from web, vs need for a separate UI text for the apps.

These are fantastic, thanks for getting these done so quickly!

Can we make the Log in and Sign up the more dominant option @cmadeo. Otherwise the copy in the figma file Rita shared looks good.

Just to be clear again, because the answer has changed a few times, @RHo do you know if temp accounts will expire or did that get cut from scope?

Thanks @RHo and @Dbrant, I've updated the copy to more closely reflect the updates on AHT.

@JTannerWMF I made login and sign-up more dominant on the first onboarding screen, but in the pop-ups that a user can tap on once in the editor, how do you feel about keeping them as secondary as at that point they could lose changes they made in the editor? Happy to switch those too though if you prefer!

In T337250#8872128, @JTannerWMF wrote:

These are fantastic, thanks for getting these done so quickly!

Can we make the Log in and Sign up the more dominant option @cmadeo. Otherwise the copy in the figma file Rita shared looks good.

Just to be clear again, because the answer has changed a few times, @RHo do you know if temp accounts will expire or did that get cut from scope?

Temp accounts *do* expire, but the time period is TBC - details are in T300271. What has been cut is providing the ability for temp accounts to 'extend the expiry period', decision based partly on usability testing showing the expiry extension was not well understood and also likely to be an extreme minority of users.

Notes from @OTichonova:
Use of snack bar in edit summary is not quite right, perhaps a banner would make more sense here (similar to Talk pages)

FWIW the web version of status bar type message is T330510

@cmadeo Questions we had from engineering sync:

1. The CTA ordering on the onboarding view seems inconsistent. Sometimes "Log in or create account" is the primary button, sometimes it's the secondary button. Just wanted to make sure you are good with that.
2. I think we can get by without having the "Discard edit" alert. My hope is the login / create account flow can appear as a modal on top of the editor. Once they successfully get through that flow we should be able to dismiss it and reveal the editor again, without them losing their changes.
3. For the "Temporary account created" toast - we also show our existing "Edit published" toast whenever an edit goes through. Should that appear first or second? Unfortunately our existing legacy toasts system does not allow the display of multiple toasts, so we'll need to pick one to display first.
4. Where do these links go?
   • Learn more and IP address links in onboarding
   • Learn more in temporary account created toast
   • Read more in the Save Changes banners.
5. Just a heads up, currently the exclamation point for edit notices button in the navigation bar is gray. Just want to confirm that you want to change this to orange.

Hi @Tsevener thanks for these questions:

1. The CTA ordering on the onboarding view seems inconsistent. Sometimes "Log in or create account" is the primary button, sometimes it's the secondary button. Just wanted to make sure you are good with that.

Thanks for checking-in! This is by design based on if they are seeing the alert as an unregistered user or a temp account.

2. I think we can get by without having the "Discard edit" alert. My hope is the login / create account flow can appear as a modal on top of the editor. Once they successfully get through that flow we should be able to dismiss it and reveal the editor again, without them losing their changes.

Great! Even better!

3. For the "Temporary account created" toast - we also show our existing "Edit published" toast whenever an edit goes through. Should that appear first or second? Unfortunately our existing legacy toasts system does not allow the display of multiple toasts, so we'll need to pick one to display first.

No worries, please show 'edit published' first and 'temp account created' second

4. Where do these links go?
   • Learn more and IP address links in onboarding
   • Learn more in temporary account created toast
   • Read more in the Save Changes banners.

These will all be provided by AHT in the future as noted in the table above. Unfortunately I don't have any new information on these since this ticket was created -- could be good for someone on the apps team to reach out to #temporary-accounts-initiative although I did find this link which might fit the ticket: https://www.mediawiki.org/wiki/Help:Temporary_accounts

5. Just a heads up, currently the exclamation point for edit notices button in the navigation bar is gray. Just want to confirm that you want to change this to orange.

It'd be great to change it to orange to better match web, but if it's a big eng lift it's okay to keep it grey. Thank you!

Note: mocks of Save Changes banner > Read more screen can be seen in T340790.