This happened in conjunction with the conversion from native footer to JS transform footer:

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

We can easily do a vertical layout:

One benefit of the vertical layout is better Android compatibility when this transform gets consolidated - the side-to-side inertial scrolling is non-standard webkit CSS.

Reminder: here's the CSS change for vertical layout.

@cmadeo

Oh on tablet we used to have a white background behind the footer. Do we want to continue doing this? The new footer does so presently:

We can adjust the tablet background and shadow independently too. Note that at the moment the CSS is configured to do a consistent shadow all around tablet read more footer cards - looked weird with no top separator.

@cmadeo Also would prefer we use the same grey background for the footer as is used for the TOC background? Right now they're a bit different.

This screenshot shows how the color difference is apparent if you choose "Read more" from the TOC on tablet (even though on tablet the footer presently has a white background, the gray used as a background for the footer on phone still appears below the footer):

Per our meeting: lets make the footer change (move legal disclaimer, etc) minor visual changes (padding around cards) and postpone the bigger changes for a future iterations (horizontal interaction).

Regarding the single line description - on mobile web a single line is used.

You can see this in the screenshot below where I've overridden a description to be super long:

And here is the same super long description but with the single line CSS commented out:

Here's a ticket which switches back to vertical layout (per our decision to postpone horizontal interaction to future date/ticket):

https://phabricator.wikimedia.org/T164330

@cmadeo Hey I parked this back in "Needs Design" and split out a child ticket for switching to vertical layout.

Awesome, thanks @Mhurd!

Hiya – will certain elements (namely the icons and text) be customizable per platform?
Namely, the following elements are different in Android:

• Icons used for filled/unfilled bookmark
• Typography style for article title and description (Roboto font and sizes)
• Text-strings - for example 'Save for later' would be 'Add to reading list' in Android

Separately, are we able to localize the wordmark once assets from T143400: Improve the reading experience of footer sections of articles are finalized?

hi @Niedzielski – just updated T143400: Improve the reading experience of footer sections of articles for design specific to the Android footer which also has links to the article's Talk and History pages, as well as a link to 'View in browser'....

...unless these are links that iOS would also want to include as part of footer standardization?

@RHo, sorry for the late response and thanks for the good questions. I'm going to sync up with @Mhurd on this later today and will follow up with the Android footer integration ticket(s) I mentioned in the page library status update email.

@RHo, sorry for the late response and thanks for the good questions. I'm going to sync up with @Mhurd on this later today and will follow up with the Android footer integration ticket(s) I mentioned in the page library status update email.

sounds good @Niedzielski - and I wouldn't call <1day reply a late response! :)

@RHo

will certain elements (namely the icons and text) be customizable per platform?

Yes! We should be able customize the items you mentioned for Android:

• Icons used for filled/unfilled bookmark

The icon class should be overridable - @Niedzielski we can work out the details.

• Typography style for article title and description (Roboto font and sizes)

We should be able to override this as well for Android.

• Text-strings - for example 'Save for later' would be 'Add to reading list' in Android

This is also not a problem as the native code passes the transform these strings.

@RHo, this cat boss jpeg is the best. I've made a placeholder for the Android integration in T165439. The consolidation is still in progress so there should be plenty of time to work on any mocks or design specs.

@Mhurd, @JMinor, does this need to be estimated?

Moving this from Goat on a Train to the Wikipedia iOS App Backlog as the current implementation utilizes a smaller card presentation for 'Read more' articles, which was the primary design goal on iOS. In the future we may want to create a Universal footer design across Mobile web, Android and iOS, but for now this design is sufficient.