@Tsevener per our meeting, this list looks good to me! Thanks!

@SNowick_WMF + @Tsevener, I made some updates based on the comments above, let me know what you think :)

@Tsevener Great points all around. Yes, it'd be great to track to see if they have clicked through to the modal before the survey is shown. I would definitely hope that seeing the modal would affect survey outcome. Let me make some updates to the flow.

@Tsevener and @SNowick_WMF I've added a rough flow diagram to this ticket, let me know if it needs any changes! Realizing this might be too simplistic?

@Tsevener oh awesome! Here are two mocks:

In T257595#6499039, @Tsevener wrote:

@cmadeo One last question I have at this point - these events can happen across multiple days, and if they are further in the past they switch from a relative timestamp to an actual timestamp. I re-used the History cell timestamps for this logic, but I could make them entirely relative if you'd like...i.e. 3 days ago, 2 weeks ago, etc. Would you like me to make them all relative, or would you like to keep the switching to a GMT timestamp? If you want them switching to GMT, we will probably want to add in a day/date too, as it's not apparent that these events are happening across multiple days.

In T257595#6499001, @Tsevener wrote:

I still need to tweak spacing and font sizes, but here's a look at the colors I chose for theming. Let me know if you'd like to make any changes with these.

These are looking great (color-wise), Toni!

@Tsevener, thanks! Responding inline:

Thanks for finding and filing this @Dmantena!
Yikes! Yeah, there is currently a lot of movement.

@Dmantena Thanks for pointing this out! Let's go ahead and make this change. Do you need any assets from me?

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

OTRS Ticket: https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom;TicketID=11521300

@Tsevener Here's a kinda rough version of what a skeleton could be like. It'd be awesome if we could have a bit of a shimmer effect to show that it is loading.

Thanks for these gifs @Tsevener!
I think we'll definitely want to have a tiered loading state where we wait to show the web content until the badge/card are loaded unless it hits an upper time limit, in which case we'll load the web (article) content and then have a loading state for the badge/card.

@Tsevener re our meeting with Shay

We should put focus on the associated tapped revision, especially if the revision is currently visible.

Updated the task description to include iPad designs and Zeplin links

Hi @schoenbaechler, this is looking really great! In particular I really like how the sparkline adds context to these cards!
One thought is that the gradient right now looks a little bit hard to read, I think this might be because the gradient of the number is flipped with the gradient of the circle, this gives it a bit of a 'shimmer' effect but also I worry might cause a bit of eyestrain (also possibly just a personal issue!) One thought is that you could use a similar gradient to iOS (top of the full list of numbers is blue, bottom is green -- gradient goes across all of the numbers) but if this feels a bit too subtle you could up the contrast between the two colors used?

Ah, yeah we'll definitely need something. Let me work on some ideas today. Also -- curious how this will effect the 'Recently updated' badge at the top, is that by any chance something that could load at the same time as the body text @Tsevener ?

Ah, sorry I mis understood the question -- I thought this was about tracking exactly where card_discuss lead to. If possible can we keep (ard_editor, card_discuss, card_change and card_more as separate events?

I love this idea, but I don't know if this is something we can support right now. It does look like you can have multiple of the same widget (size and type) so if we can find a way to customize them, I'd be happy to do a design to support this user story