Hi @GOlson-WMF - FYI we should hopefully have a couple of button components you can use here - WMFLargeButton and WMFSmallButton. You can reference WMFOnboardingView to see how they are used.

This fix has been merged - can be tested in TestFlight 7.6.0 (4193).

Fix is in https://github.com/wikimedia/wikipedia-ios/pull/5005

Experimental build will be 7.6.0 (171).

I'm kicking off an Experimental build @HNordeenWMF. I don't think I fixed it entirely, but maybe it will be at least improved. I'm sorry that I'm such a broken record here, but this is our custom navigation bar acting up again. We need to prioritize T363606 as soon as we get a moment, or else these bugs will continue to chew up time as we work on features.

https://github.com/wikimedia/wikipedia-ios/pull/5005

I see a different weird behavior where the watchlist Navigation (back and filter) moves upwards after I navigate to it: video

@HNordeenWMF Yeah I'm not sure why it's so scrunched, but the good news is the tap target is bigger:

Do we want to update screenshots for the app? The explore view now has the profile button instead of the settings button, and article view also has the profile button.

Estimating assuming we won't do nice-to-have from T376350: "add tracking into login flows to track logins/account creations that were triggered from Login/Account creation prompt."

Estimate assumes we won't do nice-to-have.

Info icon on each page links to in-app webview of mediawiki page

Add toggle into Settings called "Year in Review" that is automatically on. It can be added below "Explore feed" within Settings. Use SF symbol: timelapse. Reference for toggle → iOS Date & Time.

This could be easier if we had less UI to change before taking the snapshot. We have to build a new share card component, remove old elements, add new ones to the bottom. My bigger worry is users with dynamic type and smaller text - if content scrolls off screen does it take extra hoops to take a screenshot so that it doesn't scroll off screen?

Estimating assuming the old Share-A-Fact code will work well (which may rely on UIKit). We are making these slides with SwiftUI, so it might require a different approach.

Estimating without the nice-to-haves.

Estimating without the Nice-To-Have (fade out/in animation after tapping Continue).

Open question: Is this easiest to limit to the language that they have set as primary in the app)

Show primary language code in dynamic illustration

Is it easier to total for all languages? or just primary app language? Designs can be updated to clarify what total is referring to.

@MusikAnimal cool, sorry about that, I may have misinterpreted XTools "max of 30 concurrent connections" equivalent / sufficient for max 20 requests per second.

Hey Shay! That may actually be pretty old testing data, we ended up stripping is_anon from action_data and relying on the underlying automatic MEP library to send is_anon... let me know if that makes sense. I think you might already have more recent data with the fix.

@HNordeenWMF I think it would be good to cut this slide entirely since we don't have the data readily available and it's a heavy lift to pre-populate it.

Possible scope cut:

• Can we scope-cut linking for V1? That will take a good bit of additional work.

Question from sync:

@HNordeenWMF Should this announcement (screenshot 1) only be shown once?