Mobile-l

mobile-l@lists.wikimedia.org

3 participants
6883 discussions

[Apps] Android Wikipedia beta app release (2.0.111-beta-2015-09-16)
by Stephen Niedzielski 17 Sep '15

17 Sep '15

The Android team[0] is happy to announce a new Wikipedia Android app beta release, v2.0.111-beta-2015-09-16[1]. This revision contains the following fixes and enhancements[2]: * Improved image backgrounds in dark mode * Full roll out of link previews to all beta users! * Find in page UX improvements * Fixed link sharing on Gingerbread devices * Better heuristics for when link preview is shown * Miscellaneous minor UI tweaks and fixes * Several crash fixes Additionally, this revision is notable for being the final planned release supporting legacy devices[3]. Future releases will only be available on Android 4.0.3 (Ice Cream Sandwich MR1) and newer[4]. Today's release saw extra contributions from Dan Garry (Deskana). Thanks, Dan! You can help make it better too! Read our getting started guide[5]. We can't wait for your contributions! -The WMF Android team [0] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team#Android_App [1] Rolling out at https://play.google.com/store/apps/details?id=org.wikipedia.beta [2] A complete list of changes is available at http://git.wikimedia.org/commits/apps%2Fandroid%2Fwikipedia/beta%2F2.0.110-… [3] https://lists.wikimedia.org/pipermail/mobile-l/2015-August/009724.html [4] https://source.android.com/source/build-numbers.html [5] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_ha…

1 0

[Apps] New Android production release
by Dmitry Brant 11 Sep '15

11 Sep '15

Hi everyone, We're excited to present our latest update to the Wikipedia Android app[1][2], available now on the Google Play store! Here are the major highlights from this release: - Link previews: tapping on a link will now show you a quick "preview" that contains the first two sentences of the article, plus a swipeable gallery of image thumbnails from the article. This lets you get the gist of the link subject without losing your place in the article you were reading. You can tap on the image thumbnails to view them full-screen, or tap on the overflow menu (three dots) to save the article for later reading offline, or share it with other apps. And of course, you can easily continue to the linked article if you'd like to delve further into it. - More options when pressing-and-holding links: In addition to opening a link in a new tab, you can now save the linked article for offline reading, share the link to another app, or copy the link to the clipboard. And some further minor enhancements: - Better search result ordering - Improved handling and refreshing of saved pages - Improved screen rotation behavior - More Material Design components and styles - Share link to the current article from main overflow menu - Lots of bugs fixed and translations updated[3] Until next time, happy reading! Cheers, Dmitry Brant Product Owner (Android), Mobile Apps Team Wikimedia Foundation https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering [1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en [2] https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.… [3] https://phabricator.wikimedia.org/T112093

1 0

QA: Holding our code to better standards.
by Jon Robson 09 Sep '15

09 Sep '15

Dear Greg, and anyone else that is involved in deployment This is a follow-up from Dan Duvall's talk today during the metrics meeting about voting browser tests. Background: The reading web team this quarter with the help of Dan Duvall has made huge strides in our QA infrastructure. The extensions Gather, MobileFrontend and now the new extension QuickSurveys are all running browser tests on a per commit basis. A selected set of MobileFrontend @smoke tests (a selected subset of all he tests) are running in 15minutes on every commit and the entire set of Gather browser tests is running in around 21minutes. It marginally slows down getting patches deployed... but I think this is a good thing. The results speak for themselves. In the past month (August 4th-September 4th) only 3/33 builds failed for MobileFrontend's daily smoke test build [1] (all 3 due to issues with the Jenkins infrastructure). For the full set of tests only 10/33 failed in the Chrome daily build [3], 8 of which were due to tests being flakey and needing improvement or issues with the Jenkin infrastructure and the two others serious bugs [4,5] brought about by work the performance team had been doing that we were able to fix shortly after. In Firefox [2] there were only 6 failures and only 2 of these were serious bugs, again caused by things outside MobileFrontend [4,6]. One of these was pretty serious - we had started loading JavaScript for users with legacy browsers such as IE6. These were caught prior to the daily builds when suddenly our MobileFrontend commits would not merge. The future!: Given this success: 1) I would like to see us run @integration tests on core, but I understand given the number of bugs this might not be feasible so far. 2) We should run @integration tests prior to deployments to the cluster via the train and communicate out when we have failures (and make a decision to push broken code) 3) I'd like to see other extensions adopt browser test voting on their extensions. Please feel free to reach out to me if you need help with that. The more coverage across our extensions we have, the better. We really have no excuse going forward to push broken code out to our users and at the very least we need to be visible to each other when we are deploying broken code. We have a responsibility to our users. Thoughts? Reactions? Who's with me?! [1] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFro… [2] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFro… [3] https://integration.wikimedia.org/ci/view/Mobile/job/browsertests-MobileFro… [4] https://phabricator.wikimedia.org/T108045 [5] https://phabricator.wikimedia.org/T108191 [6] https://phabricator.wikimedia.org/T111233

