*tl;dr: We'll be stripping all content contained inside brackets from the
first sentence of articles in the Wikipedia app.*
The Mobile Apps Team is focussed on making the app a beautiful and engaging
reader experience, and trying to support use cases like wanting to look
something up quickly to find what it is. Unfortunately, there are several
aspects of Wikipedia at present that are actively detrimental to that goal.
One example of this are the lead sentences.
As mentioned in the other thread on this matter
lead sentences are poorly formatted and contain information that is
detrimental to quickly looking up a topic. The team did a quick audit
the information available inside brackets in the first sentences, and
typically it is pronunciation information which is probably better placed
in the infobox rather than breaking up the first sentence. The other
problem is that this information was typically inserted and previewed on a
platform where space is not at a premium, and that calculation is different
on mobile devices.
In order to better serve the quick lookup use case, the team has reached
the decision to strip anything inside brackets in the first sentence of
articles in the Wikipedia app.
Stripping content is not a decision to be made lightly. People took the
time to write it, and that should be respected. We realise this is
controversial. That said, it's the opinion of the team that the problem is
pretty clear: this content is not optimised for users quickly looking
things up on mobile devices at all, and will take a long time to solve
through alternative means. A quicker solution is required.
The screenshots below are mockups of the before and after of the change.
These are not final, I just put them together quickly to illustrate what
I'm talking about.
- Before: http://i.imgur.com/VwKerbv.jpg
- After: http://i.imgur.com/2A5PLmy.jpg
If you have any questions, let me know.
Associate Product Manager, Mobile Apps
As mentioned previously, the current version of the Android app contains an
A/B test where it presents "read more" suggestions to the user, based on
(a) the standard "morelike" query, or (b) the new "opening_text" query.
Here are the results from the last ~10 days of the test:
- The clickthrough rate using the default morelike query is (and has been)
- With the new opening_text query, the clickthrough rate decreases to about
[image: Inline image 1]
Therefore, it seems that the new query has a nontrivial negative effect on
We'll plan on removing this test in the next release of the app, but we'll
be happy to plug in a different or updated query, if it will be of further
use to Discovery.
(queries embedded as comments in the headers)
Senior Software Engineer / Product Owner (Android)
So, with mobile usage creeping up to and even exceeding desktop, I figured
I was overdue for switching over to the mobile skin, so I get to know it a
I think it looks very attractive and modern. But it is marred by a
usability issue so severe that it is borderline unusable to me, and that is
the manner in which the content jumps around as the page is loading.
The problem is that sections are initially loaded in an expanded state, and
This code also pulls in interface elements that are drawn quite late. Even
on a fast connection, a quick reader can be halfway through reading a
paragraph when all of a sudden the content suddenly and rudely shifts to
side or is revoked entirely.
The result is very dizzying and unpleasant. As a result, I find that I have
to train myself *not* to start reading the text in front of me until the
page has settled down.
I don't think that this is good performance. It may get something to render
sooner than it otherwise would have, but it ends up delaying the time it
takes for the page to settle into its fully-loaded layout, which forces the
user to wait longer (or tolerate the electric jolt of having the content
skip around mid-sentence).
Roan filed this as https://phabricator.wikimedia.org/T126825 . I set its
priority to "high", and I hope this e-mail gives some context as to why.
This is awesome. Now, let's make sure we are not running into throttling
limits. Could we get an estimate of the number of requests we expect from
Given that we have about 400.000 daily uniques in IOS daily we would expect
about 5 requests per second coming from the app IF traffic is widespread
through the day and app is doing 1 request per day. If traffic concentrates
in some hours request ratio might be higher
We would also like to double check that caching headers are respected in
the app and requests are not retried if they are mean to be cached. Can
developers confirm this is the case?
Both mobile apps and web are using CirrusSearch's morelike: feature which
is showing some performance issues on our end. We would like to make a
performance optimization to it, but before we would prefer to run an A/B
test to see if the results are still "about as good" as they are currently.
The optimization is basically: Currently more like this takes the entire
article into account, we would like to change this to take only the opening
text of an article into account. This should reduce the amount of work we
have to do on the backend saving both server load and latency the user sees
running the query.
This can be triggered by adding these two query parameters to the search
api request that is being performed:
The API will give a warning that these parameters do not exist, but they
are safe to ignore. Would any of you be willing to run this test? We would
basically want to look at user perceived latency along with click through
rates for the current default setup along with the restricted setup using
as far as I know the permission is in the custom build flavor only (it was moved from the main build channel to it in commit). I'm not sure, what flavor is used for fdroid, it's using the custom channel, it get's the permission (added in ).
Betreff: [WikimediaMobile] Android app now requires "run at startup" permission?
Von: "Legoktm" <legoktm.wikipedia(a)gmail.com>
An: "mobile-l" <mobile-l(a)lists.wikimedia.org>
When I upgrade from 2.1.137-fdroid to 2.1.141-fdroid (I fell a little
behind in staying up to date), the Android Wikipedia app requests the
"run at startup" permission. Is this intentional? Why does the app need
to run at startup?
Mobile-l mailing list