Hey Kunal,
Responses in-line.
On 3 February 2015 at 21:09, Legoktm legoktm.wikipedia@gmail.com wrote:
Is there a bug for this and the other issues? I'm subscribed to [1], but I don't see anything like the issues you've mentioned on it.
There's this, which documents some of them, but it's more descriptive of a specific proposed solution: https://phabricator.wikimedia.org/T87824
I welcome any other ideas that anyone has for solving our problems. We're not tied to a specific solution.
What are "read more recommendations"?
When you scroll to the end of an article, we give three suggestions as to what you could read next. The suggestions are generated quite naively by running a full text search using the current page's title as a query. Our metrics have shown a lot of positive engagement with the feature so far.
Here's a screenshot on [[Bern]]: http://i.imgur.com/qnHcsdT.png
Is there an actual instance where an API change has broken an app or is this merely a hypothetical concern? Speaking as an API developer, we occasionally have to make breaking changes, and if we broke something too fast, it would be nice to have feedback if that was the case so we can improve in the future.
I'm referring to a possible upcoming breaking change in MobileFrontend, which is the API we depend on for our content. A certain API parameter may be removed. Since the apps were made under the assumption that that value would always be in the API response, the app doesn't handle this issue well. It leaves users unable to see file pages.
This issue is particularly prominent on apps since if the user never updates the app then they'll never get the fix.
Dan