3 3

[Web] Minor drop in some EventLogging data last week
by Sam Smith 09 Sep '15

09 Sep '15

Hey y'all, Yesterday (Monday, 7th) Alex Monk submitted and subsequently back-ported and deployed a fix for an annoying bug in the code that registers the EventLogging schemas in the MobileFrontend extension [0]. The bug resulted in browse and diff click events failing to log as associated schemas weren't registered. The patch that introduced the bug was merged on Tuesday, 25th August, which, I think, means that it'd have been deployed on Thursday, 3rd September – that's a long weekend's worth of data that we won't see again. Thanks to Alex for squashing the bug so diligently. –Sam [0] https://gerrit.wikimedia.org/r/#/c/236239/

3 3

Removing of MobileFrontends Login page code - long live core login page
by Florian Schmidt 04 Sep '15

04 Sep '15

Hello together, today I want to notice the members of this lthat that I've merged a (at least for me) very important change for MobileFrontend. By resolving task T74910, MobileFrontend now will use the mediawiki core login page instead of it's own implementation. That reduces code duplication and minimizes the cost of maintenance for MobileFrontend. On the other hand, extension developers now can customize the mobile and desktop login page on the same way. More information can be found in the task, the associated tasks and changes. Thanks to Jon for making this possible :) Best, Florian Gesendet mit meinem HTC

2 1

Breaking apart MobileFrontend's front and back ends
by Sam Smith 02 Sep '15

02 Sep '15

