Per grooming discussion lets put the search history in both the search tab and when going to search from the search box.

Change to "From [Language Wikipedia]" as a phrase to translate, since gender endings aren't currently an option for iOS strings.

Only applies to White theme. So repro steps:

Per our meeting, a potential work breakdown/priotization based on "proximity" of the data to the Source in context. That is, source information is roughly in this priority:

1. Source's use in article (history, context, basic info)
2. About this article across Wikimedia
3. About this article from other online sources
4. About this article in meat space (library availability, etc)

New dev agreement accepted and "New Stores" checkbox checked, so we should be all set for the 4/10 expansion. Thanks again for flagging!

@Mholloway I think we're waiting for final copy from the community discussion. Once we have everything nailed down I think it can go live as soon as we can put it together and deploy.

triaging into infrahstructure as they need to do the final JSON and deploy.

Hey all, lets use the exhisitng announcement system as is, with just the Explore feed targeted. I agree with Carolyn that the full screen in-article banner is too aggressive given that this is just a supportive message, and we cannot limit what articles it is seen on. Its good to think about altnernative, less interruptive presetations for these uses in future, but I'm not willing to do any major updates or push app to app store right now, given our preference for lowering risks to the system.

This is mostly done, but per meeting could be smoother, esp in lookahead on media info in gallery.

Yes.

One more thing that would be helpful for us: can we get the impression count for those banners during this same time? Sorry I didn't ask this earlier.

Ok, will circle back with the team to get ETA for that. Sorry about this!

Lets see if we can do "disambiguation style" across all hatnotes at the service layer...

Looks good, but couple potential scope cuts/nice-to-haves:

Insertion cursor should be added to beginning of selected/matched search area, rather than scrolling to the top of section to insert cursor.

Per our sync, we do need to have the basic meta-information for all images in the gallery saved locally, so that when viewed offline, the user will seen information like license, caption and uploader. However, we do not need to have available the highest resolution of the image, the image as embedded in the page is acceptable.

Per our sync, we do need to have the basic meta-information for all images in the gallery saved locally, so that when viewed offline, the user will seen information like license, caption and uploader. However, we do not need to have available the highest resolution of the image, the image as embedded in the page is acceptable.

Unfortunately our system are not really integrated in a way that anything other than user reports or that is user agent like (platform, OS version, app version, language/wiki) is much help. So @pcombe thanks for that info, although it sounds like nothing is jumping out.

This is because we search by languge wiki, and do not use the wikidata coordinates currently. Ideally we'd have some kind of combined search that could fall back when Q items have coordinates but the template is not present on the wikipedia page. We may do this on the client, but perhaps worth discussion on the search index/API level.

A couple product/implementation notes:

• This is a hatnote that appears on this and other pages, but doesn't appear to be labeled clearly in the markup, so we'll need to look for the achor or something...
• Suggest we add special handling for this hatnote to make it visible just under the title (needs design)
• Not sure how universal this will be language-wise, would be good to know if/what other hatnotes or templates might exist outside english

Hey, seems like this isn't a priority on your end, and we've received no reports or complaints to the app store or OTRS regarding this, so I'm inclined to close this issue. If you have any customer emails on your end, you could just forward or copy/paste (minus payment/personal info) and send them to me or post it here. Transactions might be useful if they show the device (model or iPad/iPhone), app version, or other info derived from user agent. Just the donations themselves won't tell us much about the app :(