Page MenuHomePhabricator

IP Masking on iOS: Editing related changes
Open, LowPublic

Assigned To
None
Authored By
cmadeo
May 22 2023, 3:15 PM
Referenced Files
F37098470: Page message.svg
Jun 8 2023, 8:51 PM
F37098467: image.png
Jun 8 2023, 8:51 PM
F37098465: locked edit.svg
Jun 8 2023, 8:51 PM
F37098463: image.png
Jun 8 2023, 8:51 PM
F37098462: image.png
Jun 8 2023, 8:51 PM
F37098458: image.png
Jun 8 2023, 8:51 PM
F37098457: image.png
Jun 8 2023, 8:51 PM
F37098456: image.png
Jun 8 2023, 8:51 PM

Description

Summary of updates

Outlined below are proposed updates to the iOS editing flow for unregistered editors with and without temporary accounts. These updates were made to reflect proposed changes on desktop web related to IP masking work. Text in the screens below comes from proposed strings in the IP masking deck from AHT and may be subject to change.

Relevant links

Proposed designs

Additional onboarding screens for unregistered users without temporary accounts
Onboarding
image.png (1×750 px, 91 KB)
To be shown before editing onboarding screens when an editor is logged out and does not yet have a temp account. Learn more link to be provided by AHT in the future
Unregistered edits for users without temporary accounts
Editor - First unregistered editEditor with edit notice - First unregistered editFirst unregistered edit - tap on account iconTap on 'log in or create account'First unregistered edit - edit summary screenAfter publishing and a new temp account is created
image.png (1×750 px, 266 KB)
image.png (1×750 px, 267 KB)
image.png (812×375 px, 36 KB)
image.png (812×375 px, 41 KB)
image.png (1×750 px, 197 KB)
image.png (1×750 px, 699 KB)
Shown on first unregistered edit once in the editorShown on first unregistered edit once in the editor for an article with an edit noticeShown when tapping on the account icon in the header. Learn more link to be provided by AHT in the futureTap on 'log in or create account'Shown on edit summary screenShown after publishing only when a temp account is created based on the publish action
Unregistered edits for users with temporary accounts
Editor - Subsequent unregistered editEditor with edit notice - subsequent unregistered editsSubsequent unregistered edits - tap on account iconSubsiquent unregistered edits - create a new account or log inSubsequent unregistered edits - edit summary screen
image.png (1×750 px, 266 KB)
image.png (1×750 px, 266 KB)
image.png (812×375 px, 35 KB)
image.png (812×375 px, 39 KB)
image.png (1×750 px, 196 KB)
Shown to users editing with a temporary accountShown to users editing with a temporary account for an article with an edit noticeShown when tapping on the account icon in the header. IP address link to be provided by AHT in the futureShown when a user taps on 'log in or create an account'Shown on edit summary screen
Assets
Key illustration
image.png (226×145 px, 13 KB)
Unregistered edit without temp account icons
􀉵.png (19×23 px, 780 B)
SF Symbol: person.crop.circle.badge.xmark
Temp account edit illustration
image.png (456×464 px, 35 KB)
IP masking temp account icon
image.png (220×220 px, 4 KB)
from https://phabricator.wikimedia.org/T335694

Event Timeline

"...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!

cmadeo updated the task description. (Show Details)

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.

LGoto triaged this task as Low priority.May 23 2023, 4:30 PM

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