Hey all, I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin. Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally. My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly. My short-term goals are: * to *cover* the new extension in integration tests so that I can make structural changes * to get the unit tests passing without hitting the DB * to document the new extension thoroughly * to reduce the binding between the two extensions to exactly one call [2] * to get the extension deployed Cool? Cool! –Sam * Not a typo [0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions-MobileFrontend/blob/dd9e99e0…

4 3

[Apps] Android Wikipedia beta app release (2.0.110-beta-2015-08-31)
by Stephen Niedzielski 02 Sep '15

02 Sep '15

The Android team[0] is happy to announce a new Wikipedia Android app beta release, v2.0.110-beta-2015-08-31[1]. This revision contains the following fixes and enhancements: * Improved search result ordering! * About half a dozen crash fixes * Bug fix for unnecessarily downloading saved page images * Dismiss link preview when navigating to any page * Hide refresh and remove buttons when no saved pages exist * Autoscroll to URL fragment for redirected pages Make it better! Read our getting started guide[3]. We cannot wait for your contributions! -The WMF Android team [0] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team#Android_App [1] Rolling out at https://play.google.com/store/apps/details?id=org.wikipedia.beta [2] A complete list of changes is available at http://git.wikimedia.org/commits/apps%2Fandroid%2Fwikipedia/beta%2F2.0.109-… [3] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_ha…

5 7

Re: [WikimediaMobile] [Wikitech-l] "Try the free Wikipedia app" banners
by Matthew Flaschen 02 Sep '15

02 Sep '15

On 09/01/2015 11:30 AM, Ori Livneh wrote: > We appear to be running a banner campaign on the mobile web site, driving > people to download the mobile app: > > https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_2 > https://en.m.wikipedia.org/wiki/?banner=Aug2015_app_banner_1 > > Campaign definition: > https://meta.wikimedia.org/w/index.php?title=Special:CentralNotice&subactio… > > This isn't cool. This isn't us. We don't drive people from an open platform > to a closed one. I don't necessarily think it's a great idea to push people from web to apps either, especially when we also have people working on mobile web. I also do most of my mobile Wikipedia browsing on mobile web. That said, I think that assessment is overly critical. * The Android mobile app is fully free and open source (obvious, since all of our stuff is, but worth re-iterating). * They've done a great job on the app. In particular, they've implemented features that are easier on app (or only feasible there), like a user-friendly saved pages list and a nice UI in general. * I don't know this for sure, but I would guess the app works on fully-FOSS versions of Android (e.g. Replicant), since an updated version is in the fully-free app store (https://f-droid.org/wiki/page/org.wikipedia). If it doesn't work on Replicant (or some similar fully-FOSS Android), that does seem like something important to address. * No one is going to install proprietary software as a result of this ad. It only shows to people who are *already* running Android and asks them to install free and open source software. It's no different then recommending to a Windows user that they install Inkscape because it's a great piece of free and open source software. Finally, this is indeed only configured for Finland. Matt Flaschen

1 0

Re: [WikimediaMobile] Breaking apart MobileFrontend's front and back ends
by Florian Schmidt 01 Sep '15

01 Sep '15

> Cool? Cool! It would make the installation of MobileFrontned a lot easier for third parties (ok, I only talk about me :P), if this would be a composer module, but having it in it's own extension sounds reasonable nontheless! Best, Florian Gesendet mit meinem HTC ----- Nachricht beantworten ----- Von: "Sam Smith" <samsmith(a)wikimedia.org> An: "mobile-l" <mobile-l(a)lists.wikimedia.org> Betreff: [WikimediaMobile] Breaking apart MobileFrontend's front and back ends Datum: Di., Sep. 1, 2015 15:52 Hey all, I've been encouraged to write an update on a 1%* project that I've been working on: separating the HTML formatter and APIs from the Minerva skin. Right now, I've created a new extension, which contains the code, associated configuration variables, and unit/integration tests [0] and am running it alongside a cut down version of the MobileFrontend extension [1] locally. My long-term goal is to further separate out the HTML formatter into a versioned library and to version the API extension so that we can make smaller, more easily reasoned about changes to smaller, more easily reasoned about components and update the (relative) titan that is the MobileFrontend extension more responsibly. My short-term goals are: * to *cover* the new extension in integration tests so that I can make structural changes * to get the unit tests passing without hitting the DB * to document the new extension thoroughly * to reduce the binding between the two extensions to exactly one call [2] * to get the extension deployed Cool? Cool! –Sam * Not a typo [0] https://github.com/phuedx/MobileView [1] https://github.com/phuedx/mediawiki-extensions-MobileFrontend [2] https://github.com/phuedx/mediawiki-extensions-MobileFrontend/blob/dd9e99e0…

1 0

[Apps] Android Wikipedia legacy device active maintenance ending
by Stephen Niedzielski 01 Sep '15

01 Sep '15

The WMF Android App team will be ceasing active support for older devices soon, namely devices that run Android 4.0 (Ice Cream Sandwich) or older. Our final legacy device release is expected in mid to late September[0]. This release will remain available on the Google Play Store for devices running Android 2.3 (Gingerbread) through 4.0 (Ice Cream Sandwich). However, future releases will only target devices running Android 4.0.3 (Ice Cream Sandwich MR1) and higher. [1] * Why this is happening Devices running Android versions older than 4.0.3 make up less than 8%[2] of the Wikipedia for Android install base, and supporting older devices requires disproportionate developer time and effort. Focusing our efforts on the most recent and widely used versions will allow us to provide a faster, more stable, and more delightful Wikipedia experience. * What this means for older devices Enjoy a stable and beautiful legacy release for as long as you wish. When you're ready for a new device, a sleek and modern app awaits you. * What this means for all other devices Reap the benefits of a Wikipedia for Android experience built to take advantage of the latest and greatest Android technology available. -The Wikimedia Android team [0] This will be the final planned legacy device release. Allowances will be made to enable back support patches of critical issues. [1] https://source.android.com/source/build-numbers.html [2] Google Play Developer Console, Current Installs by Device on August 20, 2015.

5 9

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l