mazevedofs opened https://github.com/wikimedia/wikipedia-ios/pull/4884

@dcausse @MSantos

We are in the process of switching this over on iOS. I wanted to call out that our UI expects 20 results, so we are requesting that many. From what I can see Android requests 5. Will 20 results be a problem on the backend?

We will add the smaxage and maxage parameters as suggested in https://phabricator.wikimedia.org/T352801#9402209.

Thanks!

In T365595#9988219, @Tsevener wrote:

@dcausse @MSantos

We are in the process of switching this over on iOS. I wanted to call out that our UI expects 20 results, so we are requesting that many. From what I can see Android requests 5. Will 20 results be a problem on the backend?

No I don't think so since it should be pretty much the same api call you were using previously, note that if I not mistaken and assuming that /api/rest_v1/page/related was served by restbase the introduction of gsrqiprofile=classic_noboostlinks might slightly change the ordering of the results you were used to but should be consistent with what mobile web is doing.

@dcausse yep I did notice the change in ordering. That won't be a problem, thank you!

tonisevener closed https://github.com/wikimedia/wikipedia-ios/pull/4884

Can be tested starting in TestFlight 7.5.6 (3753).

Looks good to me on 7.5.6 (3760)

I'm not able to trigger the "Because you read" Recording in any language testing in 7.5.6 (3780), I may not be testing correctly

@HNordeenWMF yeah the logic is kinda difficult to reproduce. From what I can tell the related pages card should appear for any articles that you read for 30+ seconds, three days ago, or any article you saved three days ago. So you may need to change your device date to trigger the three days ago logic.

Working in English & Simplified Chinese! Thanks for the instructions @Tsevener