This uses ambox which currently is not displayed as it is on the web.

One possible solution: PCS checks for {{List has been split| and calls subsequent pages if found. It then stitches the pages together into one complete page to return to mobile clients.

In T255475#6269305, @MattCleinman wrote:

One possible solution: PCS checks for {{List has been split| and calls subsequent pages if found. It then stitches the pages together into one complete page to return to mobile clients.

Is that a desirable output from the design perspective? I would like to avoid this since the template has a performance purpose.

On the other hand, the reason why .ambox elements are not being displayed is because of the page issues extraction transform and CSS. Since we are already transforming these elements, it's straight forward to just flag the elements created by this template and apply different rules for it. But this is an edge case for an English Wikipedia specific template.

I'll let @cmadeo chime in with a more informed design perspective, but typically the "page 1 of x" concept isn't seen on mobile. More often you'd see progressive loading, where as the user scrolls down a page additional elements are continually loaded (in the background) and the user never reaches an arbitrary end of the list. (This, though, can have difficulty with the "find in page" feature.)

Sorry to jump in and be a bit dense, but is there anyway for us to display the box as a different template just on the apps?

While we could combine the split lists together, it feels more like the way these articles are built is by creating essentially 3 articles (Master article, part 1, part 2). I would also like to avoid pagination, but can see how a long list could be an issue for performance.

Another dense question, for these articles are the lists always formatted as tables?

It seems like this would be resolved by displaying the page issues as is requested in T248123. It's worth holding this until after T248123 is implemented to verify.

Thanks @cmadeo and @JoeWalsh for taking a look at this, I will move this to the backlog for now.