Updated designs are available here: https://www.figma.com/file/cedgOU5CyOR0UVqtjDOvzE/iOS-Notifications?node-id=643%3A1085

Thanks for this update and clarification @Tsevener! I like the second approach (seems closest to the current design proposal 😉), but happy to make changes as things come up.

@Tsevener when you have the time, would you mind reviewing this Figma (https://www.figma.com/file/cedgOU5CyOR0UVqtjDOvzE/iOS-Notifications?node-id=549%3A1752) The 'page' should read 'Lock Screen Notifications v2...' I believe I was able to address all of the results of the spike in the lock screen and rich notifications, but please do let me know if I missed anything. Also happy to do this via a call instead!

Thanks for the clarification @Tsevener, so does this mean that the reorganizing or notification content to 1) pull out the thread as a subject line; 2) the username of the message center and; 3) the associated page where the notification occurred will be out of scope?

@Dmantena Sounds good to me! I was thinking the same thing! Thanks!

@Tsevener I'm just catching-up on the conversations happening here in the comments (big thanks to Roan for all of your help!)

@Tsevener thank you SO MUCH for this detailed breakdown (and super helpful spreadsheet!) I'm going to go ahead and make changes to the lock screen and system notification center notifications with these notes in mind.

Thanks @Dmantena

I think this is a case where it might be advantageous to use the "Featured article not available" type placeholder instead of actual content. While the placeholder context I mentioned above is more transient, this would display in persistent contexts where it'd potentially be unexpected to see an English featured article if that wasn't your primary language.

An alternative approach could be to curate a featured article per language we support for featured articles (19 languages), persist a cache of that data to bundle with the app (would increase binary size), and display it on failure. I think just the "not available for this date" message (localized to the user's language) would be a simpler alternative to this, especially since this error state isn't very likely to be displayed unless there is some catastrophic failure with the featured content API or the user intentionally changes their device time to something wildly out of range.

Thanks for all of these clarifications @Tsevener and all of the discovery work you've been doing!!!

@Tsevener sounds good on both fronts! I'll get working on an error state for setting up push notifications!

1. We have no featured article for the date to display (currently using this as placeholder: "A featured article is not available for this date.")

In T259842#7133125, @Dmantena wrote:

@cmadeo What should our placeholder content for this widget be (not the skeleton view, but the transient widget content displayed for preview purposes - on POTD for example, we use the 2019 Commons Picture of the Year)?

1. Trending current events is a different paradigm from echo notifications in that it's constructed from the explore feed data, kicked off locally and isn't tied to user data at all. I suggest we don't do this for client simplicity. It does sound like the backend team is considering these types of notifications eventually, so that would be good to wait until that is set up since it would flow through the same system and keep things simple on our end (see here).

Thanks @Tsevener, this is super helpful! I also found some definitions related to these fields on related mediaWikipages which I hope will help with clarifying in designs!

Good to know, thanks @Tsevener !

Currently available word marks: https://commons.wikimedia.org/wiki/Category:Desktop_improvements_project_logos?useskinversion=2

@Tsevener Will we know when there is no notification vs. when there is a notification but we can't fetch the content? (eg. in the second scenario is it still possible that there isn't actually a notification?) Thanks!

Thanks @Tsevener ! These are all super helpful updates!

Haha, no worries @dr0ptp4kt ! I love a good seal image!

For design reference, here's a WWDC talk that discusses large content viewers: https://developer.apple.com/videos/play/wwdc2019/261/

We will no longer be building out this experimental feature.

This is now possible with the redesign of share-a-fact that happened a few years ago :)

The design of share-a-fact has changed and this ticket is no longer valid.

The design of share-a-fact has changed and the text and image are no longer overlaid. If you would like to see text styling changes in the new version of share-a-fact please re-open this ticket with a new image and request.

@JMinor shall I close this as invalid as we will not be moving forward with this experiment? Thanks!

I'm curious if the tap target is a bit too small for this icon...

Another report from OTRS: https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=11867012

What are the known unknowns that we would like clarity on while designing the function editor?

Thanks @Ottomata + @colewhite! Do I still need approval from @lucyblackwell ?