Riv file here: https://drive.google.com/file/d/1W4aeTtbd6AJZAM4ZsXhVjvHl-kDUVxVn/view?usp=drive_link

It looks great, thank you so much @LPetty-WMF

DQA here: https://docs.google.com/spreadsheets/d/1sYK0CrlyLV_bWiX6j4wLoHOhMIVrKoqIQ4Za_nV7ZAA/edit?gid=2040432267#gid=2040432267&range=A5 - fix priorities to be reviewed by @ABendall-WMF

DQA here - priorities to be confirmed with @ABendall-WMF: https://docs.google.com/spreadsheets/d/1sYK0CrlyLV_bWiX6j4wLoHOhMIVrKoqIQ4Za_nV7ZAA/edit?gid=1341257511#gid=1341257511&range=A5

Design QA here - https://docs.google.com/spreadsheets/d/1sYK0CrlyLV_bWiX6j4wLoHOhMIVrKoqIQ4Za_nV7ZAA/edit?gid=1942592474#gid=1942592474&range=A5 - pending PM review for priorities cc: @ABendall-WMF

Other areas I checked are all good; I just want to document this here for future reference. F[[ https://www.figma.com/design/s3KF9DqhJg2aAHpZBS8lwg/iOS---Android---%253E-Semantic-Search-%257C-Phase-2?node-id=7219-29167&t=PWHxeB7k6nTzD1yO-11 | igma link ]]

1. Links are underlined when highlight is present ✅
2. Highlight colours work as expected across our 4 themes ✅

Design QA here: https://docs.google.com/spreadsheets/d/1sYK0CrlyLV_bWiX6j4wLoHOhMIVrKoqIQ4Za_nV7ZAA/edit?gid=1586821276#gid=1586821276&range=A5

Same questions I had for Android I have here (please see parent ticket)

3 questions about the requirements here, as I am doing the Design QA:

@HNordeenWMF Rive implementation is documented sufficiently for future animations to follow the same pattern.

Animation is done in Rive, asking for Maryyann's support on best practices for exporting to our platform

Talked to Jaz via Slack about this AC line:

@JTannerWMF @ABendall-WMF for Android I am proposing we open a new Search module for this feature so it is easy to find it (instead of placing it under "General" module. The rationale is that this is a highly used feature, and I think it is important to dedicate a section to it (we do that in iOS). Mockup here: https://www.figma.com/design/s3KF9DqhJg2aAHpZBS8lwg/iOS---Android---%253E-Semantic-Search-%257C-Phase-2?node-id=6812-43349&t=37uH7AOV3YjzHiWd-11

Illustration looks great now @EAlbizzati-WMF Thanks!

Thanks @LPetty-WMF - Design QA here: https://docs.google.com/spreadsheets/d/1sYK0CrlyLV_bWiX6j4wLoHOhMIVrKoqIQ4Za_nV7ZAA/edit?gid=1476368118#gid=1476368118&range=A5Pending review by @ABendall-WMF for priorities alignment.

will move this back to "Doing" column

It looks great across themes and devices - tested on iPad and iPhone! I have only a small issue on the illustration that I am seeing: https://docs.google.com/spreadsheets/d/1sYK0CrlyLV_bWiX6j4wLoHOhMIVrKoqIQ4Za_nV7ZAA/edit?usp=sharing - cc: @ABendall-WMF

Hey @LPetty-WMF, there was a design update on this screen. See here: https://www.figma.com/design/s3KF9DqhJg2aAHpZBS8lwg/iOS---Android---%253E-Semantic-Search-%257C-Phase-2?node-id=5872-30692&t=MQd2F4jMhf6GPRKG-11

@JTannerWMF, for the in-article feedback component, we could have the thumbs up/down + text field visible at once since this is a bottom sheet and we have the space for it. In this way, the feedback is perceived as faster since readers see all in one go.Let me know what you think. Mockup: https://www.figma.com/design/s3KF9DqhJg2aAHpZBS8lwg/iOS---Android---%3E-Semantic-Search-%7C-Phase-2?node-id=6690-36657&t=mgK1HJp5ez5L3tDe-11

Design QA done, all good from the design side! Thanks @Cklimas

Design QA here:
• iOS: https://docs.google.com/spreadsheets/d/1rkideEnNj_KQifxEYJae61z7Roi84fxvuAUDVA-Zpac/edit?gid=1546792862#gid=1546792862&range=A4
• Android: https://docs.google.com/spreadsheets/d/1rkideEnNj_KQifxEYJae61z7Roi84fxvuAUDVA-Zpac/edit?gid=1972004272#gid=1972004272&range=A4

Good point here: Test behaviour when the anchor no longer exists in the live article because a section was renamed or removed.

That was the design intention as well: the bottom sheet blocks users from changing the language, so I am aligned with the experience as described by Toni. Curious if Abi and Jaz intended something different after reading this requirement line.

Hey @Tsevener, I am still working on it and talking to Jaz about this view. As it stands now, we will keep following the pattern of "history" being dedicated to articles users visited, and recent searches will be the space for queries. We won't have cards displayed on recent searches (or history), and we are aiming to simplify the interface as much as possible. @JTannerWMF FYI

Android exploration for product alignment before I build the iOS version (iOS will be a bottom sheet based on other onboardings we have). Do we have any bottom sheet onboarding with more than one step in our app already @Tsevener? If so, I would like to follow the same standard. https://www.figma.com/design/s3KF9DqhJg2aAHpZBS8lwg/iOS---Android---%3E-Semantic-Search-%7C-Phase-2?node-id=6144-60980&t=mIRh9YrNTKYqwmlX-11

Did the Design QA again, and good to go. All issues were fixed; thanks @EAlbizzati-WMF

Discussed the Sepia theme with Jaz today. I'll meet with Derek next week to explore accessible highlight color options for the Sepia theme.
Explored Show more vs truncation and leaning more toward truncation because it is cleaner (the card is already dense), and "show more" may give users the idea that the card will expand from that view.

Thanks @EAlbizzati-WMF - design QA here, it needs @ABendall-WMF's confirmation on items we want to act on based on priority: https://docs.google.com/spreadsheets/d/1J_TM_hIfFhwRbWfwaBzE4XNJqkmw-eaYM3AXFT0gviA/edit?gid=2035234400#gid=2035234400&range=A5

The body copy is a condensed version of the onboarding message and uses the same feature name and the same claims — the two must not describe the feature differently.

Currently figuring out if quotation marks need to be updated for each test language. Asked via Slack.

Discussed with Cooltey and Lamar via Slack thread. We decided to lock the screen in portrait mode so we can keep the update button visible when the keyboard is visible. Good to go. Thanks all

I can't access the Update button if I have a custom amount in the text field. Sent the issue via Slack for discussion of possible design solutions.

Awesome, thanks! All good. Moving to the next column.

Thanks for the list detailing what I should be looking at, @cooltey - here is the Design QA punch list:
https://docs.google.com/spreadsheets/d/1J_TM_hIfFhwRbWfwaBzE4XNJqkmw-eaYM3AXFT0gviA/edit?usp=sharing

Thanks, @cooltey - Design is working as expected. I imagine that with the translation, the copy will be longer, but I see that we already have the fade in place for cases in which the copy is longer than what fits in the box. Flagging for @ABorbaWMF for when we have the final copy for QA.