Fri, Apr 16
Wed, Apr 14
Tue, Apr 13
Thanks for reporting this -- we'll take a look and update our in-app guidance to match the rules on the wiki page.
I disagree that there's any ambiguity in that sentence. The number is the total pageviews of the contributions you've made in the last 30 days.
Thu, Apr 8
There are a couple of other cases to think about:
The Android client would be fine with the trivial solution, as well. We can easily make additional queries (as long as pagination works) to fill up the total amount that we need.
Wed, Apr 7
Adding a "Got it" button to the introductory tooltips within the Image Recommendations interface makes sense. But are we also talking about adding a Got It button to the tooltip that points to the Edits tab (i.e. the initial tooltip that teases the image training algorithm)? That would not make as much sense.
- When does the "Undo" affordance get shown? Is it directly after the user taps Yes/No/Not Sure?
- What if the user hits their daily goal at that moment, and is shown the big confetti screen? Is the Undo message shown on top of that?
- If they tap "Undo", does that take away from the daily goal? Is the confetti screen shown again if they re-submit after undoing?
Tue, Apr 6
I ended up implementing Variant C. I do believe it's more pleasing to the eye, and I agree it's better to show the image fully (not cropped).
This has been fixed in Beta for a while, and will go to production in the coming days.
this is done!
Mon, Apr 5
Note: This does not use the Monospace font. When using monospace fonts with italics, there are weird clipping issues (this is a known issue in the Framework). We can either (a) not use a monospace font, or (b) use monospace, but not italic.
(Note: As mentioned previously, it will not be possible to show the FAQ page in a private WebView. The user will be taken to their default browser app.)
Fri, Apr 2
Fri, Mar 26
@schoenbaechler I'm not seeing an asset for this screen in Zeplin.
Reopening this again, since we're still seeing a few similar reports from the Play Store.
Thu, Mar 25
Wed, Mar 24
Definitely agree about untangling "image source" from "suggestion source", and any of the proposed structures would work perfectly well for us, but I might actually lean towards @BPirkle's last suggested structure, which IMO is the most semantically accurate, i.e. putting source-specific details in the actual structure of the suggestion source.
Tue, Mar 23
May I ask what browser app(s) you have installed on your device? And also what Android version and device model you have?
Mon, Mar 22
This is now moot since we load non-main-namespace pages using Mobile Web.
Mar 17 2021
Mar 16 2021
Already fixed; sorry for the inconvenience!
@sdkim Yep, that looks good in the Wikipedia case. And if I understand correctly, if the image comes from the Wikidata entity, the source would be Wikidata? (with an empty or nonexistent found_on list?)
- The Edit history of an article so it’s less “detached” from the article reading experience?
Mar 12 2021
@schoenbaechler @JTannerWMF This is now done with code review. Please load the APK and see what you think of how non-article pages are loading now. Try searching for Category: pages, Portal: pages, and so on.
Mar 9 2021
@Srdjan The apps are using the following URL for getting the featured article: