[WikimediaMobile] [Apps] In-App Notifications on Android

[Dmitry Brant]

Hi everyone,

The Android team has recently released watchlists, talk pages, and an image
recommendations experiment. To make sure we hear from editors we don't
normally hear from
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Communication/UsertestingJuly2021#Primary_feedback_audience>
in the software development process, and who might have needs and use cases
we miss, we also specifically reached out to a list of communities,
regions, and types of users.

We were fortunate enough to also get some feedback from Indonesian
Wikipedia editors, Arabic editors in Morocco, and an English Wikipedia
editor based in Nigeria. The outcomes of our respondents' qualitative
feedback
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/Communication/UsertestingJuly2021#Results>,
coupled with previous feedback from the community and members of staff,
along with an ABC test <https://phabricator.wikimedia.org/T290995> we are
finishing up, has resulted in us finalizing the changes we are making in
the app to ensure communication is not lost for our users.

Our most recent release
<https://play.google.com/store/apps/details?id=org.wikipedia> now ensures
users can see their notifications in-app no matter what screen they are on,
including while reading an article, something that was highly requested
<https://en.wikipedia.org/wiki/Wikipedia:Mobile_communication_bugs>.

 Before   After

As we wrap up our work on notifications, we will shift from ensuring every
user that edits on the Android app can clearly see the notifications and
alerts they've received to ensuring the workflows for sending a
communication are as intuitive as possible for mobile devices. We already
have native user and article talk pages in the app. We will now conduct
research to see what gaps exist for our users, and introduce new (to us)
concepts like quick reactions; please check out this demo
<https://www.youtube.com/watch?v=8-xQSCREGic> to see our ideas so far.

We hope you will engage with us and tell us any thoughts you have regarding
promoting communication in our movement through the use of our tools. We
also encourage you to send more users our way that meet the demographics we
requested for notifications.  Feel free to reach out to our team
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team>, or comment on our
team's communications project talk page
<https://www.mediawiki.org/wiki/Talk:Wikimedia_Apps/Team/Android/Communication>
.

PS: If you're an iOS user, they're also working on some great things
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS/Notifications#September_2021_update>
related to communications.


Cheers,

-- 
Dmitry Brant
Lead Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list -- mobile-l@lists.wikimedia.org
To unsubscribe send an email to mobile-l-le...@lists.wikimedia.org

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're excited to present our latest release of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia>, available
now on the Google Play Store (or as a standalone download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.7.50341-r-2021-02-02.apk>
for devices without Google). Here are the major highlights from this update:

* *Watchlists*: Your watchlist is now accessible from the main screen when
you are logged in. Tap the "More" menu at the bottom and select
"Watchlist."  If you have multiple languages selected in the app, the
Watchlist screen will merge your watchlists from those language wikis. You
can also choose which languages to show by tapping the language icon in the
toolbar at the top.  Tap any of the items in your watchlist to see a
detailed diff screen for the selected change.  And of course, to add any
article you're currently reading to your watchlist, tap the top-right menu
in the toolbar, and select "Add to watchlist."

* *Talk pages*: Article talk pages and User talk pages are now presented
natively.  When reading an article, the corresponding talk page is
accessible by scrolling to the bottom and selecting "View talk page."  User
talk pages can be accessed from various places where user interactions
might occur, including your watchlist, various push notifications (e.g.
messages left by other users on your talk page), and other users' and
article talk pages.

In addition to these major updates, this release has plenty of bug fixes,
design refinements, and performance optimizations. Check it out, and as
always, we welcome your feedback!

*Special note*: This release is dedicated to the memory of our late
colleague and friend Bernd Sitzmann, a brilliant developer and a wonderful
person, without whom the app wouldn't be what it is today. He will be
missed.


Cheers,

-- 
Dmitry Brant
Lead Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Read more 3 articles

[Dmitry Brant]

Hi Patrick,

Thanks for contacting us! We'll pass your feedback on to our designers and
developers. This can now be tracked in our issue tracking system:
https://phabricator.wikimedia.org/T253759


Best,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering

On Wed, May 27, 2020 at 10:36 AM Patrick Fiset 
wrote:

>
> Hello
> I'm unsure if my messages are being delivered. Can someone confirm?
>
> It's about the truncation of the description ("...").  It would be better
> to not have these truncated, lile before.
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hey everyone,

We're excited to release our latest update to the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store. Aside from numerous minor enhancements
and bug fixes, the biggest highlight from this update is:

== *Suggested edits, the continuation ==*
Earlier this year we released the "Suggested edits" screen (accessible from
the left navigation menu in the Feed screen, when you're logged in) which
offers you a stream of suggested contributions. Initially these
contributions were limited to adding and translating Wikidata descriptions
for articles that were missing a description.

We have now expanded these suggested contributions to include adding and
translating structured image captions on Commons!  The Suggested Edits
screen now presents you with images that are missing a structured caption,
or if you have more than one language configured in the app, it shows you
images that are missing translations of the caption into the other
language(s) that you have selected.

You may also add or translate the captions of images directly while
browsing articles. Tap on any image to go to the full-screen gallery, and
you should see options to add, edit, or translate the caption.

Check it out, and we'd love to hear your feedback.
Cheers,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're pleased to release our latest update to the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store.
We may have missed a release email to this list for our previous minor
release, so here is a cumulative list of highlights since our last update:

* *Suggested edits*: The app now has a screen (accessible from the left
navigation menu) that offers suggestions for items to edit. For this
initial release, this is limited to adding and translating Wikidata
descriptions.  In future updates, this will be expanded to suggest other
types of edits.

Note that this feature must be "unlocked" to be accessible: you'll need to
add or edit at least five (5) Wikidata descriptions in the usual way (using
the edit icon while reading an article), then wait a while to make sure
your edits are not reverted. The app will then notify you when the feature
is unlocked.

* *Improved editing interface*: The article editing screen has a number of
new conveniences, including the ability to change the font size of the
wikitext window, the ability to find text within the wikitext window, and a
series of "syntax" buttons at the bottom, to simplify adding or modifying
the wikitext syntax at the cursor, as well as "undo" and "redo" buttons.

* *Sepia theme*: As usual, you can change the app's theme in Settings, or
from the bottom toolbar while reading an article.

* *"Continue reading" bar*: When browsing the Feed, or looking at your
reading lists, you will now see a "continue reading" bar at the bottom that
displays your current topmost tab, along with the total number of open tabs
you currently have.

* *Enhanced table of contents control*: The table of contents now features
a circular "thumb" scroller that you can hold down and drag to scroll
quickly through different sections of the article, while highlighting the
section that is currently in focus.

* *Improved search in reading lists*: Searching within the Reading Lists
screen will now match results from individual articles in any of your
reading lists, as well as the names of reading lists themselves.


Check it out, and happy reading (and editing)!
Cheers,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

 Hi everyone,

We've released our latest update to the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store. (For devices without Google Play
services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.7.237-r-2018-06-27-universal.apk>
 the app directly)
Here are the highlights from this update:

* *Multi-language support*: you may now select multiple languages
simultaneously to be your preferred languages in the app.
** When searching for a term within the app, you can easily switch between
preferred languages to see results in that language.
** The Explore feed now shows content in all of your preferred languages.
Customization of the feed has been expanded to include per-language
preferences for each type of feed content.
** When first installing the app, it automatically detects your languages
based on your system settings and keyboard locales.

* Per-platform app packages: when downloading or updating the app from the
Play Store, it will download an APK specifically tailored to your device's
platform. This reduces the download size from ~24MB to about ~*10MB*.

* Added a preference in Settings to restrict downloading reading list
articles only when on Wi-Fi, to conserve mobile data usage.

* A whole lot of miscellaneous bug fixes to improve stability and
performance (full change log
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;r/2.7.237-r-2018-06-27>
).


Cheers,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

 Hi everyone,

We've released our latest update to the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store. (For devices without Google Play
services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.7.234-r-2018-05-30.apk>
 the app directly)

This is a maintenance update that addresses a few minor issues and bugs:

* Respect the new {{shortdescription}} template in articles (no longer
offer to edit the Wikidata description if a local article description is
present).
* Fix possible latency issues due to incorrect cookie handling.
* Fix possible errors when synchronizing reading lists (when adding
articles from external deep links).


Cheers,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're pleased to announce our latest update to the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store! (For devices without Google Play
services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.7.232-r-2018-04-17.apk>
the app directly)

The major highlight from this update is:  *synchronized reading lists*!
Articles that you add (or have already added) to your reading lists can now
be synchronized to your Wikipedia account, so that your reading list
collection will always be available on any device on which you use the app,
whether it's an Android or iOS device (<- separate announcement
forthcoming).

You should see a prompt to enable syncing when you install or upgrade the
app, or you may enable/disable the sync feature in the app settings.

As a reminder, articles that you add to reading lists are also saved for
offline reading by default, so that you can access them even without
internet connectivity.  You may also control which lists are saved offline
by going to the "My lists" tab and tapping the overflow menu (three dots)
next to each list.

Cheers, and happy reading!

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

 Hi everyone,

We've released an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store! (For devices without Google Play
services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.7.225-releasesprod-2018-02-06.apk>
 the app directly)

This is a relatively minor update that focuses on performance improvements
in the Reading Lists feature, especially with very large numbers of
articles in reading lists.

We're also introducing the idea of a "default" reading list, created
automatically, allowing you to save articles with fewer taps, while
retaining the option to create and organize other lists as before.


Cheers,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play store [1]!  Here are the highlights from this
release (or browse the complete change history
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;r/2.7.221-r-2017-12-08>
):

- The Explore feed is now fully customizable! Access the customization
screen from the overflow menu in the feed or in each card, and make the
feed your own: enable or disable the types of cards you want to see, and
rearrange the order in which they are shown.

- New and improved Randomizer: tap the Randomizer card in the Explore feed,
and swipe through random article previews from Wikipedia, without
navigating to the full article right away. Try it out!

- On This Day: the Explore feed now contains cards with a selected
historical event that happened on the current day of the year. Tap the card
to see a full-screen view of all events from history that occurred on this
day.

- Black theme: we've heard your feedback, and added a black theme in
addition to the current light and dark themes. Perfect for AMOLED displays
and nighttime reading, this provides a fully black background throughout
most of the app.

- Plenty of minor enhancements and bug fixes.


[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.7.221-releasesprod-2017-12-08.apk>
 the app directly.

Cheers,

-- 
Dmitry Brant
Senior Software Engineer (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Android] New Beta release

[Dmitry Brant]

Hi everyone,

The Android team has released a new version of the Wikipedia Beta
<https://play.google.com/store/apps/details?id=org.wikipedia.beta> app,
available now on the Google Play Store! Here are the highlights from this
update:

- New: app shortcuts ("Search", "Random", and "Continue reading"). Press
and hold the app icon on your home screen to access these shortcuts, and
even place the shortcuts themselves on your home screen.
- Improved speed of loading larger articles.
- Optionally dim images when using dark theme. Access this option in the
app settings, or in the Font and Theme dialog when reading an article.
- Streamlined designs and color scheme in Light and Dark mode.
- Improved management of reading lists.
- Fixed several issues with language variants, specifically with
Traditional and Simplified Chinese.
- Numerous additional bug fixes.

This release also contains patches from these repeat contributors:
- Jorge Casariego, IRC: Jcasariego, Github:
https://github.com/jorgecasariego
- Yashasvi, https://about.me/yashasvigirdhar

*Important note*:
We are planning for this release to be the last update that supports
versions of Android older than KitKat (that is, Android Jelly Bean and
below).  After this update, users of Jelly Bean and below will still be
able to install our app from the Play Store, but it will be frozen at this
version, and will no longer receive updates.


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>, now
available on the Google Play Store! [1]. Here are the highlights from this
update (or browse the complete change history
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.6.201-beta-2017-08-10>
):

- New: lazy-loading of images! When browsing articles, images will be
loaded only when they are scrolled into view.
- Improvements and fixes for saving and managing offline reading list
articles.
- The dark theme can now be enabled from the app settings, as well as from
the article overflow menu.
- Improved dark mode color scheme.
- Minor design enhancements throughout.
- Numerous bug fixes.

Special thanks to the volunteer contributors who submitted patches for this
release:

- Jorge Casariego, (IRC: Jcasariego, Github:
https://github.com/jorgecasariego)
- Yashasvi, (https://about.me/yashasvigirdhar)
- Florian Schmidt, (IRC: FlorianSW, GitHub: https://github.com/FlorianSW)
- Amir Aharoni (IRC: aharoni, Wikipedia User:Amire80)
- Kaartic Sivaraam (GitHub: https://github.com/sivaraam)

If you'd like to help improve the app yourself, take a look at our getting
started
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>
guide.
We're looking forward to your contributions!


[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.6.201-releasesprod-2017-08-10.apk>
 the app directly.

Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android Beta release

[Dmitry Brant]

Hello!

The Wikipedia Android team is pleased to announce a new Beta release of our
Android app[1]. Here are the highlights from this update (or see the
complete list of changes[2]):

- Significant improvements to offline storage and availability of reading
lists and pages
- Design enhancements for management of reading lists
- Reading lists now show total storage space used by saved pages
- Improved management of browsing history (swipe to delete items, with undo)
- Enhanced design and behavior of multiple features when offline
- Numerous miscellaneous bug fixes

Many thanks to our volunteers who contributed patches to this release,
including:

- Jorge Casariego, IRC: Jcasariego, Github:
https://github.com/jorgecasariego
- Florian Schmidt, IRC: FlorianSW, GitHub: https://github.com/FlorianSW
- Hamadi Krimo, Twitter: https://twitter.com/krimokrimo007

You too can help make it better! Read our getting started guide[3]. We look
forward to your contributions!

[1] https://play.google.com/store/apps/details?id=org.wikipedia.beta
[2]
https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.6.197-beta-2017-06-08
[3] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/
Wikipedia_Android_app_hacking


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

I should add to the list of new features:
- We're now continuing our rollout of editing Wikidata descriptions by
expanding the languages for which descriptions can be added/edited. For
more details, please see the announcement
<https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2017/04#Wikidata_description_editing_in_the_Wikipedia_Android_app>
on Wikidata.


Cheers!

On Mon, Apr 24, 2017 at 4:48 PM, Dmitry Brant  wrote:

> Hello!
>
> We're pleased to bring you an updated version of the Wikipedia Android
> app, available now on the Google Play Store! [1]. Here are the highlights
> from this update (or browse the complete change history
> <https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.5.195-beta-2017-04-21>
> ):
>
> - Numerous improvements to the UI for managing your reading lists.
> - Individual reading list articles can now be toggled on/offline.
> - Improved caching of images for offline availability.
> - Random feed card now pulls a random article from the user's reading
> lists when offline.
> - Many other bug fixes and design updates.
>
> Many thanks to our volunteers who contributed patches to this release,
> including Amir Aharoni (IRC: aharoni, Wikipedia User:Amire80), Codrut Grosu
> (Github: superCodrut, Twitter: @GrosuCodrut), and Dinu Kumarasiri (IRC:
> sandaru, Github: sandarumk).
>
> If you'd like to help improve the app yourself, take a look at our getting
> started
> <https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/App_hacking>
> guide. We're looking forward to your contributions!
>
>
> [1] For devices without Google Play services, you may download
> <https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.5.195-releasesprod-2017-04-21.apk>
> the app directly.
>
> Cheers,
>
> --
> Dmitry Brant
> Senior Software Engineer / Product Owner (Android)
> Wikimedia Foundation
> https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
>
>


-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hello!

We're pleased to bring you an updated version of the Wikipedia Android app,
available now on the Google Play Store! [1]. Here are the highlights from
this update (or browse the complete change history
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.5.195-beta-2017-04-21>
):

- Numerous improvements to the UI for managing your reading lists.
- Individual reading list articles can now be toggled on/offline.
- Improved caching of images for offline availability.
- Random feed card now pulls a random article from the user's reading lists
when offline.
- Many other bug fixes and design updates.

Many thanks to our volunteers who contributed patches to this release,
including Amir Aharoni (IRC: aharoni, Wikipedia User:Amire80), Codrut Grosu
(Github: superCodrut, Twitter: @GrosuCodrut), and Dinu Kumarasiri (IRC:
sandaru, Github: sandarumk).

If you'd like to help improve the app yourself, take a look at our getting
started
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Android/App_hacking>
guide. We're looking forward to your contributions!


[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.5.195-releasesprod-2017-04-21.apk>
the app directly.

Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>,
rolling out now to the Google Play Store! [1]. Here are the highlights from
this update (or browse the complete change history
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;r/2.5.190-r-2017-02-24>
):

- Contribute to Wikipedia by editing title descriptions for articles that
you browse! (Powered by Wikidata, and currently limited to Russian, Hebrew,
and Catalan Wikipedia. More languages will follow, once we analyze
engagement data with this initial group of communities. If you're
interested, here is the original project outline
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Short_descriptions>, and the
rollout announcement
<https://www.wikidata.org/wiki/Wikidata:Project_chat#Wikidata_description_editing_in_the_Wikipedia_Android_app>
)

- Support for two-factor authentication when logging in.
- Improved multi-window support for Samsung devices and for Android Nougat.
- Improved network performance and offline support for cached page previews.
- Minor UI refinements to image gallery, link previews, and reading lists.
- Changing the wiki language now also changes the app UI language.
- Numerous bug and crash fixes.

Special thanks to the volunteer contributors who submitted patches for this
release:

The Discoverer - [[mw:User:The Discoverer]]
Dinu Kumarasiri - IRC: sandaru, https://github.com/sandarumk
Odysseas Kristalakos - https://github.com/OdysseasKr
Kunal Grover - https://github.com/kunalgrover05

If you'd like to help improve the app yourself, take a look at our getting
started
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>
guide.
We're looking forward to your contributions!


[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.5.190-releasesprod-2017-02-24.apk>
the
app directly.

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>,
rolling out now to the Google Play Store! [1]. Here are the highlights from
this update (or browse the complete change history
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;r/2.4.183-r-2016-12-08>
):

- Full support for Android 7 (Nougat).
- Support for announcements in the Explore feed.
- Improved system notifications for Wikipedia Zero.
- Home screen widgets are now resizable.
- Improved animations when dismissing/restoring cards in the feed.
- Internal overhaul of network functions for improved performance.
- Numerous fixes for bugs and crashes.

Please note that as of this release, we will no longer provide updates for
Android 4.0 (Ice Cream Sandwich) and below, and will only support Android
4.1 (Jelly Bean) and higher.

Special thanks to the volunteer contributors who submitted patches for this
release:

Amir Aharoni (IRC: aharoni, Wikipedia User:Amire80)
Anirudh S (https://github.com/anirudh24seven)
Himanshu Lakhara (https://plus.google.com/+HimanshuLakhara)
Kunal Grover (https://github.com/kunalgrover05)
Odysseas Kristalakos (https://github.com/OdysseasKr)

If you'd like to help improve the app yourself, take a look at our getting
started
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>
guide.
We're looking forward to your contributions!

[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.4.183-releasesprod-2016-12-08.apk>
the
app directly.


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] Android Wikipedia beta app release (2.4.181-beta-2016-12-05)

[Dmitry Brant]

Hi all,

We're pleased to announce a new Beta version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia.beta>. Here
are the highlights from this update (or browse the complete change history
<https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.4.181-beta-2016-12-05>
):

- Full support for Android 7 (Nougat).
- Support for announcements in the Explore feed.
- Improved system notifications for Wikipedia Zero.
- Home screen widgets are now resizable.
- Internal overhaul of network functions for improved performance.
- Numerous fixes for bugs and crashes.

Please note that as of this release, we will no longer provide updates for
Android 4.0 (Ice Cream Sandwich) and below, and will only support Android
4.1 (Jelly Bean) and higher.

Special thanks to the volunteer contributors who submitted patches for this
release:

Amir Aharoni (IRC: aharoni, Wikipedia User:Amire80)
Anirudh S (https://github.com/anirudh24seven)
Kunal Grover (https://github.com/kunalgrover05)
Odysseas Kristalakos (https://github.com/OdysseasKr)

If you'd like to help improve the app yourself, take a look at our getting
started
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>
guide. We're looking forward to your contributions!

Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>,
rolling out now to the Google Play Store! [1]

This version contains the following updates:
- Access your favorite features more easily with bottom navigation: quickly
jump between the Explore feed, your reading lists, your recently-viewed
articles, and pages nearby you.
- When reading an article, the bottom toolbar now provides access to the
most popular actions (save to reading list, share, change language, find in
page, and table of contents).
- Reading lists and their contents are now searchable.
- A number of minor bug and crash fixes.

Want to help make the app even better? Read our getting-started
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>
guide, and start contributing!

[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.4.157-releasesprod-2016-09-28.apk>
the app directly.


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>,
rolling out now to the Google Play Store! [1]

This version contains the following updates:
- Added a button at the top of the Explore feed for quick access to your
list of open tabs.
- The Tabs button now shows the number of active tabs that you've opened.
- Cards dismissed from the Explore feed (swiped away) are now correctly
remembered when refreshing the feed or reloading the app.
- Miscellaneous bug fixes.

Want to help make the app even better? Read our getting-started guide
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>,
and start contributing!

[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.3.152-releasesprod-2016-08-18.apk>
the
app directly.


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're excited to bring you an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>,
rolling out now to the Google Play store! [1]

In this update, we're introducing the Explore feed: a new way to discover
Wikipedia content! We've redesigned the home screen of the app, which now
shows a feed of featured content from Wikipedia, as well as personalized
reading suggestions based on your reading history in the app[2]. See
Wikipedia articles about current events, today's trending articles, today's
featured article and featured picture from Commons, and more. Please see
today's blog post
<https://blog.wikimedia.org/2016/07/28/wikipedia-android-redesign/> for
more information.

Want to help make the app even better? Read our getting-started guide
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>,
and start contributing!

[1] For devices without Google Play services, you may download
<https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.3.150-releasesprod-2016-07-25.apk>
the app directly.
[2] Note: your reading history is only stored locally on your device.


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Android Wikipedia beta app release (2.3.148-beta-2016-07-18)

[Dmitry Brant]

Hi Orsolya,

Thanks for the feedback; we're glad you're enjoying it!
To change the language of the content in the feed, tap the Search bar, then
tap the language selector in the top right corner (this sets the language
for all the features in the app).
After you change the language, go back to the feed and refresh it by
swiping down. You should now see trending articles for the newly selected
language wiki.



On Tue, Jul 26, 2016 at 4:29 PM, Orsolya Gyenes <
gyenes.orso...@wiki.media.hu> wrote:

> WOW!
>
> You guys deserve a BIG applaud, this is definitely amazing!
>
> We've been waiting for something like this for so long!
>
> I love it, especially the Trending feed.
>
> I'm wondering if there's a possibility to change language on Trending? I
> see our results of hu.wiki but I'd like to know what's trending on other
> wikis?
>
> Thank you very much for your hard work!
>
> 🙋🍸💯🎉
>
> *~Orsolya*
>
> 2016-07-19 0:02 GMT+02:00 Stephen Niedzielski 
> :
>
>> Introducing the Explore Feed: a new way to discover Wikipedia content!
>>
>> We've redesigned the home screen of the app, which now shows a feed of
>> featured content from Wikipedia, as well as personalized reading
>> suggestions based on your reading history in the app[0]. See Wikipedia
>> articles about current events, today's trending articles, today's featured
>> article and featured picture from Commons, and more[1]. Scroll down in the
>> feed to see featured content from previous days.
>>
>> Since this is a significant departure from the previous experience in the
>> app, we especially welcome the feedback of our Beta users. Let us know if
>> you see any issues or bugs, or if you have any suggestions for making it
>> even better.
>>
>> This version includes a volunteer contribution from repeat contributor
>> Amir Aharoni[2]. Good work! You too can help make it better! Read our
>> getting started guide[3]. We can't wait for your contributions!
>>
>>
>> -The WMF Android team
>>
>> [0] Note: your reading history is only stored locally on your device.
>> [1] "In the news" and "Today's featured article" are currently limited to
>> English Wikipedia only.
>> [2] Wikipedia User:Amire80, IRC and Twitter: aharoni
>> [3]
>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "android" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android+unsubscr...@wikimedia.org.
> To post to this group, send email to andr...@wikimedia.org.
>



-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We've just released an updated version of the Wikipedia Android app[1][2],
rolling out now to the Google Play store! Here are the highlights from this
update:

* Reading Lists can now be sorted by name or last-read.
* Added tip for how to remove articles from reading lists.
* Minor UI tweak to search results.
* Added talk link to bottom of articles (will open in external browser).
* Several miscellaneous crash fixes.

Want to help make the app even better? Read our getting-started guide[3],
and start contributing!

[1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
[2]
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.2.147-releasesprod-2016-06-06.apk
[3]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking


Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hello!

We've just released an updated version of the Wikipedia Android app
<https://play.google.com/store/apps/details?id=org.wikipedia&hl=en>,
rolling out as we speak to the Google Play store! Here are the highlights
from this update:

* Reading Lists: In place of the old "Saved Pages", you can now organize
the articles you browse into reading lists, which you can access even when
you're offline. Create as many lists as you like, give them custom names,
and populate them with articles from any language wiki!
* "Edit here": Press and hold to highlight a word while reading an article,
and select the "edit here" button to start editing at the highlighted
location.
* Show redirect source in search results, if applicable.
* Update login authentication to work with the latest server changes.
* Improved Wikipedia Zero banner design and persistence.
* No longer download and widen high-quality images when on a metered
connection.
* Numerous crash and bug fixes.

Thanks to the following contributors for their patches: Michael Basil
<https://github.com/intrications>, Elad Keyshawn
<https://twitter.com/EladKeyshawn>, maroloccio
<https://twitter.com/maroloccio>, and Deskana
<https://twitter.com/danjgarry>.
Want to help make the app even better? Read our getting-started guide
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking>,
and start contributing!

Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Android Wikipedia beta app release (2.2.146-beta-2016-05-23)

[Dmitry Brant]

In the long term, absolutely. Currently, we're continuing to brainstorm
different mobile contribution models that don't necessarily involve a
full-blown editing interface, which isn't well-suited for a mobile screen.



On Fri, May 27, 2016 at 2:53 PM, Pine W  wrote:

> Ok, thank you.
>
> By the way, shifting the subject a bit to longer term plans, are there any
> plans to make the apps (both Android and iPhone) be more suitable for
> editing content?
>
> Pine
> On May 27, 2016 07:06, "Dmitry Brant"  wrote:
>
>> Hi Pine,
>>
>> To be clear, prior to this change, the app widened images in all cases
>> (regardless of connection quality).  With this change, knowing that a
>> cellular connection is much more likely to be metered, this will benefit at
>> least those users.
>>
>> There's no manual setting to enable/disable image widening, but the user
>> may still enable/disable images entirely (in Settings) if there are data
>> cost concerns on whatever network they currently are.
>>
>>
>> On Thu, May 26, 2016 at 8:17 PM, Pine W  wrote:
>>
>>> Hi Michael,
>>>
>>> Ok, after exploring this further I think that my question about
>>> isActiveNetworkMetered() might be complicated enough that I should ask it
>>> of Google. (: As you probably know, some wifi networks can be slow and/or
>>> have a pay-per-unit fee or cap, while some cellular connections can include
>>> "unlimited" data.
>>>
>>> Is there a way that a user can manually select whether to enable or
>>> disable "force downloading and widening HQ images when on a metered
>>> connection" in the Wikipedia app for Android?
>>>
>>> Thanks,
>>> Pine
>>>
>>> On Tue, May 24, 2016 at 10:42 AM, Michael Holloway <
>>> mhollo...@wikimedia.org> wrote:
>>>
>>>> Hi Pine,
>>>>
>>>> I followed the Android docs[1] in using the term "metered connection"
>>>> in the release notes, but in concrete terms, your connection is considered
>>>> "metered" if you're on a cellular (as opposed to wi-fi) network.[2]
>>>>
>>>> Regards,
>>>> Michael
>>>>
>>>> [1]
>>>> https://developer.android.com/reference/android/support/v4/net/ConnectivityManagerCompat.html#isActiveNetworkMetered(android.net.ConnectivityManager)
>>>> [2]
>>>> https://android.googlesource.com/platform/frameworks/support/+/refs/heads/master/v4/java/android/support/v4/net/ConnectivityManagerCompat.java#37
>>>>
>>>> On Tue, May 24, 2016 at 1:11 PM, Pine W  wrote:
>>>>
>>>>> Hi Stephen,
>>>>>
>>>>> > No longer force downloading and widening HQ images when on a metered
>>>>> connection.
>>>>>
>>>>> Thank you. May I ask how the app knows if the device is using a
>>>>> metered connection at any given point in time?
>>>>>
>>>>> Pine
>>>>> On May 24, 2016 09:37, "Stephen Niedzielski" <
>>>>> sniedziel...@wikimedia.org> wrote:
>>>>>
>>>>>> The Android team[0] is pleased to announce a new Wikipedia Android app
>>>>>> beta release, v2.2.146-beta-2016-05-23[1]. This revision contains the
>>>>>> following new fixes and functionality[2]:
>>>>>>
>>>>>> * Introducing Reading Lists: In place of the old "Saved Pages", you
>>>>>> can
>>>>>>   now organize the articles you browse into reading lists, which you
>>>>>> can
>>>>>>   access even when you're offline. Create as many lists as you like,
>>>>>>   give them custom names, and populate them with articles from any
>>>>>>   language wiki!
>>>>>> * Update authentication to work with the latest server changes.
>>>>>> * Add "edit here" to the long press menu.
>>>>>> * Check Wikipedia Zero status on page load instead of on network state
>>>>>>   change.
>>>>>> * Improved Wikipedia Zero banner design.
>>>>>> * No longer force downloading and widening HQ images when on a metered
>>>>>>   connection.
>>>>>> * Numerous crash and bug fixes.
>>>>>>
>>>>>> Included in this version are patches from

Re: [WikimediaMobile] [Apps] Android Wikipedia beta app release (2.2.146-beta-2016-05-23)

[Dmitry Brant]

Hi Pine,

To be clear, prior to this change, the app widened images in all cases
(regardless of connection quality).  With this change, knowing that a
cellular connection is much more likely to be metered, this will benefit at
least those users.

There's no manual setting to enable/disable image widening, but the user
may still enable/disable images entirely (in Settings) if there are data
cost concerns on whatever network they currently are.


On Thu, May 26, 2016 at 8:17 PM, Pine W  wrote:

> Hi Michael,
>
> Ok, after exploring this further I think that my question about
> isActiveNetworkMetered() might be complicated enough that I should ask it
> of Google. (: As you probably know, some wifi networks can be slow and/or
> have a pay-per-unit fee or cap, while some cellular connections can include
> "unlimited" data.
>
> Is there a way that a user can manually select whether to enable or
> disable "force downloading and widening HQ images when on a metered
> connection" in the Wikipedia app for Android?
>
> Thanks,
> Pine
>
> On Tue, May 24, 2016 at 10:42 AM, Michael Holloway <
> mhollo...@wikimedia.org> wrote:
>
>> Hi Pine,
>>
>> I followed the Android docs[1] in using the term "metered connection" in
>> the release notes, but in concrete terms, your connection is considered
>> "metered" if you're on a cellular (as opposed to wi-fi) network.[2]
>>
>> Regards,
>> Michael
>>
>> [1]
>> https://developer.android.com/reference/android/support/v4/net/ConnectivityManagerCompat.html#isActiveNetworkMetered(android.net.ConnectivityManager)
>> [2]
>> https://android.googlesource.com/platform/frameworks/support/+/refs/heads/master/v4/java/android/support/v4/net/ConnectivityManagerCompat.java#37
>>
>> On Tue, May 24, 2016 at 1:11 PM, Pine W  wrote:
>>
>>> Hi Stephen,
>>>
>>> > No longer force downloading and widening HQ images when on a metered
>>> connection.
>>>
>>> Thank you. May I ask how the app knows if the device is using a metered
>>> connection at any given point in time?
>>>
>>> Pine
>>> On May 24, 2016 09:37, "Stephen Niedzielski" 
>>> wrote:
>>>
>>>> The Android team[0] is pleased to announce a new Wikipedia Android app
>>>> beta release, v2.2.146-beta-2016-05-23[1]. This revision contains the
>>>> following new fixes and functionality[2]:
>>>>
>>>> * Introducing Reading Lists: In place of the old "Saved Pages", you can
>>>>   now organize the articles you browse into reading lists, which you can
>>>>   access even when you're offline. Create as many lists as you like,
>>>>   give them custom names, and populate them with articles from any
>>>>   language wiki!
>>>> * Update authentication to work with the latest server changes.
>>>> * Add "edit here" to the long press menu.
>>>> * Check Wikipedia Zero status on page load instead of on network state
>>>>   change.
>>>> * Improved Wikipedia Zero banner design.
>>>> * No longer force downloading and widening HQ images when on a metered
>>>>   connection.
>>>> * Numerous crash and bug fixes.
>>>>
>>>> Included in this version are patches from first time contributors,
>>>> Michael Basil[3] and Elad Keyshawn[4], and repeat contributors,
>>>> maroloccio[5] and Dan Garry[6]. Nice work, devs!
>>>>
>>>> You too can help make it better! Read our getting started guide[7]. 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
>>>> https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.2.146-beta-2016-05-23
>>>> [3] https://github.com/intrications
>>>> [4] https://twitter.com/EladKeyshawn
>>>> [5] IRC: maroloccio, https://twitter.com/maroloccio
>>>> [6] IRC: Deskana, https://twitter.com/danjgarry
>>>> [7]
>>>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
>>>>
>>>> ___
>>>> Mobile-l mailing list
>>>> Mobile-l@lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>>
>>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We've just released a high-priority maintenance update to the production
version of our Android app[0].
This fixes some issues that numerous users have reported in the last couple
days regarding being unable to login or save edits[1]. This also makes sure
that the "Define" button that shows the Wiktionary definition of a
highlighted word is enabled for all users (on enwiki).

Sorry for any inconvenience!


[0] Rolling out at
https://play.google.com/store/apps/details?id=org.wikipedia
[1] We think it has to do with our networking library not playing nicely
with the version of nginx currently on our servers when using HTTP/2, so
we've disabled HTTP/2 in the app until this is resolved in the library (
https://gerrit.wikimedia.org/r/287675)

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] New features in the Android app enabled by Mobile Content Service

[Dmitry Brant]

Hi everyone,

In the last few weeks, we've been rolling out the ability of our Android
app to connect to the Mobile Content Service[0], built on RESTBase[1], for
retrieving article content, and the rollout is now complete.  Over the
course of the next day or so, the app installed on your device should
seamlessly switch over to using MCS instead of the MediaWiki (mobileview)
API.[2]

While this change won't affect your day-to-day browsing, it does mean that
several additional features that were dependent on the content service will
now become enabled in the app! These include:

- *Definitions of words from Wiktionary*. Tap-and-hold any word in an
article to highlight it, then tap the "Define" button to see a popup
definition of the highlighted word. (Note: this is currently enabled only
for English Wikipedia articles)

- If an article has a recorded *audio pronunciation* of its title included
in it, the app will display an "audio" button next to the article title.
Tap the button to play back the pronunciation.

- If an article has *geo coordinates* associated with it, the app will
display a "pin" button below the article title. Tapping this button will
open the default maps app on your device, and navigate to the coordinates
of the article.

Many thanks to the Services team for helping us reach this important
milestone, and props to our own Bernd and Michael for their efforts to get
this done. This will enable us to build future service-based features much
more easily, and it's our hope that the content service will be adopted by
many other consumers, not just the Android app.


[0] https://rest.wikimedia.org/en.wikipedia.org/v1/?doc#/Mobile
[1] https://www.mediawiki.org/wiki/RESTBase
[2] This is done within the app itself, and does not require an update from
the Play store.

Cheers,

--
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We've just released an updated version of the Wikipedia Android app[1][2],
rolling out as we speak to the Google Play store! Here are the highlights
from this update:

- Synchronize theme and font options across devices for logged-in users.[*]
- Restore and improve pinch-to-zoom functionality in image gallery.
- Update the Settings screen with Material design.
- Further improve memory usage and fix memory leaks on certain devices.
- Improve network data usage when retrieving certain thumbnails.
- Show link preview thumbnails even when only one or two are available.
- Miscellaneous bug and crash fixes.

Thanks to the following contributors for their patches:
* Maroloccio (@maroloccio)
* Paladox
* You?[3]

[*] On devices with Android versions earlier than Marshmallow (6.0), this
requires the app to ask for a new permission upon installing, namely the
"Identity" permission. This permission is necessary for any kind of
synchronizing interactions with remote accounts (a feature which we plan on
expanding in future updates). For more information, please refer to our FAQ
<https://www.mediawiki.org/wiki/Wikimedia_Apps/Android_FAQ#Security_and_Permissions>
.

[1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
[2]
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.1.143-releasesprod-2016-03-16.apk
[3]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking

Cheers,

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Results from similar articles A/B test

[Dmitry Brant]

Hello all,

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[0]:
- The clickthrough rate using the default morelike query is (and has been)
around 15%.
- With the new opening_text query, the clickthrough rate decreases to about
12%:

[image: Inline image 1]

Therefore, it seems that the new query has a nontrivial negative effect on
CTR :(
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.


[0]
https://docs.google.com/a/wikimedia.org/spreadsheets/d/1BFsrAcPgexQyNVemmJ3k3IX5rtPvJ_5vdYOyGgS5R6Y/edit?usp=sharing
(queries embedded as comments in the headers)

-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android app now requires "run at startup" permission?

[Dmitry Brant]

To give some more clarity to this:
The app is built in such a way as to allow certain mobile manufacturers to
have our app pre-loaded on their devices. For analytics purposes, we'd like
to know how much traffic comes from these preloads. The way that we do this
is by including a custom identifier string directly into the app, and
passing that string into the analytics.

The problem is: when the app gets updated on those devices via Google Play
(which is inevitably the first thing that happens when the device is
powered on), the identifier string gets overwritten. Therefore, we've added
an on-boot handler (which requires the new permission), so that the app
gets a chance to save the custom identifier to the settings database, which
will persist across updates of the app.

Note that we don't require this permission in the production or beta
versions of the app on Google Play, and it wasn't intentional to require
the permission in the f-droid variant (since f-droid doesn't use Google
Play). Since Stephen's patch is already merged, this will be resolved in
our next release.

-Dmitry


On Fri, Feb 19, 2016 at 12:39 PM, Stephen Niedzielski <
sniedziel...@wikimedia.org> wrote:

> I've opened a Phab for this issue[0].
>
> [0] https://phabricator.wikimedia.org/T127479
>
> On Fri, Feb 19, 2016 at 10:31 AM, Bernd Sitzmann 
> wrote:
>
>> Yes, for F-Droid the custom flavor is used. We should consider making a
>> dedicated flavor for F-Droid to avoid this permission request there.
>>
>> Regards,
>> Bernd
>>
>> On Fri, Feb 19, 2016 at 4:11 AM, Florian Schmidt <
>> florian.schmidt.wel...@t-online.de> wrote:
>>
>>> Hi Legoktm,
>>>
>>> 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[1]). I'm not sure,
>>> what flavor is used for fdroid, it's using the custom channel, it get's the
>>> permission (added in [2]).
>>>
>>> [1]
>>> https://github.com/wikimedia/apps-android-wikipedia/commit/2b18cea8108b074dcbb305258186c7abf6ca0c41
>>> [2]
>>> https://github.com/wikimedia/apps-android-wikipedia/commit/026b8ed03996d0683c62ff4d301a7181055d19b1
>>>
>>> Best,
>>> Florian
>>>
>>> -Original-Nachricht-
>>> Betreff: [WikimediaMobile] Android app now requires "run at startup"
>>> permission?
>>> Datum: 2016-02-19T08:29:44+0100
>>> Von: "Legoktm" 
>>> An: "mobile-l" 
>>>
>>> Hi,
>>>
>>> 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?
>>>
>>> Thanks,
>>> -- Legoktm
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>> _______
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Contributing to Wikipedia Android App(GSoC 2016)

[Dmitry Brant]

Hi Donald,

Thanks for your interest in our Android app! To get started with
contributing, check out this wiki page:
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking

It contains all the information you'll need for setting up a build
environment, setting up an account on our code review system, and links to
our bug and feature tracker.

If you have any questions or issues, don't hesitate to ask (via email, or
on IRC at #wikimedia-mobile on freenode).
Looking forward to your contributions!


On Tue, Feb 16, 2016 at 10:25 AM, Donaldson Epignosis 
wrote:

> Hello Guys,
>
> My name is Donald, I am 23, and also a second year undergraduate student
> from Nigeria. I am interested in contributing to the Wikimedia
> foundation[WMF] with intentions to eventually enrol in the GSoC 2016
> program if the Foundation would be participating .
>
> I am particularly interested in the Wikipedia Android App development, I
> have over 3 years worth of Android development experience which I acquired
> before I enrolled into a university.
>
> I am very inspired about the work you guys do at Wikimedia, I am a heavy
> user of your softwares, they have made a huge impact in my life and I am so
> excited about contributing to this amazing project . I would appreciate any
> advice from the team on where best to start.
>
> Thank you.
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Similar articles feature performance in CirrusSearch for apps and mobile web

[Dmitry Brant]

Just a quick note that our latest production release (just published)
contains this A/B test, in addition to the other updates.
Looking forward to seeing the numbers from this!

-Dmitry


On Sun, Jan 31, 2016 at 9:35 PM, Dmitry Brant  wrote:

> Roger that! I think we could squeeze it in -- the change would be pretty
> straightforward. We'll be able to release a Beta with this A/B test in
> short order, but it will probably be a couple weeks until our next
> production release. I hope that's all right.
>
>
> On Sat, Jan 30, 2016 at 1:02 PM, Gabriel Wicke 
> wrote:
>
>> We are also happy to add cached entry points for high-traffic end
>> points in the REST API. I commented to that effect at
>> https://phabricator.wikimedia.org/T124216#1984206. Let us know if you
>> think this would be useful for this use case.
>>
>> On Sat, Jan 30, 2016 at 8:11 AM, Adam Baso  wrote:
>> > Okay. As per https://phabricator.wikimedia.org/T124225#1984080 I think
>> if
>> > we're doing near term experimentation with a controlled A/B test the
>> Android
>> > app is the only logical place to start. Dmitry, can that work for you?
>> It's
>> > not required, but I think it would be neat to see if we can move the
>> needle
>> > even more. Of course your quarterly goals take top priority...but what
>> do
>> > you think?
>> >
>> > On Sat, Jan 23, 2016 at 5:58 AM, Adam Baso  wrote:
>> >>
>> >> Hey all, am planning to look at Phabricator tasks and provide a reply
>> >> during the upcoming weekdays. Just wanted to acknowledge I saw your
>> replies!
>> >>
>> >>
>> >> On Friday, January 22, 2016, Erik Bernhardson <
>> ebernhard...@wikimedia.org>
>> >> wrote:
>> >>>
>> >>> On Thu, Jan 21, 2016 at 1:29 AM, Joaquin Oltra Hernandez
>> >>>  wrote:
>> >>>>
>> >>>> Regarding the caching, we would need to agree between apps and web
>> about
>> >>>> the url and smaxage parameter as Adam noted so that the urls are
>> exactly the
>> >>>> same to not bloat varnish and reuse the same cached objects across
>> >>>> platforms.
>> >>>>
>> >>>> It is an extremely adhoc and brittle solution but seems like it
>> would be
>> >>>> the greatest win.
>> >>>>
>> >>>> 20% of the traffic from searches by being only in android and web
>> beta
>> >>>> seems a lot to me, and we should work on reducing it, otherwise when
>> it hits
>> >>>> web stable we're going to crush the servers, so caching seems the
>> highest
>> >>>> priority.
>> >>>>
>> >>> To clarify its 20% of the load, as opposed to 20% of the traffic. But
>> >>> same difference :)
>> >>>
>> >>>>
>> >>>> Let's chime in https://phabricator.wikimedia.org/T124216 and
>> continue
>> >>>> the cache discussion there.
>> >>>>
>> >>>> Regarding the validity of results with opening text only, how should
>> we
>> >>>> proceed? Adam?
>> >>>>
>> >>> I've put together https://phabricator.wikimedia.org/T124258 to track
>> >>> putting together an AB test that measures the difference in click
>> through
>> >>> rates for the two approaches.
>> >>>
>> >>>
>> >>>>
>> >>>> On Wed, Jan 20, 2016 at 9:34 PM, David Causse > >
>> >>>> wrote:
>> >>>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> Yes we can combine many factors, from templates (quality but also
>> >>>>> disambiguation/stubs), size and others.
>> >>>>> Today cirrus uses mostly the number of incoming links which (imho)
>> is
>> >>>>> not very good for morelike.
>> >>>>> On enwiki results will also be scored according the weights defined
>> in
>> >>>>>
>> https://en.wikipedia.org/wiki/MediaWiki:Cirrussearch-boost-templates.
>> >>>>>
>> >>>>> I wrote a small bash to compare results :
>> >>>>> https://gist.github.com/nomoa/93c5097e3c3cb3b6ebad
>> >>>>> Here is some random results from the list (Semetimes better,
>> sometimes
>> >>>>> wor

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We've just released an updated version of the Wikipedia Android app[1][2],
rolling out as we speak to the Google Play store! Here are the highlights
from this update:

* Support for animated images throughout the app (image gallery, lead
images, search results, etc).
* When saving media from the gallery, the files are now downloaded in their
original form and resolution to your device's external memory, and made
available in the device's Gallery app.
* Improved memory consumption in the app when browsing lots of pages and
images.
* Improvements to the networking layer and stability.
* Fixed account creation without an email address.
* Fixed ability to copy large amounts of text to the clipboard.
* Numerous miscellaneous bug and crash fixes.

Thanks to the following contributors for their patches:
* Yuvi Panda
* Dan Garry (Deskana)
* Justin Du (MtDu)
* You?[3]


[1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
[2]
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.1.141-releasesprod-2016-02-10.apk
[3]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking

Cheers,

--
Dmitry Brant
Senior Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Services] Someone please announce/explain T119235 (RESTBase for Wiktionary)

[Dmitry Brant]

Hi Nemo,

As Gabriel notes, the Wiktionary endpoint is still very much experimental,
and is subject to change. One of the ongoing goals for the Android app is
to integrate more rich content into the browsing experience. One such
feature is to allow the user to highlight words in an article and see a
quick popup definition of the word from Wiktionary[1]. To facilitate this
action, we set up a RESTBase endpoint for fetching the desired term from
Wiktionary[2].

This feature is currently only available in the Wikipedia Beta app, and is
restricted only to English wiktionary. Further work on this endpoint will
depend on the level of user engagement with the feature, once it's rolled
out to the main Wikipedia app. So, once again, even though we're building
the endpoint with the hope that it would be used by other consumers besides
the Android app (and expanded to all languages), at the moment it's by no
means ready for general consumption.

We do have a wiki page[3] with some more details on the service endpoints
that are used by the apps, which you, as well as the Wiktionary community,
are welcome to comment on.

-Dmitry

[1] https://phabricator.wikimedia.org/T115484
[2] https://phabricator.wikimedia.org/T119235
[3]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/RESTBase_services_for_apps


On Sun, Feb 14, 2016 at 12:18 PM, Gabriel Wicke 
wrote:

> Federico,
>
> as indicated by the classification as "experimental" [1], the
> definition end point [2] is at a very early point of its development.
> The mobile app team has added preliminary support for extracting
> definitions in the content service [3] using Parsoid's template
> metadata, and is using this end point to power a "define this word"
> feature in the next version of the Android app. You can preview the
> feature in the beta Android app when browsing English Wikipedia by
> selecting a word, and then hitting the 'definition' icon next to
> 'copy'.
>
> In this first iteration, only English Wiktionary is supported.
> Generalizing the service and API end point to provide definitions
> using more or all Wiktionaries will require more work and planning. In
> the next iteration, I would expect a focus on enabling collaborative
> definition and maintenance of extraction rules, as well as broader
> involvement of Wiktionary communities in the planning process. The
> timing for the next iteration depends partly on the mobile app team's
> priorities, so I will defer to the team to comment on this.
>
> To summarize: We are aiming to gradually develop this into a generally
> useful, stable and well-documented API entry point for word
> definitions. The experimental end point published right now is just
> the beginning, and you are very much invited to help shape the way
> forward.
>
> Gabriel
>
> [1]: https://www.mediawiki.org/wiki/API_versioning#Experimental
> [2]:
> https://en.wiktionary.org/api/rest_v1/?doc#!/Page_content/get_page_definition_term
> [3]:
> https://github.com/wikimedia/mediawiki-services-mobileapps/blob/master/lib/parseDefinition.js
>
>
> --
> Gabriel Wicke
> Principal Engineer, Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>



-- 
Dmitry Brant
Software Engineer / Product Owner (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Android Wikipedia beta app release (2.1.140-beta-2016-02-04)

[Dmitry Brant]

If bandwidth is a concern, you can always turn images off entirely
(Settings -> Show images).

As for CPU load (viz. battery usage) considerations, we haven't done
*extensive* testing, but at least on the devices I own, the increase is
barely discernible.  Of course, part of the reason for releasing this to
Beta is to test the waters with how this feature will behave in the wild,
and what feedback our users will give.


On Thu, Feb 4, 2016 at 6:33 PM, Stephen Niedzielski <
sniedziel...@wikimedia.org> wrote:

> Hello!
>
> > 1
> Animations are not configurable :( Prior to this release, we supported
> animations in articles and the new gallery animation support is a natural
> extension of that.
>
> > 2
> Yes! These changes only affect media explicitly downloaded by the user
> (via tapping the save button in the overflow menu). Bandwidth optimized
> images are still shown when paging through the gallery.
>
> On Thu, Feb 4, 2016 at 3:55 PM, Pine W  wrote:
>
>> Thanks Stephen. Questions:
>>
>> 1. Is it possible to disable animations so that the media files consume
>> less bandwidth, CPU, and memory?
>> 2. Does "Media saved in the gallery are now downloaded in their original
>> form  and resolution" refer to media files after a user clicks on them? I
>> can imagine that automatically downloading every media file in a gallery at
>> original size would consume a lot of bandwidth.
>>
>> Thanks,
>> Pine
>>
>> On Thu, Feb 4, 2016 at 2:13 PM, Stephen Niedzielski <
>> sniedziel...@wikimedia.org> wrote:
>>
>>> The Android team[0] is pleased to announce a new Wikipedia Android app
>>> beta release, v2.1.140-beta-2016-02-04[1]. This revision contains the
>>> following new functionality[2]:
>>>
>>> - Support for animated images throughout the app (gallery, search,
>>>   history, etc).
>>> - Media saved in the gallery are now downloaded in their original form
>>>   and resolution.
>>> - Improved app memory consumption.
>>> - Resize wide images to fit without scrolling.
>>> - Fix transparent image canvases in galleries.
>>> - Fix copying large amounts of text to clipboard.
>>> - Fix account creation without an email address.
>>> - Bug fix to keep the toolbar hidden when scrolling down quickly.
>>>
>>> Included in this version are patches from repeat contributor Dan
>>> Garry[3] and first time contributor, Justin Du[4]. Great work, devs!
>>>
>>> You too can help make it better! 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
>>>
>>> https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.1.140-beta-2016-02-04
>>> [3] https://twitter.com/danjgarry, IRC: Deskana
>>> [4] IRC: MtDu
>>> [5]
>>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
>>>
>>> _______
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android app: nearby, but elsewhere

[Dmitry Brant]

Hi Andy,

Glad to hear you're enjoying the feature!
It is indeed possible to look at nearby articles in other parts of the
world, but the only way to do it at the moment is to zoom out (by
pinching), scroll to the desired location, and zoom back in.

I agree that this can be further refined. I'm afraid that enhancements to
the Nearby function aren't in our plans for this quarter, but we may
revisit it in the next quarter, or perhaps at an upcoming hackathon. :)


On Mon, Feb 1, 2016 at 1:24 PM, Andy Mabbett 
wrote:

> I'm enjoying the "nearby" feature now that its been restored to the
> Android app; and especially looking forward to using it on an upcoming
> overseas trip.
>
> However, I don't seem to be able too use it, while at home, to look at
> other parts of the world. Is that possible?
>
> It could either be by scrolling or typing in the name of a far-flung
> place, or by tapping on the coordinates in a geo-tagged article.
>
> --
> Andy Mabbett
> @pigsonthewing
> http://pigsonthewing.org.uk
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>



-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Similar articles feature performance in CirrusSearch for apps and mobile web

[Dmitry Brant]

> >>>>>>> get more cache hits at the edge across all clients. Here's the URL
> I
> >>>>>>> see
> >>>>>>> being used on the web today from mobile web beta:
> >>>>>>>
> >>>>>>>
> >>>>>>>
> https://en.m.wikipedia.org/w/api.php?action=query&format=json&formatversion=2&prop=pageimages%7Cpageterms&piprop=thumbnail&pithumbsize=80&wbptterms=description&pilimit=3&generator=search&gsrsearch=morelike%3ACome_Share_My_Love&gsrnamespace=0&gsrlimit=3
> >>>>>>>
> >>>>>>>
> >>>>>>> -Adam
> >>>>>>>
> >>>>>>> On Wed, Jan 20, 2016 at 7:45 AM, Joaquin Oltra Hernandez
> >>>>>>>  wrote:
> >>>>>>>>
> >>>>>>>> I'd be up to it if we manage to cram it up in a following sprint
> and
> >>>>>>>> it is
> >>>>>>>> worth it.
> >>>>>>>>
> >>>>>>>> We could run a controlled test against production with a long
> batch
> >>>>>>>> of
> >>>>>>>> articles and check median/percentiles response time with repeated
> >>>>>>>> runs and
> >>>>>>>> highlight the different results for human inspection regarding
> >>>>>>>> quality.
> >>>>>>>>
> >>>>>>>> It's been noted previously that the results are far from ideal
> >>>>>>>> (which they
> >>>>>>>> are because it is just morelike), and I think it would be a great
> >>>>>>>> idea to
> >>>>>>>> change the endpoint to a specific one that is smarter and has some
> >>>>>>>> cache (we
> >>>>>>>> could do much more to get relevant results besides text
> similarity,
> >>>>>>>> take
> >>>>>>>> into account links, or see also links if there are, etc...).
> >>>>>>>>
> >>>>>>>> As a note, in mobile web the related articles extension allows
> >>>>>>>> editors to
> >>>>>>>> specify articles to show in the section, which would avoid queries
> >>>>>>>> to
> >>>>>>>> cirrussearch if it was more used (once rolled into stable I
> guess).
> >>>>>>>>
> >>>>>>>> I remember that the performance related task was closed as
> resolved
> >>>>>>>> (https://phabricator.wikimedia.org/T121254#1907192), should we
> >>>>>>>> reopen it or
> >>>>>>>> create a new one?
> >>>>>>>>
> >>>>>>>> I'm not sure if we ended up adding the smaxage parameter (I think
> we
> >>>>>>>> didn't), should we? To me it seems a no-brainer that we should be
> >>>>>>>> caching
> >>>>>>>> this results in varnish since they don't need to be completely up
> to
> >>>>>>>> date
> >>>>>>>> for this use case.
> >>>>>>>>
> >>>>>>>> On Tue, Jan 19, 2016 at 11:54 PM, Erik Bernhardson
> >>>>>>>>  wrote:
> >>>>>>>>>
> >>>>>>>>> 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:
> >>>>>>>>>
> >>>>>>>>> cirrusMltUseFields=yes&cirrusMltFields=opening_text
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> 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
> >>>>>>>>> only opening_text.
> >>>>>>>>>
> >>>>>>>>> Erik B.
> >>>>>>>>>
> >>>>>>>>> ___
> >>>>>>>>> Mobile-l mailing list
> >>>>>>>>> Mobile-l@lists.wikimedia.org
> >>>>>>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>>>>>>>
> >>>>>>>
> >>>>>>> ___
> >>>>>>> Mobile-l mailing list
> >>>>>>> Mobile-l@lists.wikimedia.org
> >>>>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>>>>>
> >>>>>> ___
> >>>>>> Mobile-l mailing list
> >>>>>> Mobile-l@lists.wikimedia.org
> >>>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>>>
> >>>>>
> >>>>>
> >>>>> ___
> >>>>> Mobile-l mailing list
> >>>>> Mobile-l@lists.wikimedia.org
> >>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>>
> >>>>
> >>>>
> >>>> ___
> >>>> Mobile-l mailing list
> >>>> Mobile-l@lists.wikimedia.org
> >>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >>>>
> >>>
> >
> >
> > ___
> > Mobile-l mailing list
> > Mobile-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
>
>
>
> --
> Gabriel Wicke
> Principal Engineer, Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>



-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We've just released an updated version of the Wikipedia Android app[1][2],
rolling out as we speak to the Google Play store! This is mostly a
maintenance update, focusing on improved memory usage for lower-memory
devices. Additional enhancements include:

* Introduced a toolbar under the lead image for quick access to share an
article or save it for offline reading.
* Moved "similar pages" and "page issues" to the overflow menu (when
applicable).
* Improved support for Norwegian language in the app.
* HTML tags are now stripped from edit summaries.


Cheers,

-- 
Dmitry Brant
Mobile Apps Team (Android)
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.1.137-releasesprod-2016-01-11.apk
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We're pleased to announce our latest update to the Wikipedia Android
app[1][2], rolling out as we speak to the Google Play store! Here are the
highlights from this update:

* Nearby with Maps! Tap the Nearby option in the navigation menu to see an
interactive map with Wikipedia articles about points of interest near you.
You can also pan/zoom/rotate the map and go to any other part of the world,
and see Wikipedia articles for those locations.
* In Android 6.0, highlighting a word in any other app gives the option to
search for it in Wikipedia.
* Deleting your browsing history will now also clear your open tabs.
* Updated link preview design.
* A metric ton of bug- and crash fixes.[3]

Thanks to the following brave volunteers for their excellent contributions:
* Ondřej Kroupa (Sealskej / @kroupao)
* Daniel Rey (@DanReyLop)
* Dan Garry (Deskana / @danjgarry)
* Katie Filbert (Aude / @filbertkm)
* You?[4]

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.1.136-releasesprod-2015-12-09.apk
[3] https://phabricator.wikimedia.org/T121236
[4]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Apps - WikidataPageBanner properties available from API

[Dmitry Brant]

Wow! Very cool.


On Fri, Dec 4, 2015 at 12:42 PM, Jon Robson  wrote:

> Thanks to Sumit's latest change you can now access focus area and
> image directly from the API in pageprops [1].
>
> The image comes from editor, if not present Wikidata and soon (if
> someone merges it) from PageImages [2].
>
> Currently this is only deployed on WIkivoyage but by deploying the
> extension on Wikipedia and disabling article rendering you could use
> the API for the app.
>
> Currently updating the origin x and origin y values with the API is
> not easy and as nice as it could be but it is potentially doable by
> editing the entire page and using some clever regexps.
>
> Something to think about!
>
> [1]
> http://en.wikipedia.beta.wmflabs.org/wiki/Special:ApiSandbox#action=query&prop=pageprops&format=json&titles=WikidataPageBanner_example_1
> [2] https://gerrit.wikimedia.org/r/#/c/239010/
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>



-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Android Wikipedia beta app release (2.1.135-beta-2015-12-03)

[Dmitry Brant]

Hi Pine,

This Beta release does indeed have everything shown in the Metrics demo.
We've found a couple additional minor issues that we may want to fix before
pushing all of this to production, so we may issue an additional beta in
the coming days, prior to releasing to production. Stay tuned.



On Thu, Dec 3, 2015 at 6:58 PM, Pine W  wrote:

> Thanks Stephen. Was this the mobile app version that was shown at Metrics
> today with the map service that works without GPS? Or is that feature
> already in production?
>
> Pine
> On Dec 3, 2015 3:53 PM, "Stephen Niedzielski" 
> wrote:
>
>> The Android team[0] is happy to announce a new Wikipedia Android app
>> beta release, v2.1.135-beta-2015-12-03[1]. This revision contains the
>> following new functionality and bug fixes[2]:
>>
>> * Enable title thumbnails and locations for link previews. Tap "get
>>   directions" in a link preview to launch your navigation app
>> * Significant upgrades to Nearby map and UI
>> * Add Wikipedia to the system text selection menu where available
>> * Clear tabs when clearing history
>> * Fix rare bug causing tabs to be lost or app to crash
>> * Fix titles with spaces not recognized as saved
>> * Fix web requests for certain system languages
>> * Fix sporadic crash on pages with images
>>
>> Included in this version are patches from Ondřej Kroupa[3] and repeat
>> contributors Daniel Rey[4] and Dan Garry[5]. Very nice work!
>>
>> You too can help make it better! Read our getting started guide[6]. 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
>>
>> https://phabricator.wikimedia.org/diffusion/APAW/history/master/;beta/2.1.135-beta-2015-12-03
>> [3] https://twitter.com/kroupao, IRC: kroupao
>> [4] https://twitter.com/DanReyLop
>> [5] https://twitter.com/danjgarry, IRC: Deskana
>> [6]
>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We're pleased to announce our latest update to the Wikipedia Android
app[1][2], available now on the Google Play store! Here are the highlights
from this update:

* Added share-a-fact support for Android Marshmallow devices.
* Improved fallback to cached or saved versions of articles, when not
connected to the Internet.
* Images saved to external storage are saved in a separate Wikipedia Images
folder.
* Fixed possible crashes upon launch for certain devices.
* Fixed occasional flickering when scrolling on some devices.
* Added donation link to navigation drawer.
* Various other bug fixes and design enhancements.[3]

A big thanks to the following volunteers for their excellent contributions:
* Daniel Rey (@DanReyLop)
* Wikinaut (@Wikinaut)
* You?[4]

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.1.134-releasesprod-2015-11-12.apk
[3] https://phabricator.wikimedia.org/T118853
[4]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi all,

We're pleased to announce our latest update to the Wikipedia Android
app[1][2], available now on the Google Play store! Here are the highlights
from this update:

* More consistent article language display for multilingual users.
* Fixed occasional abnormal CPU usage.
* Improved crash reporting.
* Added preference to enable/disable link previews.
* Improved link preview design and text.
* Display system notification after saving an image.
* Various other bug fixes and design enhancements.[3]

We'd also like to thank the following volunteers for their excellent
contributions:
* Daniel Rey (@DanReyLop)
* Wikinaut (@Wikinaut)
* Asad Salman (asadpsalman)
* You?[4]

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.1.133-releasesprod-2015-10-26.apk
[3] https://phabricator.wikimedia.org/T116922
[4]
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_hacking
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We've released our latest update to the Wikipedia Android app[1][2],
available now on the Google Play store. This is mostly a maintenance
release that contains a few bug fixes and minor design updates since our
previous version.

More notably, as we announced earlier[3], this will be the last version of
the app that supports older Android devices, specifically devices older
than Ice Cream Sandwich MR1 (i.e. older than version 4.0.3, API 15).  As we
continue to release future versions of the app, these older devices will
still be able to install our app from the Play Store, but the version that
they receive will be frozen at today's release.  Newer devices will, of
course, continue to receive the latest version of the app, as before.


Best,

--
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.0.111-releasesprod-2015-09-16.apk
[3] https://lists.wikimedia.org/pipermail/mobile-l/2015-August/009724.html
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

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.0.110-releasesprod-2015-08-31.apk
[3] https://phabricator.wikimedia.org/T112093
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] What people think about Wikidata descriptions in search on mobile web beta, and a question about "arbitrary access" of Wikidata data

[Dmitry Brant]

My thoughts, as ever(!), are as follows:

- The tool that generates the descriptions deserves a lot more development.
Magnus' tool is very much a prototype, and represents a tiny glimpse of
what's possible. Looking at its current output is a straw man.
- Auto-generated descriptions work for current articles, and *all future
articles*. They automatically adapt to updated data. They automatically
become more accurate as new data is added.
- When you edit the descriptions yourself, you're not really making a
meaningful contribution to the *data* that underpins the given Wikidata
entry; i.e. you're not contributing any new information. You're simply
paraphrasing the first sentence or two of the Wikipedia article. That can't
possibly be a productive use of contributors' time.

As for Brian's suggestion:
It would be a step forward; we can even invent a whole template-type syntax
for transcluding bits of actual data into the description. But IMO, that
kind of effort would still be better spent on fully-automatic descriptions,
because that's the ideal that semi-automatic descriptions can only approach.


On Tue, Aug 18, 2015 at 10:36 PM, Brian Gerstle 
wrote:

> Could there be a way to have our nicely curated description cake and eat
> it too? For example, interpolating data into the description and/or marking
> data points which are referenced in the description (so as to mark it as
> outdated when they change)?
>
> I appreciate the potential benefits of generated descriptions (and other
> things), but Monte's examples might have swayed me towards human
> curated—when available.
>
> On Tuesday, August 18, 2015, Monte Hurd  wrote:
>
>> Ok, so I just did what I proposed. I went to random enwiki articles and
>> described the first ten I found which didn't already have descriptions:
>>
>>
>> - "Courage Under Fire", *1996 film about a Gulf War friendly-fire
>> incident*
>>
>> - "Pebasiconcha immanis", *largest known species of land snail, extinct*
>>
>> - "List of Kenyan writers", *notable Kenyan authors*
>>
>> - "Solar eclipse of December 14, 1917", *annular eclipse which lasted 77
>> seconds*
>>
>> - "Natchaug Forest Lumber Shed", *historic Civilian Conservation Corps
>> post-and-beam building*
>>
>> - "Sun of Jamaica (album)", *debut 1980 studio album by Goombay Dance
>> Band*
>>
>> - "E-1027", *modernist villa in France by architect Eileen Gray*
>>
>> - "Daingerfield State Park", *park in Morris County, Texas, USA,
>> bordering Lake Daingerfield*
>>
>> - "Todo Lo Que Soy-En Vivo", *2014 Live album by Mexican pop singer Fey*
>>
>> - "2009 UEFA Regions' Cup", *6th UEFA Regions' Cup, won by Castile and
>> Leon*
>>
>>
>>
>> And here are the respective descriptions from Magnus' (quite excellent)
>> autodesc.js:
>>
>>
>>
>> - "Courage Under Fire", *1996 film by Edward Zwick, produced by John
>> Davis and David T. Friendly from United States of America*
>>
>> - "Pebasiconcha immanis", *species of Mollusca*
>>
>> - "List of Kenyan writers", *Wikimedia list article*
>>
>> - "Solar eclipse of December 14, 1917", *solar eclipse*
>>
>> - "Natchaug Forest Lumber Shed", *Construction in Connecticut, United
>> States of America*
>>
>> - "Sun of Jamaica (album)", *album*
>>
>> - "E-1027", *villa in Roquebrune-Cap-Martin, France*
>>
>> - "Daingerfield State Park", *state park and state park of a state of
>> the United States in Texas, United States of America*
>>
>> - "Todo Lo Que Soy-En Vivo", *live album by Fey*
>>
>> - "2009 UEFA Regions' Cup", *none*
>>
>>
>>
>> Thoughts?
>>
>> Just trying to make my own bold assertions falsifiable :)
>>
>>
>>
>> On Tue, Aug 18, 2015 at 6:32 PM, Monte Hurd  wrote:
>>
>>> The whole human-vs-extracted descriptions quality question could be
>>> fairly easy to test I think:
>>>
>>> - Pick, some number of articles at random.
>>> - Run them through a description extraction script.
>>> - Have a human describe the same articles with, say, the app interface I
>>> demo'ed.
>>>
>>> If nothing else this exercise could perhaps make what's thus far been a
>>> wildly abstract discussion more concrete.
>>>
>>>
>>>
>>>
>>> On Tue, Aug 18, 2015

Re: [WikimediaMobile] What people think about Wikidata descriptions in search on mobile web beta, and a question about "arbitrary access" of Wikidata data

[Dmitry Brant]

IMO, allowing the user to edit the description is a missed opportunity to
make the user edit the actual *data*, such that the description is
generated correctly.



On Tue, Aug 18, 2015 at 8:02 PM, Monte Hurd  wrote:

> IMO, if the goal is quality, then human curated descriptions are superior
> until such time as the auto-generation script passes the Turing test ;)
>
> I see these empty descriptions as an amazing opportunity to give
> *everyone* an easy new way to edit. I whipped an app editing interface up
> at the Lyon hackathon:
> https://www.youtube.com/watch?v=6VblyGhf_c8
>
> I used it to add a couple hundred descriptions in a single day just by
> hitting "random" then adding descriptions for articles which didn't have
> them.
>
> I'd love to try a limited test of this in production to get a sense for
> how effective human curation can be if the interface is easy to use...
>
>
> On Tue, Aug 18, 2015 at 1:25 PM, Jan Ainali 
> wrote:
>
>> Nice one!
>>
>> Does not appear to work on svwiki though. Does it have something to do
>> with that the wiki in question does not display that tagline?
>>
>>
>> *Med vänliga hälsningar,Jan Ainali*
>>
>> Verksamhetschef, Wikimedia Sverige <http://wikimedia.se>
>> 0729 - 67 29 48
>>
>>
>> *Tänk dig en värld där varje människa har fri tillgång till
>> mänsklighetens samlade kunskap. Det är det vi gör.*
>> Bli medlem. <http://blimedlem.wikimedia.se>
>>
>>
>> 2015-08-18 17:23 GMT+02:00 Magnus Manske :
>>
>>> Show automatic description underneath "From Wikipedia...":
>>> https://en.wikipedia.org/wiki/User:Magnus_Manske/autodesc.js
>>>
>>> To use, add:
>>> importScript ( 'User:Magnus_Manske/autodesc.js' ) ;
>>> to your common.js
>>>
>>> On Tue, Aug 18, 2015 at 9:47 AM Jane Darnell  wrote:
>>>
>>>> It would be even better if this (short: 3 field max) pipe-separated
>>>> list was available as a gadget to wikidatans on Wikipedia (like me). I
>>>> can't see if a page I am on has an "instance of" (though it should) and I
>>>> can see the description thanks to another gadget (sorry no idea which one
>>>> that is). Often I will update empty descriptions, but if I was served basic
>>>> fields (so for a painting, the creator field), I would click through to
>>>> update that too.
>>>>
>>>> On Tue, Aug 18, 2015 at 9:58 AM, Federico Leva (Nemo) <
>>>> nemow...@gmail.com> wrote:
>>>>
>>>>> Jane Darnell, 15/08/2015 08:53:
>>>>>
>>>>>> Yes but even if the descriptions were just the contents of fields
>>>>>> separated by a pipe it would be better than nothing.
>>>>>>
>>>>>
>>>>> +1, item descriptions are mostly useless in my experience.
>>>>>
>>>>> As for "get into production on Wikipedia" I don't know what it means,
>>>>> I certainly don't like 1) mobile-specific features, 2) overriding existing
>>>>> manually curated content; but it's good to 3) fill gaps. Mobile folks 
>>>>> often
>>>>> do (1) and (2), if they *instead* did (3) I'd be very happy. :)
>>>>>
>>>>> Nemo
>>>>>
>>>>
>>>> ___
>>>> Mobile-l mailing list
>>>> Mobile-l@lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>>
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] What people think about Wikidata descriptions in search on mobile web beta, and a question about "arbitrary access" of Wikidata data

[Dmitry Brant]

> The argument "not good enough" is a fail IMHO, though. If it's bad,
improve the algorithm and/or add statements. If it's still bad, THEN add a
manual description.

+10^100


On Fri, Aug 14, 2015 at 6:22 PM, Magnus Manske 
wrote:

>
>
> On Fri, Aug 14, 2015 at 9:54 PM Gergo Tisza  wrote:
>
>>
>> On Fri, Aug 14, 2015 at 10:31 AM, Magnus Manske <
>> magnusman...@googlemail.com> wrote:
>>
>>> IMHO the next step is auto-generating short descriptions from the item
>>> statements, which will be perfectly fine for the vast majority of cases.
>>>
>>
>> The Wikidata team is not a fan of that idea: T91981
>> <https://phabricator.wikimedia.org/T91981>
>>
>> Yes, sadly. The argument "not good enough" is a fail IMHO, though. If
> it's bad, improve the algorithm and/or add statements. If it's still bad,
> THEN add a manual description.
>
> I think the worst possible description is the one that's missing.
>
> Back-of-the-envelope calculation:
> * We have ~45 million manual descriptions at the moment on Wikidata
> * We have ~18 million items
> * We have ~250 languages
> That means that, as of this moment, less than 1% of all possible
> descriptions are filled in. And the quality of these manual descriptions is
> everyone's best guess; I've seen plenty "disambiguation page" and "category
> page", EVEN IS THAT IS NOT TRUE. Some crappy bot filled those in. No chance
> of quickly fixing this.
>
> So, 99% descriptions missing, with little chance of them getting filled in
> at all (think: small languages), and a rather dubious track record for the
> ones that are.
>
> It's like letting people drown in the Mediterranean because the tents to
> house them temporarily are "not good enough". Frustrating, seriously.
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>


-- 
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Old Wikipedia-App tasks in Phabricator

[Dmitry Brant]

Hey Andre,
Thanks for reminding us about these. Since they're not associated with the
active Android and iOS projects, they've fallen through the cracks.
I'll go through as many as I can, and try to close any duplicates or
invalid ones, or bring them into the Android project if they're still
relevant.


On Tue, Aug 11, 2015 at 6:54 AM, Andre Klapper 
wrote:

> Hey Mobile Apps crew,
>
> there are 58 open tasks in archived Wikipedia-App-* Phabricator
> projects which do not have any active projects associated either:
>
> https://phabricator.wikimedia.org/maniphest/query/s4y9prrcTSnQ/#R
>
> What should happen to these tasks and what feedback should be given to
> the folks who spent time to report those issues?
>
> We can mass-{add comments, change statuses, change priorities} but I
> don't know which message you'd like to send out here.
>
> Thanks in advance!,
> andre
> --
> Andre Klapper | Wikimedia Bugwrangler
> http://blogs.gnome.org/aklapper/
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We're thrilled to bring you our latest update to the Wikipedia Android
app[1][2], available now on the Google Play Store. Here are the highlights
from this release:

* Tabbed browsing! Pressing-and-holding a link now lets you open it in a
new tab, allowing you to keep reading the current article without losing
your place, and switch to the new tab when you're ready.  This can also be
done directly from Search results, Nearby results, "Similar Pages" links,
and "Read More" links. To view and manage your current list of open tabs,
press the Tabs button near the top-right corner, which will allow you to
switch to any tab in the list, create a new tab, or close a tab.

* Language selection from the Search bar! When searching from within the
app, you can now select the language of Wikipedia to be searched. By
default, the Wiki language in the app is set to the system language of your
Android device. But now, for our multilingual friends, you can quickly
change your preferred language by pressing the button next to the Search
field while searching.

* A slightly redesigned table-of-contents button: the button now appears at
the bottom right of the screen, and disappears a short time after you
scroll away from the top of the article. The button reappears if you start
scrolling quickly, or if you reach the top of the article again. (The table
of contents is also still accessible by swiping from the right edge of the
screen)

Additional minor enhancements include:
* Added and updated some more Material Design components in the app.
* Improved error handling and presentation of error messages throughout the
app.
* Improved relevance of "read more" suggestions at the bottom of articles.
* Added option to view the current page in an external browser (at the
bottom of the article).
* Many more bug fixes and localization updates.[3]

Until next time, happy reading!

Best,


Dmitry Brant

Mobile Apps Team (Android)

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.0.108-releasesprod-2015-08-04.apk
[3] https://phabricator.wikimedia.org/T107344
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Wikitech-l] Showing article information on tap in Wikipedia mobile app (a thank you)

[Dmitry Brant]

Hi Tomasz,

Thanks for your feedback! The link preview feature is something that we're
actively developing, and are very excited to promote to the stable app as
soon as it's ready.

Thanks for continuing to use the app, and feel free to give any additional
feedback anytime!

Best,

-- 

Dmitry Brant

Mobile Apps Team (Android)

Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering

On Sat, Aug 8, 2015 at 4:50 PM, Tomasz W. Kozlowski 
wrote:

> Hi!
> So I'm just going through the latest Wikimedia Foundation quarterly
> report, and I stumbled on a short passage that mentions a feature of
> the mobile Wikipedia app that I really, really enjoy using.
>
> The ability to view a link preview when clicking on an article link
> inside the app is just fantastic.  Not only does it save time when you
> only need to quickly look up a fact, but the way that the app does it
> is elegant and fast.
>
> I'm using the alpha version of the app on an Android 5.1 smartphone,
> and the report says it's also in the beta version, but I do hope it
> will be added to the stable app too :-)
>
> So, to cut a long story short: a huge thank you and please-keep-it-up
> to the mobile team for implementing this handy little feature :-)
>
> --
> Tomasz
>
> ___
> Wikitech-l mailing list
> wikitec...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Apps for Kindle and Windows

[Dmitry Brant]

I've just received access to the beta of the Windows Android Bridge[1],
which will supposedly allow Android apps to run on Windows 10 Mobile with
very little modification. In fact, most of the bridge functionality has to
do with providing interop functions that replace Google Play services,
which we don't use anyway.

I'll also mention that Microsoft has an equivalent bridge for iOS apps
(which they've recently open-sourced[2]) that should allow existing iOS
apps to run on Windows Phone.

My concern, however, would be that our Android app (or iOS app) would look
really out of place if it ran unmodified within the ecosystem of Windows 10
Mobile, meaning that we would still need to devote significant design and
engineering resources to make the app look like it "belongs" on this
platform...


[1] http://uwp.dev.windows.com/en-us/uwp-bridges/android/
[2] https://github.com/Microsoft/WinObjC/



On Mon, Aug 3, 2015 at 6:29 AM, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:

> Thanks for the link Adam, there's interesting context there.
>
> On Thu, Jul 30, 2015 at 5:32 PM, Adam Baso  wrote:
>
>> My understanding is: in part, although people who were on the mobile team
>> during the most active part of these projects are probably best situated to
>> speak to it. There's also this page that has some historical information:
>>
>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Wikipedia/Hybrid_notes
>>
>> -Adam
>>
>>
>>
>>
>>
>> On Thu, Jul 30, 2015 at 7:41 AM, Stephane Bisson 
>> wrote:
>>
>>> Is the firefox os wikipedia app that's currently out there based on the
>>> old phonegap app?
>>>
>>> https://marketplace.firefox.com/app/wikipedia/
>>>
>>> https://gerrit.wikimedia.org/r/#/admin/projects/apps/firefox/wikipedia
>>>
>>>
>>> On Thu, Jul 30, 2015 at 10:06 AM, Michael Holloway <
>>> mhollo...@wikimedia.org> wrote:
>>>
 The old PhoneGap app repo lives here on GitHub:
 https://github.com/wikimedia/WikipediaMobile

 (I haven't touched it and can't speak to its current state.)

 On Thu, Jul 30, 2015 at 9:52 AM, Joaquin Oltra Hernandez <
 jhernan...@wikimedia.org> wrote:

> I've also floated the idea of cleaning up / replacing the experimental
>> Firefox OS app (which is based on our old PhoneGap app code) and using a
>> modernized HTML5+JS app for both Firefox OS and Windows 10 Tablet/Mobile.
>> Nobody's bitten on the idea yet, but I think it might be better than 
>> trying
>> to separately spin up resources for multiple minority mobile OSs.
>
>
> Where is such phonegap app? I'm very interested in building a web
> client and have already been doing so for the last 2 hackathons
>  (T106275
> ) and I'm working on it
> thinking mobile first.
>
> I would be very interested in checking the feature set of the old
> phonegap app and when good enough, making an effort to package something
> like that web client for firefoxOS & windows phone.
>
> Thoughts?
>
> On Sun, Jul 26, 2015 at 4:10 AM, Stephen Niedzielski <
> sniedziel...@wikimedia.org> wrote:
>
>>   Hey! I believe we update the Wikipedia for Fire OS (Android) app[0]
>> whenever a production version has fully rolled out on Play, although we
>> don't offer the Beta[2] on Appstore. I can see they're both currently at
>> the latest and greatest. I don't have Fire device presently, but if you
>> highlight a term for sharing and have Wikipedia installed, you should get
>> the option to search with the app. I *thought* there was also some
>> additional platform level support for Wikipedia lookups built by Amazon 
>> but
>> I might be mistaken.
>>
>>
>> --stephen
>>
>> [0] https://www.amazon.com/gp/mas/dl/android?p=org.wikipedia
>> [1] https://play.google.com/store/apps/details?id=org.wikipedia
>> [2] https://play.google.com/store/apps/details?id=org.wikipedia.beta
>>
>> On Sat, Jul 25, 2015 at 7:42 PM, Pine W  wrote:
>>
>>> Hi Brion,
>>>
>>> Ok, thanks.
>>>
>>> Is the Wikipedia app promoted to Kindle Fire users very much? It
>>> would be interesting if highlighting a term in a Kindle book or 
>>> newspaper
>>> would take the user to a Wikipedia or Wiktionary article for definitions
>>> and background info.
>>>
>>> I wonder if Microsoft would be willing to support Wikipedia app
>>> development for Windows with Microsoft financing or in-kind 
>>> contribution of
>>> developer time. Any thoughts?
>>>
>>> Pine
>>> On Jul 25, 2015 6:08 PM, "Brion Vibber" 
>>> wrote:
>>>
 On Sat, Jul 25, 2015 at 5:56 PM, Pine W 
 wrote:

> Hi Mobilizers,
>
> 1. Do you think it would make sense to develop a Wikipedia app for
> Kindle, or to encourage Amazon to do so or financially spons

Re: [WikimediaMobile] [Wikimedia-search] Fwd: "Morelike" suggestions - the results are in!

[Dmitry Brant]

Will surely take note for next time. Thanks!
Now that we've got the results from this test, we will soon update the app
to use *only* morelike suggestions, which means you'll be getting twice as
many morelike queries from the app as before. (We'll let you know when
that's released)

On Wed, Jul 29, 2015 at 4:17 PM, Oliver Keyes  wrote:

> This is fantastic work to see!
>
> For future work around this stuff, can I ask that you keep us in the
> loop? When you build a feature like this, users get more things - and
> search gets more queries, some that succeed and some but fail. But for
> this email at the tail-end of the test we wouldn't know this was
> happening, and it has the potential to mess with some of our core
> KPIs.
>
> On 29 July 2015 at 16:01, Dmitry Brant  wrote:
> > moving to mobile-l, and cc Search & Discovery.
> >
> > -- Forwarded message --
> > From: Dmitry Brant 
> > Date: Wed, Jul 29, 2015 at 3:38 PM
> > Subject: "Morelike" suggestions - the results are in!
> > To: Internal communication for WMF Reading team
> > 
> >
> >
> > Hi all,
> >
> > For the last few weeks, we've had an A/B test in the Android app where we
> > measure user engagement with the "read more" suggestions that we show at
> the
> > bottom of each article. We display three suggestions for further reading,
> > based on either (A) a plain full-text search query based on the title of
> the
> > current article, or (B) a query using the "morelike" feature in
> > CirrusSearch.
> >
> > And the winner is... (perhaps not entirely surprisingly) "morelike"!
> Users
> > who saw suggestions based on "morelike" were over 20% more likely to
> click
> > on one of the suggestions.
> >
> > Here's a quick analysis and chart of the data from the last 10 days:
> >
> >
> https://docs.google.com/spreadsheets/d/1BFsrAcPgexQyNVemmJ3k3IX5rtPvJ_5vdYOyGgS5R6Y/edit?usp=sharing
> >
> >
> > -Dmitry
> >
> >
> >
> > ___
> > Wikimedia-search mailing list
> > wikimedia-sea...@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/wikimedia-search
> >
>
>
>
> --
> Oliver Keyes
> Research Analyst
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Fwd: "Morelike" suggestions - the results are in!

[Dmitry Brant]

moving to mobile-l, and cc Search & Discovery.

-- Forwarded message --
From: Dmitry Brant 
Date: Wed, Jul 29, 2015 at 3:38 PM
Subject: "Morelike" suggestions - the results are in!
To: Internal communication for WMF Reading team <
reading-...@lists.wikimedia.org>


Hi all,

For the last few weeks, we've had an A/B test in the Android app where we
measure user engagement with the "read more" suggestions that we show at
the bottom of each article. We display three suggestions for further
reading, based on either (A) a plain full-text search query based on the
title of the current article, or (B) a query using the "morelike" feature
in CirrusSearch.

And the winner is... (perhaps not entirely surprisingly) "morelike"!  Users
who saw suggestions based on "morelike" were over 20% more likely to click
on one of the suggestions.

Here's a quick analysis and chart of the data from the last 10 days:

*https://docs.google.com/spreadsheets/d/1BFsrAcPgexQyNVemmJ3k3IX5rtPvJ_5vdYOyGgS5R6Y/edit?usp=sharing
<https://docs.google.com/spreadsheets/d/1BFsrAcPgexQyNVemmJ3k3IX5rtPvJ_5vdYOyGgS5R6Y/edit?usp=sharing>*


-Dmitry
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] In-app editing / talk pages support

[Dmitry Brant]

Thanks for taking initiative on this, Michael! Talk pages are indeed part
of the life-blood of Wikipedia, and should ideally be accessible from the
app.  Here, however, are the challenges I see with the kind of
implementation that you're proposing:

Amir correctly notes that Flow is gradually poising itself to replace
traditional talk pages, being backed by structured data and a nice API that
the apps will be able to use natively. If we want to get talk pages
"right," we would need to implement a great native presentation of Flow.

But more importantly, you mentioned yourself that talk pages are really
part of the _editing_ experience. And, quite frankly, we have to remind
ourselves that the apps are still light years away from having a good
editing experience. Therefore, providing access to talk pages without
providing the other fundamentals that are central to editing (moderation
tools, watchlists, diffs, notifications, etc) may be putting the cart
before the horse, and may lead to confusion. In fact, I'm not sure if any
*one* of those editing features makes sense without all the others. And to
implement all of those features in the apps would require a department-wide
focus on editing, which is currently not the case.

All that being said, I'm not opposed to making gradual progress towards
better editing features, as long as we maintain our focus on creating a
beautiful reading experience.  To sum up, I'm not opposed to adding an
option to go to the Talk page of an article, but until the app has a more
robust editing experience, I would suggest that this option takes the user
to the Mobile Web version of the talk page (like we currently do for
article history), and make it much less prominent than a primary action in
the Toolbar.



On Wed, Jul 22, 2015 at 1:34 PM, Amir E. Aharoni <
amir.ahar...@mail.huji.ac.il> wrote:

> > Now, this is enabled on certain pages at the moment, no?
>
> Yes, only on particular pages.
>
> At least one Wikipedia has it on Village Pump - Catalan:
> https://ca.wikipedia.org/wiki/Viquip%C3%A8dia:La_taverna/Novetats .
>
> AFAIK, the intention is to transition all talk and discussion ages to Flow
> some day, and I don't know when will it actually happen. Maybe Danny has a
> better idea.
>
>
> --
> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> http://aharoni.wordpress.com
> ‪“We're living in pieces,
> I want to live in peace.” – T. Moore‬
>
> 2015-07-22 12:28 GMT-05:00 Adam Baso :
>
>> I see. Now, this is enabled on certain pages at the moment, no? Or is
>> there a means of activating the Flow mobile-compatible mode with well
>> formed URLs or something like that for any given .m.wikipedia.org
>> page? Apologies, I do most of my Talk page stuff on desktop typically. But
>> that said, that is a pretty nice layout on those links you listed!
>>
>> -Adam
>>
>
> On Wed, Jul 22, 2015 at 10:02 AM, Amir E. Aharoni <
> amir.ahar...@mail.huji.ac.il> wrote:
>
>> No, I'm not sure what does mobileaction=toggle_view_desktop do for Flow.
>>
>> I was referring to rendering of Flow on mobile websites, for example
>> https://m.mediawiki.org/wiki/Talk:CX or
>> https://he.m.wikipedia.org/wiki/User_talk:Amire80 .
>>
>> Trying it on an actual phone gives the best effect.
>>
>> Though there certainly are some issues (
>> https://phabricator.wikimedia.org/T93430 ), Flow pages work FAR better
>> on phones than the classic talk pages.
>>
>>
>> --
>> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
>> http://aharoni.wordpress.com
>> ‪“We're living in pieces,
>> I want to live in peace.” – T. Moore‬
>>
>> 2015-07-22 11:58 GMT-05:00 Adam Baso :
>>
>>> Amir, are you referring to use of the inbuilt "desktop" mode of Flow,
>>> such as
>>> https://www.mediawiki.org/wiki/Talk:MediaWiki?mobileaction=toggle_view_desktop
>>> ?
>>>
>>> -Adam
>>>
>>
>> On Wed, Jul 22, 2015 at 8:30 AM, Amir E. Aharoni <
>> amir.ahar...@mail.huji.ac.il> wrote:
>>
>>> It's probably a dilettante-ish comment, but for a while already Flow has
>>> been working quite well on mobile web, incomparably better than the old
>>> talk pages, and it could be Flow's biggest "selling point". My intuition
>>> tells me that work to support talk pages on mobile should focus more on
>>> Flow and less on the old talk pages.
>>>
>>>
>>> --
>>> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
>>> http://aharoni.wordpress.com
>>> ‪“We're living in pieces,
>>> I want to live in peace.” – T. Moore‬
>>>
>>> 2015-07-22 10:12 GMT-05:00 Adam Baso :
>>>
 Moving discussion to mobile-l.

 On Wednesday, July 22, 2015, Michael Holloway 
 wrote:

> OK by me.
>
> On Wed, Jul 22, 2015 at 10:53 AM, Adam Baso 
> wrote:
>
>> Okay to move this discussion to mobile-l?
>>
>> I'm talking with Editing (includes VE and Flow) this morning about
>> engagement model and their short to medium term roadmap, which should be
>> helpful in your guys' examination of bridge/stopgap solutions for this
>> pretty fundamental 

Re: [WikimediaMobile] deep-linking in apps

[Dmitry Brant]

For the Android app, we do indeed. If you look at the HTML of any wiki
article, you'll notice an "alternate" link in the  tag that looks
like this:



This is a deep link that tells Google that it's possible to open this page
in our Android app.


On Mon, Jul 13, 2015 at 11:28 AM, Toby Negrin  wrote:

> Do we support any deep-linking[1] scheme for our apps? I know that we've
> made some steps in integrating with google search on this but I don't know
> what our general approach.
>
> thanks,
>
> -Toby
>
> [1] https://en.wikipedia.org/wiki/Mobile_deep_linking
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi Pine,

We usually work with Comms when we have a significant new feature in the
apps that we want to promote, and Comms has done a great job so far of
notifying all the various tech news outlets to pick up the story (for
example[1]).  The app is also fairly easily discoverable within the Play
Store itself, although we could probably benefit from some SEO to make the
app rank higher for different search terms.
Are there additional venues for spreading the word about the apps that you
would suggest?

[1]
http://techcrunch.com/2015/01/15/wikipedia-rolls-out-a-redesigned-mobile-app/



On Wed, Jul 8, 2015 at 2:34 PM, Pine W  wrote:

> Thanks Dmitry. Is WMF Comms going to market product updates like this? One
> item of feedback on the Strategic Plan was a request for a Wikipedia app,
> suggesting a lack of public awareness about the existing apps.
>
> Pine
> On Jul 8, 2015 7:30 AM, "Dmitry Brant"  wrote:
>
>> Hi everyone,
>>
>> We've released a new version of the production Wikipedia Android app
>> [1][2], which is currently rolling out to all Play Store users today. This
>> is mostly a maintenance release, with a few welcome visual enhancements.
>> Here's an abridged list of the updates in this release:
>>
>> * Enlarged images when browsing articles
>> * Improved "read more" suggestions at the bottom of articles
>> * Enabled "Search Wikipedia" when sharing text from other apps
>> * Added system language support & Chinese dialects to Wikipedia language
>> picker
>> * Improved appearance and consistency of article lists (History, Saved
>> Pages, etc.)
>> * Improved text alignment for mixed left-to-right and right-to-left
>> languages
>> * Improved page caching
>> * Added link to app FAQ in the "More" menu
>> * Various miscellaneous fixes and enhancements [3]
>>
>> Stay tuned for future updates! We have some big things in store for our
>> next release. You won't want to miss it!
>>
>> Best,
>>
>> Dmitry Brant
>> Mobile apps team (Android)
>> Wikimedia Foundation
>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team
>>
>> [1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
>> [2]
>> https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.0.105-releasesprod-2015-06-30.apk
>> [3] https://phabricator.wikimedia.org/T103788
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi Baha,

I'm afraid that support for watchlists is not in the immediate future for
the app. However, one thing that we're planning on doing is syncing of
saved pages across devices (i.e. the list of saved pages persists with the
user's account), but this is also more towards Q2/Q3.



On Wed, Jul 8, 2015 at 1:33 PM, Bahodir Mansurov 
wrote:

> On Jul 8, 2015, at 10:30 AM, Dmitry Brant  wrote:
>
>
> Stay tuned for future updates! We have some big things in store for our
> next release. You won't want to miss it!
>
> That’s great news, Dmitry. Is watchlist coming to Android too? (Or is it
> already there which I didn’t see?) I’d really love to be able to access all
> my watched pages on Android and add them to the saved pages for a later
> reading.
>
> Thanks,
> Baha
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] New Android production release

[Dmitry Brant]

Hi everyone,

We've released a new version of the production Wikipedia Android app
[1][2], which is currently rolling out to all Play Store users today. This
is mostly a maintenance release, with a few welcome visual enhancements.
Here's an abridged list of the updates in this release:

* Enlarged images when browsing articles
* Improved "read more" suggestions at the bottom of articles
* Enabled "Search Wikipedia" when sharing text from other apps
* Added system language support & Chinese dialects to Wikipedia language
picker
* Improved appearance and consistency of article lists (History, Saved
Pages, etc.)
* Improved text alignment for mixed left-to-right and right-to-left
languages
* Improved page caching
* Added link to app FAQ in the "More" menu
* Various miscellaneous fixes and enhancements [3]

Stay tuned for future updates! We have some big things in store for our
next release. You won't want to miss it!

Best,

Dmitry Brant
Mobile apps team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_Apps/Team

[1] https://play.google.com/store/apps/details?id=org.wikipedia&hl=en
[2]
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.0.105-releasesprod-2015-06-30.apk
[3] https://phabricator.wikimedia.org/T103788
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [reading-wmf] Wikipedia article previews in Kindle app

[Dmitry Brant]

Sure! When I highlight the word "London", the Wikipedia preview contains an
IPA block that has a link which, when pressed, causes the app to crash.


On Fri, Jun 5, 2015 at 11:27 AM, Adam Baso  wrote:

> Thanks. Want me to reach out to Amazon about that crash condition so they
> can patch it?
>
>
> On Friday, June 5, 2015, Dmitry Brant  wrote:
>
>> +mobile-l
>>
>>
>> On Fri, Jun 5, 2015 at 11:23 AM, Adam Baso  wrote:
>>
>>> Okay to move this to mobile-l?
>>>
>>>
>>> On Friday, June 5, 2015, Brian Gerstle  wrote:
>>>
>>>> While they strip out links/citations, they do preserve text formatting
>>>> (italics & bold).
>>>>
>>>> On Fri, Jun 5, 2015 at 10:39 AM, Bernd Sitzmann 
>>>> wrote:
>>>>
>>>>> Nice find. I also like being able to swipe those cards left/right
>>>>> between different information sources. Looks like depending on the 
>>>>> selected
>>>>> words it's: Dictionary, Wikipedia, Translation
>>>>>
>>>>> On Thu, Jun 4, 2015 at 10:45 PM, Dmitry Brant 
>>>>> wrote:
>>>>>
>>>>>> I was using the Kindle app on the plane today, and I noticed a few
>>>>>> interesting things, including this:
>>>>>> ​
>>>>>>  device-2015-06-04-225651.png
>>>>>> <https://docs.google.com/a/wikimedia.org/file/d/0BzcksMsMNpY1SzA3bHY4WF9hM1U/edit?usp=drive_web>
>>>>>> ​
>>>>>> When highlighting a word or phrase, the user is presented with a
>>>>>> definition of the word from Wikipedia. The content is presented in a 
>>>>>> native
>>>>>> component, with only the first section of text shown (all links,
>>>>>> references, infoboxes, etc. are stripped out). (I wonder what API they're
>>>>>> using?)
>>>>>>
>>>>>> It looks very similar to the link preview prototypes we've been
>>>>>> developing in our apps, and it's very telling that the Kindle app has 
>>>>>> such
>>>>>> a feature, since it helps emphasize the usefulness of this feature in any
>>>>>> kind of "reader" app.  Perhaps, in addition to link previews, we may also
>>>>>> want to think about allowing users to highlight words and show 
>>>>>> definitions
>>>>>> (from Wiktionary?), pronunciations, translations, etc...
>>>>>>
>>>>>>
>>>>>> p.s. I was able to get the Kindle app to crash by clicking a link
>>>>>> inside one of the Wikipedia "previews" that wasn't stripped out 
>>>>>> correctly.
>>>>>> In other words, no app is safe from the edge cases of wikitext!
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> reading-wmf mailing list
>>>>>> reading-...@lists.wikimedia.org
>>>>>> https://lists.wikimedia.org/mailman/listinfo/reading-wmf
>>>>>>
>>>>>>
>>>>>
>>>>> ___
>>>>> reading-wmf mailing list
>>>>> reading-...@lists.wikimedia.org
>>>>> https://lists.wikimedia.org/mailman/listinfo/reading-wmf
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> EN Wikipedia user page:
>>>> https://en.wikipedia.org/wiki/User:Brian.gerstle
>>>> IRC: bgerstle
>>>>
>>>
>>> ___
>>> reading-wmf mailing list
>>> reading-...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/reading-wmf
>>>
>>>
>>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [reading-wmf] Wikipedia article previews in Kindle app

[Dmitry Brant]

+mobile-l


On Fri, Jun 5, 2015 at 11:23 AM, Adam Baso  wrote:

> Okay to move this to mobile-l?
>
>
> On Friday, June 5, 2015, Brian Gerstle  wrote:
>
>> While they strip out links/citations, they do preserve text formatting
>> (italics & bold).
>>
>> On Fri, Jun 5, 2015 at 10:39 AM, Bernd Sitzmann 
>> wrote:
>>
>>> Nice find. I also like being able to swipe those cards left/right
>>> between different information sources. Looks like depending on the selected
>>> words it's: Dictionary, Wikipedia, Translation
>>>
>>> On Thu, Jun 4, 2015 at 10:45 PM, Dmitry Brant 
>>> wrote:
>>>
>>>> I was using the Kindle app on the plane today, and I noticed a few
>>>> interesting things, including this:
>>>> ​
>>>>  device-2015-06-04-225651.png
>>>> <https://docs.google.com/a/wikimedia.org/file/d/0BzcksMsMNpY1SzA3bHY4WF9hM1U/edit?usp=drive_web>
>>>> ​
>>>> When highlighting a word or phrase, the user is presented with a
>>>> definition of the word from Wikipedia. The content is presented in a native
>>>> component, with only the first section of text shown (all links,
>>>> references, infoboxes, etc. are stripped out). (I wonder what API they're
>>>> using?)
>>>>
>>>> It looks very similar to the link preview prototypes we've been
>>>> developing in our apps, and it's very telling that the Kindle app has such
>>>> a feature, since it helps emphasize the usefulness of this feature in any
>>>> kind of "reader" app.  Perhaps, in addition to link previews, we may also
>>>> want to think about allowing users to highlight words and show definitions
>>>> (from Wiktionary?), pronunciations, translations, etc...
>>>>
>>>>
>>>> p.s. I was able to get the Kindle app to crash by clicking a link
>>>> inside one of the Wikipedia "previews" that wasn't stripped out correctly.
>>>> In other words, no app is safe from the edge cases of wikitext!
>>>>
>>>>
>>>> ___
>>>> reading-wmf mailing list
>>>> reading-...@lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/reading-wmf
>>>>
>>>>
>>>
>>> ___
>>> reading-wmf mailing list
>>> reading-...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/reading-wmf
>>>
>>>
>>
>>
>> --
>> EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle
>> IRC: bgerstle
>>
>
> ___
> reading-wmf mailing list
> reading-...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/reading-wmf
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] [Apps] Android app update

[Dmitry Brant]

Hi everyone,

We've released an update to the production Wikipedia Android app, which
will be rolled out to all Play Store users today. This is mostly a
maintenance release that takes care of the following enhancements and
issues:

* Improved handling of image map links
* Made sure the Share-a-fact button works on all devices
* Fixed sharing of images to Facebook app
* Improved "tap to expand" interaction for expandable tables
* Fixed text directionality consistency in Nearby
* Show "Read in other languages" only if article exists in other languages
* Fixed word wrapping when selecting from "Read in other languages"
* Added upside-down mode for devices that support it
* Fixed a few possible crashes

Enjoy!

-Dmitry
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Some EventLogging events failing validation

[Dmitry Brant]

[brain fart] it's in your email. :(  Thanks!

On Fri, May 15, 2015 at 3:59 PM, Dmitry Brant  wrote:

> Thanks for reporting this, Marcel!
> I've created a task for us to correct the behavior of our EL funnels:
> https://phabricator.wikimedia.org/T99276
>
> Is the actual character limit of EL messages specified somewhere?
>
>
> -Dmitry
>
>
> On Fri, May 15, 2015 at 3:41 PM, Marcel Ruiz Forns 
> wrote:
>
>> Hi Mobile,
>>
>> Analyzing EventLogging logs we percieved that a significant share of
>> MobileWikiAppSavedPages, MobileWikiAppArticleSuggestions and
>> MobileWikiAppShareAFact events are failing validation.
>>
>> *1) MobileWikiAppShareAFact: 1.5% not validating*
>> In this schema, the field "text" stores long fractions of text sometimes.
>> This exceeds the size limitation of EL, specially when the text contains
>> special characters, like chinese, greek, etc.
>>
>> *2) MobileWikiAppArticleSuggestions: 1% not validating*
>> In this case, it's the field "readMoreList" that is sometimes very long,
>> specially when it contains special characters.
>> This, again, exceeds the log size limit.
>>
>> *3) MobileWikiAppSavedPages: 1% not validating*
>> Some events do not contain the required field "appInstallID".
>>
>> In cases 1) and 2) the percentage is not big overall, but it can be that
>> for a given language, a lot of events are lost.
>>
>> EventLogging performance is not compromised by these validation errors,
>> but we are receiving monitoring alerts, and would like to maintain the
>> validation rate close to 100%.
>>
>> Is it possible for you to somehow reduce the size of the logs of 1) and
>> 2)?
>> If so, have in mind that the log size limit is 1k, and that the highest
>> priority for us would be 2).
>>
>> Thank you!
>>
>> Marcel
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Some EventLogging events failing validation

[Dmitry Brant]

Thanks for reporting this, Marcel!
I've created a task for us to correct the behavior of our EL funnels:
https://phabricator.wikimedia.org/T99276

Is the actual character limit of EL messages specified somewhere?


-Dmitry


On Fri, May 15, 2015 at 3:41 PM, Marcel Ruiz Forns 
wrote:

> Hi Mobile,
>
> Analyzing EventLogging logs we percieved that a significant share of
> MobileWikiAppSavedPages, MobileWikiAppArticleSuggestions and
> MobileWikiAppShareAFact events are failing validation.
>
> *1) MobileWikiAppShareAFact: 1.5% not validating*
> In this schema, the field "text" stores long fractions of text sometimes.
> This exceeds the size limitation of EL, specially when the text contains
> special characters, like chinese, greek, etc.
>
> *2) MobileWikiAppArticleSuggestions: 1% not validating*
> In this case, it's the field "readMoreList" that is sometimes very long,
> specially when it contains special characters.
> This, again, exceeds the log size limit.
>
> *3) MobileWikiAppSavedPages: 1% not validating*
> Some events do not contain the required field "appInstallID".
>
> In cases 1) and 2) the percentage is not big overall, but it can be that
> for a given language, a lot of events are lost.
>
> EventLogging performance is not compromised by these validation errors,
> but we are receiving monitoring alerts, and would like to maintain the
> validation rate close to 100%.
>
> Is it possible for you to somehow reduce the size of the logs of 1) and 2)?
> If so, have in mind that the log size limit is 1k, and that the highest
> priority for us would be 2).
>
> Thank you!
>
> Marcel
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Wikitech-l] Tracking Antifeature?

[Dmitry Brant]

The mobile apps (Android and iOS) do indeed collect anonymous usage
statistics [0].
For more information on what the usage reports contain, as well as other
topics such as app permissions, please refer to our FAQ [1].

[0]:
https://github.com/wikimedia/apps-android-wikipedia/blob/b316b11ba9f70d3adc8fc80825f931590f4e476a/wikipedia/src/main/java/org/wikipedia/analytics/EventLoggingEvent.java#L69-L73
[1]:
https://www.mediawiki.org/wiki/Wikimedia_Apps/FAQ#Offline_reading_and_data


On Thu, May 14, 2015 at 8:50 PM, Bryan Davis  wrote:

> On Thu, May 14, 2015 at 5:40 PM, Ricordisamoa
>  wrote:
> > FYI
> > https://f-droid.org/wiki/index.php?title=org.wikipedia&diff=54674
> > https://f-droid.org/wiki/page/Antifeature:Tracking
>
> Maybe for the ACRA [0] integration that emails crash reports to OTRS
> [1]? I think it asks if you want to send the report though.
>
> [0]: http://www.acra.ch/
> [1]:
> https://github.com/wikimedia/apps-android-wikipedia/blob/b316b11ba9f70d3adc8fc80825f931590f4e476a/wikipedia/src/main/java/org/wikipedia/WikipediaApp.java#L50-L56
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Hackathon: mobile apps meeting needs?

[Dmitry Brant]

A huge \o/




On Tue, May 12, 2015 at 11:02 AM, Bernd Sitzmann 
wrote:

> Antoine,
>
> Thank you for updating the Jenkins build to use the new Gradle build. This
> is great. Maybe we could get together later this week or at the Hackathon
> to also deal with running the tests?
>
> This is already a great improvement. We now have apk files build for each
> patch set, and send link to those to designers or QA if needed (before or
> after merge).
>
> We can now obsolete the Maven pom files, and restructure the folders to
> match a more Gradle standard folder structure.
>
> Thank you,
>
> Bernd
>
>
> Am 12.05.2015 11:11 schrieb "Antoine Musso" :
>
>> Le 11/05/2015 20:34, Bernd Sitzmann a écrit :
>> > I would like it if you could set up a Jenkins job for Android according
>> > to https://phabricator.wikimedia.org/T88494. No Gradle or Android SDK
>> > setup is needed!
>> 
>>
>> Thank you a ton Bernd to make it so trivial to build the app!
>>
>> Following our discussion yesterday and this morning, I have removed the
>> maven Jenkins job and replaced it with a couple gradle ones
>>
>>
>> From the task:
>>
>> ---8<--8<--8<--8<---
>> apps-android-wikipedia-gradlew
>>
>> ./gradlew -q clean checkstyle assembleAlphaDebug
>> Wich craft a checkstyle report.
>>
>> apps-android-wikipedia-gradlew-lint
>>
>> ./gradlew -q clean lintAlphaDebug
>> That fails for now and is made non voting. Once it is passing we can
>> move the lint goal to the other job. The lint job captures artifacts
>> under /build/outputs/ , there is apparently a Jenkins plugin to
>> interpret them (
>> https://wiki.jenkins-ci.org/display/JENKINS/Android+Lint+Plugin ) but
>> the site is down for now and there is no JJB support for it. So that
>> would be for later.
>>
>> I have send a dummy change https://gerrit.wikimedia.org/r/210289 which
>> yields:
>>
>> jshint SUCCESS in 1s
>> tox-flake8 SUCCESS in 6s
>> apps-android-wikipedia-gradlew   SUCCESS in 2m 40s
>> apps-android-wikipedia-gradlew-lint  FAILURE in 3m 03s (non-voting)
>> ---8<--8<--8<--8<---
>>
>>
>> Can be polished up later :)
>>
>>
>> --
>> Antoine "hashar" Musso
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikipedia Zero editing

[Dmitry Brant]

I would be surprised (and perplexed) if this is the case. At least in apps,
both reading and editing are done via API requests, which are in turn
performed over https. The carrier would have no way of knowing what packets
are "editing" vs. "reading".


On Mon, May 4, 2015 at 8:49 AM, Amir E. Aharoni <
amir.ahar...@mail.huji.ac.il> wrote:

> Hi,
>
> Is Wikipedia Zero only for reading, or for editing, too?
>
> I noticed this Twitter conversation today:
> https://twitter.com/thornet/status/594837690778034176
>
> It says that it's only for reading.
>
> If it's true, is there a reason for this?
>
> I don't know about images and videos, but I imagine that the costs for
> editing traffic would be negligible to the carriers and it will create a
> lot of, um, good karma for everybody.
>
> --
> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> http://aharoni.wordpress.com
> ‪“We're living in pieces,
> I want to live in peace.” – T. Moore‬
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] iOS Engineering Review Meeting

[Dmitry Brant]

Probably good to institute this for Android, as well. (On a monthly basis,
I would think)


On Tue, Mar 31, 2015 at 6:16 PM, Tomasz Finc  wrote:

> Excellent. Keep mailing out post those to share good practices. thanks
> teams.
>
> On Tue, Mar 31, 2015 at 3:11 PM, Jon Robson  wrote:
> > We have the developer pow wow for the mobile web team where we get
> together
> > every month and share tools, best practices, ideas. We've been doing this
> > since the end of January. (See "Team session notes" from Joaquin for
> notes
> > on the first one). I thoroughly recommend this practice it's been super
> > useful so far.
> >
> >
> > On Tue, Mar 31, 2015 at 3:00 PM, Tomasz Finc 
> wrote:
> >>
> >> This is a great practice.
> >>
> >> Gather & WikiGrok, are you already doing something similar to stay in
> >> sync?
> >>
> >> --tomasz
> >>
> >> On Fri, Mar 27, 2015 at 2:54 PM, Brian Gerstle 
> >> wrote:
> >> > Hey everyone,
> >> >
> >> > The iOS engineers had our regular "review" meeting today, where we
> >> > discuss
> >> > team practices and topics in the industry.  We've started taking
> minutes
> >> > for
> >> > future reference, and of course to keep in touch with all of you!
> >> >
> >> > The main page for the meeting is
> >> >
> >> > Wikimedia_Apps/Team/iOS/Engineering_Review
> >> >
> >> > and today's minutes can be found at
> >> >
> >> > Wikimedia_Apps/Team/iOS/Engineering_Review/March_27_2015.
> >> >
> >> > Topics discussed were: system dependencies being installed via the
> >> > Makefile
> >> > and our code review practices.
> >> >
> >> > Have a great weekend!
> >> >
> >> > Brian
> >> >
> >> > --
> >> > EN Wikipedia user page:
> https://en.wikipedia.org/wiki/User:Brian.gerstle
> >> > IRC: bgerstle
> >> >
> >> > ___
> >> > Mobile-l mailing list
> >> > Mobile-l@lists.wikimedia.org
> >> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >> >
> >>
> >> ___
> >> Mobile-l mailing list
> >> Mobile-l@lists.wikimedia.org
> >> https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
> >
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Description editing prototype testing

[Dmitry Brant]

Excellent! Thanks for putting this together.



On Thu, Mar 26, 2015 at 12:13 PM, Daisy Chen  wrote:

> Hi all,
> Please find the goals for and top-level findings from guerrilla testing
> description editing on Wikipedia Alpha below. More in-depth information
> including tasks/questions posed and raw notes on the 5 participants can be
> found here
> .
> There may be typos and small formatting errors (I'll be proofing the page
> in the next hour).
> Happy quarterly planning--Daisy
> ---
> Goal
>
> The goal of this research was to observe people interact with the CTA
> ("Tap to add a description!") line in the header under article titles in
> Wikipedia Alpha. After tapping the CTA, users experience 3 editable
> scenarios: 1. an meaningful description suggestion, 2. a blank form field,
> and 3. a random/irrelevant description suggestion.
>
>1. Do users notice the CTA prompt? How effective are they in
>triggering action?
>2. How do users feel about the CTA?
>3. How effective are descriptions that are auto-generated and
>meaningful? Do they assist users with finalizing the description or confuse
>users as to why they are prompted to edit a description that is already
>automated and correct?
>4. How effective is not giving a user a pre-populated description
>field?
>5. How effective are descriptions that are auto-generated and random?
>6. How do users feel about the process of editing description lines
>overall?
>
> Findings: Patterns Observed
>
>1. 3 of 5 users required some level of facilitator prompting to notice
>the CTA.
>2. Interactivity breakdown:
>   1. 2 users would most likely overlook this field, 2 users might
>   notice/interact depending on the situation, and 1 user was not sure.
>3. All users either specifically indicated field interaction was easy
>and intuitive or had no specific complaint or struggle that was observed.
>Only 1 user was briefly confused about the blank SF description field,
>thinking he couldn't type because he didn't see a blinking cursor.
>4. 3 scenarios feedback breakdown
>   1. Meaningful description suggestion
>  1. most helpful: 2 users
>  2. most helpful, but pointless because I can't see it on page: 1
>  user
>  3. confusing: 1 user
>   2. Blank
>  1. fine if you know about topic: 1 user
>  2. fine and having the CTA here made most sense: 1 user
>  3. most engaging: 1 user
>  4. easiest: 1 user
>   3. Random/irrelevant description suggestion
>  1. if visible, could prompt action: 2 users
>   5. 2 of 5 users expressed some level of confusion around why the
>CTA hides the description. One user was confused about why he was prompted
>to action when the description was correct on Picasso. Another user was
>confused about the same thing, and also mentioned that he would be much
>more likely to take action on the random article if he could see that the
>description was incorrect. The latter also mentioned that the CTA really
>only makes sense on the SF blank description page.
>6. 1 user was confused about whether these descriptions were for
>himself or for all of Wikipedia.
>7. No users indicated confusion about the CTA pop-up language.
>
>
> --
> Daisy Chen
> Wikimedia Foundation
>
> Imagine a world in which every single human being can freely share in
> the sum of all knowledge. Help us make it a reality!
>
> *https://donate.wikimedia.org *
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Android Wikipedia Beta app update

[Dmitry Brant]

Good news, everyone!
The latest version of the Beta app[1] has been released, and will be
available on the Play Store shortly. Some highlights from this version:

- Improved layout and styling of Share-a-fact cards.
- Enabled caching of pages on internal/external storage of the device
(should improve memory usage and fix out-of-memory errors).
- Updated launcher icon and miscellaneous Material design elements in the
app.
- Updated for the latest Android SDK version.
- Fixed miscellaneous bugs and updated translations.

Best,

Dmitry

[1] https://play.google.com/store/apps/details?id=org.wikipedia.beta
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikidata descriptions: ruminations

[Dmitry Brant]

Hi Monte!
inline:

> Deeply hard, in fact, because it's complicated not only by language
syntax and grammatical rules, but also by qualitative factors (readability,
meaning, context, relevance etc).
> This already complicated situation then becomes many orders of magnitude
more difficult because these qualitative factors can differ between
languages.

Again, I agree that this is not an easy problem. However, in the case of
language translations, automated descriptions have the potential of
simplifying things tremendously. The algorithm for the grammar and syntax
of a certain language needs to be written only once. And once it's written,
it can be applied to every Wikidata item, past and future. Sure, there
would likely be a different algorithm for each language, and maybe even
different algorithms for various taxa of Wikidata items.  But this kind of
solution simply feels more scalable, and I'm surprised that researching
methods of accomplishing this are of little interest.


> I predict this won't be any worse than what happened when we enabled
section editing.

But when we enabled section editing, did we do it with a prominent call to
action? I just feel a little hesitation about going full-on with something
like this, without having a baseline level of administrative feedback in
the apps (e.g. a notification for when a description is reverted, and the
reason for it).

To be clear, of course I'm totally on board for experimenting with allowing
users to contribute descriptions. Making bold moves is what makes our team
so great. My goal is simply to point out various other solutions that, to
me, make slightly more sense (and to welcome feedback on why they don't!).


> But reducing the first sentence in this way is deceptively complicated to
do programmatically, precisely because of the word "arguably" in the
preceding sentence - it's almost entirely a matter of qualitative
judgement. You have to know what a fish is to know what parts of the first
sentence are most important

That's almost convincing :) but still... why duplicate content when the
essential information is already there?
Maybe I didn't convey my idea of "markup" for extracting a description
properly. For example, the description for the [[Fish]] article can be
marked up as follows:

A fish is any member of a paraphyletic group of organisms that consist of
all ***gill-bearing aquatic craniate animal***s
that lack limbs with digits.

The above markup would be done by a human editor, with the knowledge that
the text within the  tag will end up as the Wikidata
description.  I would wager that a similar scheme could be applied to any
number of articles. Let's try it for a few random articles:

[[Poland]]
Poland (Polish: Polska; pronounced [ˈpɔlska] ( listen)), officially the
Republic of Poland (Polish: Rzeczpospolita Polska; pronounced
[ʐɛt͡ʂpɔˈspɔʎit̪a ˈpɔlska] ( listen)), is a ***country in
Central Europe*** bordered by Germany to the west; the Czech
Republic and Slovakia to the south...

[[Schadenfreude]]
Schadenfreude (/ˈʃɑːdənfrɔɪdə/; German: [ˈʃaːdn̩ˌfʀɔɪ̯də] ( listen)) is
***pleasure derived from the misfortunes of others*
**.[1] This word is taken from German...

[[Ming dynasty]]
The Ming dynasty, also Empire of the Great Ming, was the ***ruling
dynasty of China for 276 years (1368–1644)*** following the
collapse of the Mongol-led Yuan dynasty...

[[Homomorphism]]
In abstract algebra, a homomorphism is a ***structure-preserving
map between two algebraic structures*** (such as groups,
rings, or vector spaces)...

^^ What would be the downside(s) of doing something like that?



On Sun, Mar 22, 2015 at 9:37 PM, Monte Hurd  wrote:

> My previous reply was partial and accidentally sent - here's my actual
> reply :)
>
>
>
>
> On Sun, Mar 22, 2015 at 1:53 PM, Dmitry Brant 
> wrote:
>
>> Hi Lydia,
>>
>> Indeed, there are many more Wikidata items than Wikipedia articles.
>> However, the users of our mobile apps only see Wikipedia articles in our
>> search results (at least for now), which means that they will only be able
>> to contribute descriptions to Wikidata items for which a Wikipedia article
>> exists.
>>
>>
>
>
> They are also used in "*Recent*" and  "*Nearby*" and Vibha wants them in 
> "*Saved
> Pages*" list as well.
>
>
>
>
>
>> No doubt, the description field is an important component of each
>> Wikidata entry.  But, when there is a corresponding Wikipedia article, why
>> not query it to provide an automatic description? This could be based on
>> the first sentence of the article, or a subset of the first sentence, or
>> some other kind of metadata within the article.
>>
>
>
>
>
> Why not query it to provide an automatic description? Because finding the
>

Re: [WikimediaMobile] Wikidata descriptions: ruminations

[Dmitry Brant]

Hi Lydia,

Indeed, there are many more Wikidata items than Wikipedia articles.
However, the users of our mobile apps only see Wikipedia articles in our
search results (at least for now), which means that they will only be able
to contribute descriptions to Wikidata items for which a Wikipedia article
exists.

No doubt, the description field is an important component of each Wikidata
entry.  But, when there is a corresponding Wikipedia article, why not query
it to provide an automatic description? This could be based on the first
sentence of the article, or a subset of the first sentence, or some other
kind of metadata within the article. The key is that the description would
stay with the article, which would eliminate the need for duplication and
synchronization.

So, in a sense, I would look at it the other way: descriptions within
Wikipedia articles would be useful for Wikidata entries.

-Dmitry

On Sun, Mar 22, 2015 at 4:17 PM, Lydia Pintscher <
lydia.pintsc...@wikimedia.de> wrote:

> On Sun, Mar 22, 2015 at 9:10 PM, Dmitry Brant 
> wrote:
> > Hi Jane,
> >
> > Perhaps my comments came off as more pessimistic than I intended. Of
> course
> > I believe in the power of crowdsourcing, and I would never want to make
> > anyone feel like their contributions are being marginalized.
> >
> > I'll agree for now that the idea of "fully" automated descriptions leans
> > more towards science fiction than reality. :)
> >
> > However, my whole point has more to do with the apparent duplication of
> > content that seems to be happening between the first sentence of
> Wikipedia
> > articles and the corresponding Wikidata description.  There's something
> > about it that seems unnecessary.  If we can figure out a way to
> > automatically extract the description from the first sentence of the
> > article, it would simplify things in two ways:
> >
> > 1) People wouldn't need to edit Wikidata descriptions, and would instead
> > focus on improving the Wikipedia article.
> > 2) People who monitor changes made to articles would need to monitor only
> > the article, instead of the article plus its corresponding Wikidata
> > description.
>
> There are a lot more items on Wikidata than articles on Wikipedia. And
> not every language has a Wikipedia article for each item. Don't just
> look at descriptions on Wikidata as something useful for Wikipedia.
> They're much more than that.
>
>
> Cheers
> Lydia
>
> --
> Lydia Pintscher - http://about.me/lydia.pintscher
> Product Manager for Wikidata
>
> Wikimedia Deutschland e.V.
> Tempelhofer Ufer 23-24
> 10963 Berlin
> www.wikimedia.de
>
> Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
>
> Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
> unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
> Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikidata descriptions: ruminations

[Dmitry Brant]

Hi Jane,

Perhaps my comments came off as more pessimistic than I intended. Of course
I believe in the power of crowdsourcing, and I would never want to make
anyone feel like their contributions are being marginalized.

I'll agree for now that the idea of "fully" automated descriptions leans
more towards science fiction than reality. :)

However, my whole point has more to do with the apparent duplication of
content that seems to be happening between the first sentence of Wikipedia
articles and the corresponding Wikidata description.  There's something
about it that seems unnecessary.  If we can figure out a way to
automatically extract the description from the first sentence of the
article, it would simplify things in two ways:

1) People wouldn't need to edit Wikidata descriptions, and would instead
focus on improving the Wikipedia article.
2) People who monitor changes made to articles would need to monitor only
the article, instead of the article plus its corresponding Wikidata
description.

-Dmitry


On Sun, Mar 22, 2015 at 3:29 PM, Jane Darnell  wrote:

> I agree with Monte Hurd and would add that my personal volunteer time on
> Wiki projects, though unique, is not irreplaceable, and the idea that I and
> others interested in my area of editing could be "overworked" by some new
> technology is just silly. I think you need to have a little faith in the
> whole concept of crowd-sourcing. It really does seem to work. Automated
> descriptions sounds like a terrible idea and I have seen time and again on
> all sorts of subjects that the main claim to fame switches across
> languages. An example is a language -pedia that has added a town because it
> is the location of a castle that is notable in that language -pedia for
> whatever reason, while in the language -pedia of the town itself, the town
> may be better known as a hub on a railway network or some such thing.
>
> On Sun, Mar 22, 2015 at 8:08 PM, Monte Hurd  wrote:
>
>> Responses inline...
>>
>>
>>
>> > On Mar 22, 2015, at 8:57 AM, Dmitry Brant  wrote:
>> >
>> > In preparation for next week's quarterly planning, I'd like to restate
>> some of my concerns regarding Wikidata descriptions and flesh them out more
>> comprehensively, since we're featuring them more prominently in the
>> upcoming quarter.
>> > (n.b. These are more like "devil's advocate" thoughts, lest I make it
>> sound like the Apps team isn't unified in its vision, which it certainly
>> is.)
>> >
>> > My reservations fall under two categories:
>> >
>> > == Philosophical ==
>> >
>> > Wikidata is a superbly valuable repository of *data* -- data that a
>> machine can use to generate all kinds of results that us humans can
>> consume. The "description" field, on the other hand, is the only thing that
>> is *not* data, and is not usable by a machine in any way.
>> >
>> > To allow users to manually fill in the Wikidata description (i.e. to
>> manually duplicate the contents of Wikipedia) is to miss the point of the
>> true potential of Wikidata, which is to be able to *use* the data to
>> generate the description automatically!
>> >
>>
>>
>> I disagree with the premise that the description being "data" means it is
>> missing its promise if it is human curated. I am more concerned with the
>> quality of the description.
>>
>>
>>
>>
>> > Of course the counterargument to this is that the current state of
>> auto-generated descriptions is not quite good (they often sound strange or
>> nonsensical), but that's only because the tools we have at our disposal for
>> generating descriptions are still in their infancy. I don't deny that this
>> will be a hard problem to solve, but in my view, this is ultimately the
>> *correct* problem to solve.
>> >
>>
>>
>>
>> It's surprisingly hard to create auto generated descriptions that rival
>> the quality of user generated descriptions.
>>
>> Deeply hard, in fact, because it's complicated not only by language
>> syntax and grammatical rules, but also by qualitative factors (readability,
>> meaning, context, relevance etc).
>>
>> This already complicated situation then becomes many orders of magnitude
>> more difficult because these qualitative factors can differ between
>> languages.
>>
>>
>>
>>
>>
>> > The other thing (a more obvious one) that makes Wikidata descriptions
>> redundant is the first sentence of every Wikipedia article which, on its
>> own, is intended to provid

[WikimediaMobile] Wikidata descriptions: ruminations

[Dmitry Brant]

In preparation for next week's quarterly planning, I'd like to restate some
of my concerns regarding Wikidata descriptions and flesh them out more
comprehensively, since we're featuring them more prominently in the
upcoming quarter.
(n.b. These are more like "devil's advocate" thoughts, lest I make it sound
like the Apps team isn't unified in its vision, which it certainly is.)

My reservations fall under two categories:

== Philosophical ==

Wikidata is a superbly valuable repository of *data* -- data that a machine
can use to generate all kinds of results that us humans can consume. The
"description" field, on the other hand, is the only thing that is *not*
data, and is not usable by a machine in any way.

To allow users to manually fill in the Wikidata description (i.e. to
manually duplicate the contents of Wikipedia) is to miss the point of the
true potential of Wikidata, which is to be able to *use* the data to
generate the description automatically!

Of course the counterargument to this is that the current state of
auto-generated descriptions is not quite good (they often sound strange or
nonsensical), but that's only because the tools we have at our disposal for
generating descriptions are still in their infancy. I don't deny that this
will be a hard problem to solve, but in my view, this is ultimately the
*correct* problem to solve.

The other thing (a more obvious one) that makes Wikidata descriptions
redundant is the first sentence of every Wikipedia article which, on its
own, is intended to provide a concise description of the article (and many
articles already do this with rather good consistency). In fact, as we
speak, we're working on programmatically "cleaning up" the first sentence
to make it even more concise. Why not simply use this as the description?

Is the first sentence sometimes too long to be a good description? No
problem: create a markup annotation that will denote the *portion* of the
first sentence that will serve as the description. In any case, making
users manually copy the content from the first sentence (which is from
where most of the current Wikidata descriptions appear to be derived) seems
extraordinarily unnecessary.  On top of all that, it creates an unnecessary
synchronization cost, fulfillable only by a human contributor, between the
two sources of data.

So, what I mean to say is: every edit to the Wikidata description is a
missed opportunity to edit the Wikipedia article in such a way that the
description could be auto-generated correctly. (or, similarly, a missed
opportunity to edit the *data* of the Wikidata entry in such a way that the
description could be auto-generated correctly)

== Practical ==

If we open the floodgates to editing the Wikidata description (i.e. if we
make it too easy to edit the description), I predict that we'll be very
disappointed by the quality of the contributions we'll get. I can see it
quickly devolving into a whole lot of noise, spam, and vandalism.

This means that we would need to implement the same kind of
moderation/administration schemes that currently exist on Wikipedia
itself.  I'm by no means qualified to speak for the Community, but I doubt
that many Wikipedians will want to double their workload by having to
"watch" the Wikidata description of their favorite articles, in addition to
the articles themselves.

I'll also point out that we do not yet expose any administrative mechanisms
in the mobile apps.  This means that users will routinely see their edits
disappear or be reverted without any notification or explanation.  This is
already the case for the general editing of article content in the apps,
but since the description is featured much more prominently, any edits (or
reverts) to it will be much more noticeable, and will surely add to the
confusion and frustration.
If we really want to get it right, we have to figure this out before
proceeding.


-Dmitry
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Google Now cards?

[Dmitry Brant]

Tracked here:
https://phabricator.wikimedia.org/T91512



On Mon, Mar 16, 2015 at 6:16 AM, Magnus Manske 
wrote:

>
> http://www.androidcentral.com/any-third-party-app-will-soon-be-able-access-google-now-api
>
> Something for the mobile app? Nearby (Wikidata?) items? With images to
> show, or without images - for the user to snap? Article of the day?
> Most-edited articles in the last X hours?
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Improving Android release cadence

[Dmitry Brant]

Well, technically all of the new features we're currently developing are
properly flagged. So there's nothing blocking a production release (based
on the current Beta tag) (Bernd, correct me if I'm wrong).
I think the only remaining hesitation at this point is the lack of a
formalized QA process. This is what instills a sense of apprehension
towards making a production release, and pushes the idea of a release to
the back of our minds, until it reaches an arbitrary critical mass.


On Thu, Mar 12, 2015 at 5:01 PM, Dan Garry  wrote:

> So it sounds like we have agreement on using feature flags for our
> features, with the aim of increasing our cadence.
>
> What are our next steps now?
>
> Dan
>
> On 11 March 2015 at 14:01, Dmitry Brant  wrote:
>
>> Yeah, I'll make sure to listen to the podcast, but generally I'm on the
>> side of feature flags.
>>
>>
>>
>> On Wed, Mar 11, 2015 at 4:58 PM, Corey Floyd 
>> wrote:
>>
>>> Yeah - after listening to the podcast I was on the fence about it too… I
>>> think they bring up good points on the tradeoffs of both (even the hosts
>>> were split on their preference at the end).
>>>
>>> I was initially attracted towards the git methodology as it gets these
>>> business decisions out of the code base - but I also think that having
>>> these flags that work at runtime (from a debug menu) is really valuable for
>>> testing purposes.
>>>
>>> One thing I am not convinced on is that there will be "less work at the
>>> end" when integrating features into a release with the feature flag
>>> methodology - I feel like that could still be a problem if you are not
>>> merging/rebasing. They discussed this in the podcast almost as an aside -
>>> but it is entirely possible to develop conflicting features using feature
>>> flags if developers do not coordinate (I feel this is really an orthogonal
>>> issue to enabling features).
>>>
>>> Still - I think the feature flag solution has promise - but I am way
>>> more interested in it if we do it as run time option to get the testing/QA
>>> benefits.
>>>
>>>
>>> On Wed, Mar 11, 2015 at 4:08 PM, Bernd Sitzmann 
>>> wrote:
>>>
>>>> I have not listened to the podcast yet, but my opinion is similar to
>>>> what Brian described.
>>>> So, +1 for feature flags.
>>>>
>>>> Bernd
>>>>
>>>> On Wed, Mar 11, 2015 at 1:40 PM, Brian Gerstle 
>>>> wrote:
>>>>
>>>>> Listened to it this morning, gotta say I think I'm on "Team Flag," if
>>>>> it's done well.  IMO we should try one (or both) and see how it goes.
>>>>> Here's my take on each approach:
>>>>>
>>>>> Branches are cheap to implement, but come at the a potentially high
>>>>> cost if you don't continually rebase and try to keep the work scope as
>>>>> small as possible.  At a previous job we used git submodules as pseudo
>>>>> feature branches.  There were common problems w/ dependencies between
>>>>> branches and between branches and the main repo, which as the hosts 
>>>>> mention
>>>>> are often pushed later in the process.
>>>>>
>>>>> Flags are more expensive to implement up front, but allow for truly
>>>>> continuous integration and delivery—as well as the potential for gradual
>>>>> rollout.  IMO it could also lead to better architected code since feature
>>>>> flags require you to codify the boundaries between the "platform" and the
>>>>> features (and between the features themselves).  You also need to limit
>>>>> global state and have good test coverage (which we should do anyway) in
>>>>> order to keep undesired side-effects to a minimum.  My previous job also
>>>>> switched to this model and was able to improve their release cadence and
>>>>> sync between features (IIRC, don't have any concrete evidence to back it 
>>>>> up
>>>>> unfortunately).
>>>>>
>>>>>
>>>>> On Tue, Mar 10, 2015 at 11:16 PM, Corey Floyd 
>>>>> wrote:
>>>>>
>>>>>> As luck would have it, a very good tech podcast I subscribe
>>>>>> to recently discussed this subject. It is a pretty good listen and
>>>>>> discusses trade offs for both feature flags and branching.
>>>>&

Re: [WikimediaMobile] [Apps] Improving Android release cadence

[Dmitry Brant]

Yeah, I'll make sure to listen to the podcast, but generally I'm on the
side of feature flags.



On Wed, Mar 11, 2015 at 4:58 PM, Corey Floyd  wrote:

> Yeah - after listening to the podcast I was on the fence about it too… I
> think they bring up good points on the tradeoffs of both (even the hosts
> were split on their preference at the end).
>
> I was initially attracted towards the git methodology as it gets these
> business decisions out of the code base - but I also think that having
> these flags that work at runtime (from a debug menu) is really valuable for
> testing purposes.
>
> One thing I am not convinced on is that there will be "less work at the
> end" when integrating features into a release with the feature flag
> methodology - I feel like that could still be a problem if you are not
> merging/rebasing. They discussed this in the podcast almost as an aside -
> but it is entirely possible to develop conflicting features using feature
> flags if developers do not coordinate (I feel this is really an orthogonal
> issue to enabling features).
>
> Still - I think the feature flag solution has promise - but I am way more
> interested in it if we do it as run time option to get the testing/QA
> benefits.
>
>
> On Wed, Mar 11, 2015 at 4:08 PM, Bernd Sitzmann 
> wrote:
>
>> I have not listened to the podcast yet, but my opinion is similar to what
>> Brian described.
>> So, +1 for feature flags.
>>
>> Bernd
>>
>> On Wed, Mar 11, 2015 at 1:40 PM, Brian Gerstle 
>> wrote:
>>
>>> Listened to it this morning, gotta say I think I'm on "Team Flag," if
>>> it's done well.  IMO we should try one (or both) and see how it goes.
>>> Here's my take on each approach:
>>>
>>> Branches are cheap to implement, but come at the a potentially high cost
>>> if you don't continually rebase and try to keep the work scope as small as
>>> possible.  At a previous job we used git submodules as pseudo feature
>>> branches.  There were common problems w/ dependencies between branches and
>>> between branches and the main repo, which as the hosts mention are often
>>> pushed later in the process.
>>>
>>> Flags are more expensive to implement up front, but allow for truly
>>> continuous integration and delivery—as well as the potential for gradual
>>> rollout.  IMO it could also lead to better architected code since feature
>>> flags require you to codify the boundaries between the "platform" and the
>>> features (and between the features themselves).  You also need to limit
>>> global state and have good test coverage (which we should do anyway) in
>>> order to keep undesired side-effects to a minimum.  My previous job also
>>> switched to this model and was able to improve their release cadence and
>>> sync between features (IIRC, don't have any concrete evidence to back it up
>>> unfortunately).
>>>
>>>
>>> On Tue, Mar 10, 2015 at 11:16 PM, Corey Floyd 
>>> wrote:
>>>
 As luck would have it, a very good tech podcast I subscribe to recently
 discussed this subject. It is a pretty good listen and discusses trade offs
 for both feature flags and branching.


 http://edgecasesshow.com/123-whats-the-deal-with-nsinteger.html

 (Topic is covered in the 2nd half of the show)


 On Monday, March 9, 2015, Dan Duvall  wrote:

> One very simple model that I think works well with distributed
> software (and should play somewhat nice with Gerrit) is to branch per 
> minor
> release (assuming somewhat semantic versioning). In this model, master can
> continue to serve as an integration branch, bug fixes are developed 
> against
> the release branch and merged following each patch release, and features
> are developed against master per usual. With Gerrit in the mix, you're
> essentially left with a two-stage merge for bug fixes which can be a bit 
> of
> extra work to get them merged into master, but at least the pipeline is
> greased for getting them released.
>
> I can't say whether this would fit your team's workflow and, as Corey
> mentioned, there are many different branching models to consider, each 
> with
> its own focus and drawbacks.[1][2] The one I've outlined above is geared
> more for stability and maintenance but can probably be tweaked for more
> frequent releases of features as well. I'm happy to brainstorm further.
>
> [1]
> http://blog.codinghorror.com/software-branching-and-parallel-universes/
> [2] https://msdn.microsoft.com/en-us/library/bb668955.aspx
>
>
> On Mon, Mar 9, 2015 at 2:30 PM, Corey Floyd 
> wrote:
>
>> Feature flags would help, but they also add an extra development
>> investment to make sure all features are engineered in a way that a flag
>> can shut them off without other bad things happening (not necessarily a 
>> bad
>> thing, but require more effort).
>>
>> Another route to go is to manage this in git using the bra

Re: [WikimediaMobile] Problem i met with wikimedia_android app

[Dmitry Brant]

Greetings,

Thanks for your interest in the Android app!
Technically we do not yet officially support using the app with arbitrary
MediaWiki installations, which is why our documentation for doing this is a
bit lacking at the moment.  However, there's no reason it couldn't be done,
and it sounds like you're 90% there.

At a minimum, you would need to install the MobileFrontend extension:
https://www.mediawiki.org/wiki/Extension:MobileFrontend
(the above page also discusses how to get Nearby working)

...and the MobileApp extension:
https://www.mediawiki.org/wiki/Extension:MobileApp

It sounds like you've correctly modified Site.java to point to the IP
address of your installation (since you're able to log in from the app), so
installing the above extensions may be the only thing left to do.

Let us know if you have additional questions!
Best,

Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering


On Wed, Mar 11, 2015 at 9:34 AM, cxysh...@yeah.net 
wrote:

> hi there:
> i really need help for my wikimedia_android app.  it is not easy to
> study the project ,since i don't know where i can get the design documents
> about the android app . i have study wikimedia_android app for about a
> month(download from https://github.com/wikimedia/apps-android-wikipedia)
> ,i also build a mediaWiki (download from
> https://www.mediawiki.org/wiki/Download) on my wampserver *(i didn't
> install any extentions on mediaWiki,i don't know what Extentions i need to
> install)* . In left menu of app ,there are functions such as : Log in ,
> Today , History ,Saved pages ,Nearby ,Random
>
>   * What i want to do* is that i tried to build my own android app which
> will connect to my local mediaWiki server (192.167.137.1) to get all the
> data the app need.And all the functions (Log in , Today , History ,Saved
> pages ,Nearby ,Random ) work well.
>
>*What i have done : *i modify the  domain = "192.168.137.1",  language
> ="zh"  in Site.java because of that my app can register and login ,app
> communicates well with my local mediaWiki server. and it will show my
> username in left menu.
>
>
>*Problem i met: *after i click "Today" ,the page of Today did not
> display on my android phone and i got these message :
> 03-11 15:35:46.176 31202-31202/org.wikipedia.alpha D/Wikipedia﹕ Using
> packaged styles
> 03-11 15:35:46.201 31202-31202/org.wikipedia.alpha W/AwContents﹕
> nativeOnDraw failed; clearing to background color.
> 03-11 15:35:46.261 31202-31202/org.wikipedia.alpha D/Wikipedia﹕ Using
> packaged styles
> 03-11 15:35:46.276 31202-31202/org.wikipedia.alpha W/AwContents﹕
> nativeOnDraw failed; clearing to background color.
> 03-11 15:35:46.636 31202-31202/org.wikipedia.alpha I/chromium﹕
> [INFO:async_pixel_transfer_manager_android.cc(60)] Async pixel transfers
> not supported
>
>  * here is my question:*
>   *1:*  I don't know what happened ,why the page of "Today" did not
> display ?
>   *2:*  Is that because I didn't install any extentions on my local
> mediaWiki ? I saw "Mobile Web" and "Extension:MobileFrontend" in
> https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering .If that true
> ,what Extentions do i need to install and how ?
>   *3: *Or maybe i need to write some php program in my local mediaWiki server
> ? because it is my local server not Wikipedia server which may have some
> php program achieved by it's team
>   *4:* the function "Nearby"  and "Random" also didn't work,is that the
> same reason with "Today" ? if not ,what maybe the reasons ?
>  * 5*: Are there design  and api documents about the *android ap*p , and
> where i can get the documents ?
>   *6*: Are there design  and api documents about the *mediaWiki* , and
> where i can get the documents ?
>
>I am now really confused with the project  ,i have  been working on
> that problem for two days but get nothing, I really hope someone can help .
>
>   thanks a lot !
>   shine
>
> --
> cxysh...@yeah.net
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android Arsenal: libraries for Android dev

[Dmitry Brant]

Excellent find (especially [2]); thanks!



On Thu, Mar 5, 2015 at 11:31 AM, Bernd Sitzmann  wrote:

> FYI, while searching for Android libraries I came across the Android
> Arsenal site[1], which is a directory of libraries for Android.
> Warning: I admit it got me a bit sidetracked because of all the
> interesting links there.
> On there it also has some best practices and pattern links. One of the
> many I like is [2]. My Design layout attributes patch[3] was inspired by
> it. I couldn't resist.
>
> -Bernd
>
> [1] https://android-arsenal.com/demo?sort=rating
> [2] https://github.com/futurice/android-best-practices
> [3] https://gerrit.wikimedia.org/r/#/c/194263/
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android Wikipedia beta app release

[Dmitry Brant]

Yeah, the problem with widgets is that they're not very discoverable.  A
more worthwhile effort might be to integrate better with Google Now, so
that our content would be exposed whenever the user performs any kind of
search from the device.



On Sat, Feb 21, 2015 at 4:56 PM, Dan Garry  wrote:

> On 19 February 2015 at 14:15, Tomasz Finc  wrote:
>>
>> How difficult would it be to allow the feature article widget to be
>> resizable so that we can showcase a snippet of text and an image?
>>
>
> I'm glad you like the widgets!
>
> Before investing any more resources into widgets, we'll need to see how
> much they're used relative to our other features. We suspect that they will
> not be used much, but chose to prioritise getting them out because Dmitry
> already had a proof of concept patch ready which just needed some minor
> design polishing.
>
> Dan
>
> --
> Dan Garry
> Associate Product Manager, Mobile Apps
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Fwd: [Android app] Memory profiling results

[Dmitry Brant]

cc mobile-l

-- Forwarded message --
From: Dmitry Brant 
Date: Wed, Feb 18, 2015 at 10:51 AM
Subject: [Android app] Memory profiling results
To: mobile-tech 


I've been doing some memory profiling of the Android app.  The good news is
that we don't have any glaring resource leaks. However, we do have plenty
of room for improvement in our general memory usage.  I've written up some
of the key takeaways in this page (feel free to comment!):
https://www.mediawiki.org/wiki/Wikimedia_Apps/Android/Memory_usage

...and I've created these corresponding Phab tasks:
https://phabricator.wikimedia.org/T89826
https://phabricator.wikimedia.org/T89828
https://phabricator.wikimedia.org/T89831
https://phabricator.wikimedia.org/T89834
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Open Source Third Party Libraries in iOS

[Dmitry Brant]

I would imagine that the Android team will adopt these criteria, as well.
It hasn't been much of an issue so far, since we've only needed to import
one new library within the last year, but it will be good to have these
guidelines specified officially.

-Dmitry


On Thu, Feb 12, 2015 at 9:37 PM, Dan Garry  wrote:

> Looks good.
>
> Is this currently being trialled as a set of criteria which will then also
> be adopted by the Android guys as well, or are they drafting their own
> criteria?
>
> Dan
>
> On 12 February 2015 at 16:46, Adam Baso  wrote:
>
>> Following up, here's where we arrived:
>>
>>
>> https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS/Third_Party_Libraries
>>
>> -Adam
>>
>> On Wed, Feb 11, 2015 at 9:37 AM, Adam Baso  wrote:
>>
>>> The apps crew is going to be having a meeting to go over third party
>>> library usage in iOS. We're currently use CocoaPods for package management.
>>>
>>> In advance of that meeting tomorrow, anybody have advice we should
>>> consider?
>>>
>>> -Adam
>>>
>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
>
> --
> Dan Garry
> Associate Product Manager, Mobile Apps
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Fwd: [Wikidata-l] descriptions in mobile app

[Dmitry Brant]

Sure, I won't deny that it would still need a lot of work, but I still see
it as a logical next step.


On Mon, Feb 9, 2015 at 11:41 AM, Max Semenik  wrote:

> Eh, please don't - have you tried it for languages other than English?
> 09 февр. 2015 г. 5:55 пользователь "Dmitry Brant" 
> написал:
>
> Awesome! I would love to see the output of AutoDesc be returned by the
>> API, when a manual description is not available.
>> I would also be a strong proponent of fully auto-generated descriptions
>> for all articles. (The data is right there!)
>>
>>
>> On Mon, Feb 9, 2015 at 5:44 AM, Erik Moeller  wrote:
>>
>>> See https://tools.wmflabs.org/autodesc for the new API described in the
>>> post. Interesting at least as a fallback to human-written descriptions...
>>>
>>> -- Forwarded message --
>>> From: Magnus Manske 
>>> Date: Mon, Feb 9, 2015 at 2:41 AM
>>> Subject: Re: [Wikidata-l] descriptions in mobile app
>>> To: "Discussion list for the Wikidata project." <
>>> wikidat...@lists.wikimedia.org>
>>>
>>>
>>> Manual descriptions are, in the vast majority of cases, a waste of
>>> volunteer time. Alternative:
>>> http://magnusmanske.de/wordpress/?p=265
>>>
>>>
>>> On Sun Feb 08 2015 at 17:37:42 Gerard Meijssen <
>>> gerard.meijs...@gmail.com> wrote:
>>>
>>>> Hoi,
>>>> How does that help ? The point is exactly that there is no point to
>>>> descriptions. Why iterate on a dog it will still be a mutt.
>>>> Thanks,
>>>> GerardM
>>>>
>>>> On 8 February 2015 at 14:07, Amir E. Aharoni <
>>>> amir.ahar...@mail.huji.ac.il> wrote:
>>>>
>>>>> I'd rather see it not as something terribly disappointing, but as an
>>>>> opportunity to find a way to fill item descriptions more efficiently.
>>>>>
>>>>> Basically, to find some cycles to resolve
>>>>> https://phabricator.wikimedia.org/T64695
>>>>> בתאריך 8 בפבר 2015 10:33, ‏"Gerard Meijssen" <
>>>>> gerard.meijs...@gmail.com> כתב:
>>>>>
>>>>>> Hoi,
>>>>>> I understand that item descriptions are going to be used in a mobile
>>>>>> app. In my opinion that is seriously disappointing because it is not
>>>>>> realistic to expect enough coverage in any language. Particularly in the
>>>>>> small languages it will not be really useful.
>>>>>>
>>>>>> My question is: we have had automated descriptions for a long time.
>>>>>> What is it that they makes that they are not used.?
>>>>>>
>>>>>> Thanks,
>>>>>>  GerardM
>>>>>>
>>>>>> ___
>>>>>> Wikidata-l mailing list
>>>>>> wikidat...@lists.wikimedia.org
>>>>>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>>>>>
>>>>>>
>>>>> ___
>>>>> Wikidata-l mailing list
>>>>> wikidat...@lists.wikimedia.org
>>>>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>>>>
>>>>>
>>>> ___
>>>> Wikidata-l mailing list
>>>> wikidat...@lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>>>
>>>
>>> ___
>>> Wikidata-l mailing list
>>> wikidat...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>>
>>>
>>>
>>>
>>> --
>>> Erik Möller
>>> VP of Product & Strategy, Wikimedia Foundation
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Fwd: [Wikidata-l] descriptions in mobile app

[Dmitry Brant]

Awesome! I would love to see the output of AutoDesc be returned by the API,
when a manual description is not available.
I would also be a strong proponent of fully auto-generated descriptions for
all articles. (The data is right there!)


On Mon, Feb 9, 2015 at 5:44 AM, Erik Moeller  wrote:

> See https://tools.wmflabs.org/autodesc for the new API described in the
> post. Interesting at least as a fallback to human-written descriptions...
>
> -- Forwarded message --
> From: Magnus Manske 
> Date: Mon, Feb 9, 2015 at 2:41 AM
> Subject: Re: [Wikidata-l] descriptions in mobile app
> To: "Discussion list for the Wikidata project." <
> wikidat...@lists.wikimedia.org>
>
>
> Manual descriptions are, in the vast majority of cases, a waste of
> volunteer time. Alternative:
> http://magnusmanske.de/wordpress/?p=265
>
>
> On Sun Feb 08 2015 at 17:37:42 Gerard Meijssen 
> wrote:
>
>> Hoi,
>> How does that help ? The point is exactly that there is no point to
>> descriptions. Why iterate on a dog it will still be a mutt.
>> Thanks,
>> GerardM
>>
>> On 8 February 2015 at 14:07, Amir E. Aharoni <
>> amir.ahar...@mail.huji.ac.il> wrote:
>>
>>> I'd rather see it not as something terribly disappointing, but as an
>>> opportunity to find a way to fill item descriptions more efficiently.
>>>
>>> Basically, to find some cycles to resolve
>>> https://phabricator.wikimedia.org/T64695
>>> בתאריך 8 בפבר 2015 10:33, ‏"Gerard Meijssen" 
>>> כתב:
>>>
 Hoi,
 I understand that item descriptions are going to be used in a mobile
 app. In my opinion that is seriously disappointing because it is not
 realistic to expect enough coverage in any language. Particularly in the
 small languages it will not be really useful.

 My question is: we have had automated descriptions for a long time.
 What is it that they makes that they are not used.?

 Thanks,
  GerardM

 ___
 Wikidata-l mailing list
 wikidat...@lists.wikimedia.org
 https://lists.wikimedia.org/mailman/listinfo/wikidata-l


>>> ___
>>> Wikidata-l mailing list
>>> wikidat...@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>>
>>>
>> ___
>> Wikidata-l mailing list
>> wikidat...@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>>
>
> ___
> Wikidata-l mailing list
> wikidat...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata-l
>
>
>
>
> --
> Erik Möller
> VP of Product & Strategy, Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Wikipedia Lite app?

[Dmitry Brant]

A definite +1 for the idea of having a separate "Lite" app where we focus
on optimizing for size and network usage for the developing world.

However, I'm afraid that having a Lite app would not automatically allow us
to drop support for Android 2.3 in the "main" app. I'll be the first to
attest to the number of headaches that supporting 2.3 has caused, but
unfortunately this is just a routine part of Android development.  Even if
we drop support for 2.3, we would still need to use the Support (AppCompat)
library which, for all its flaws, provides fairly great compatibility with
versions all the way down to 2.1, practically for free.

After all, the Facebook app (the "full" version) is still very much
available on Android 2.3, and provides an experience that's fully
consistent with the experience on my 4.4 device.

By the same token, there are plenty of 2.3 devices that are still quite
powerful even by today's standards, and surely deserve the experience of
the full Wikipedia app.

So then, I agree with all the other motivations for splitting off a Lite
app, but as much as it pains me to say this, dropping support for Android
2.3 shouldn't necessarily be one of them.

-Dmitry


On Sun, Feb 1, 2015 at 2:15 PM, Carolynne Schloeder <
cschloe...@wikimedia.org> wrote:

> Creating a separate app to optimize sounds like a good idea. We will check
> the market stats on Android versions, and I'll get the scoop from Facebook
> on their learning.
>
> I was somewhat surprised that most OEM's we've talked to are shipping
> Android 4.x even on low-priced models targeted for developing markets. But
> I'll clarify what's happening and circle back with Dan on the distribution
> plan (preload vs. appstores). I'll also catch up with Kim.
>
> I do love to see this attention given to our lower end handset users,
> thank you!
>
> Carolynne
>
> On Sun, Feb 1, 2015 at 9:30 AM, Lila Tretikov  wrote:
>
>> Dan,
>>
>> I think this is really important and thank you for highlighting this.
>>
>> Could you do rough sizing on what it would take to get something like
>> this out? What if we did this with a pre-load?
>>
>> Carolynne -- I recommend you start reaching out to Kim as you
>> re-formulate your W0 strategy.
>>
>> Lila
>>
>> On Sat, Jan 31, 2015 at 2:36 AM, Florian Schmidt <
>> florian.schmidt.wel...@t-online.de> wrote:
>>
>>> +1 for this idea. I still have an Android 2.3 device, but the Wikipedia
>>> app (and others too) is very slow and becomes more and more unusable, while
>>> it's agreat user experience on my Android 4.4 device.
>>>
>>> If dropping 2.3 support means a faster development of the main Wikipedia
>>> app and the <2.3 users still have access to Wikipedia through a lite app
>>> (which will be faster and more usable) i would say: do it, it has
>>> advantages for both sides :)
>>>
>>> Florian
>>>
>>> Gesendet mit meinem HTC
>>>
>>> - Reply message -
>>> Von: "Dan Garry" 
>>> An: "mobile-l" , "Carolynne Schloeder" <
>>> cschloe...@wikimedia.org>, "Toby Negrin" , "Lila
>>> Tretikov" 
>>> Betreff: [WikimediaMobile] [Apps] Wikipedia Lite app?
>>> Datum: Sa., Jan. 31, 2015 06:45
>>>
>>> Hi everyone,
>>>
>>> Those of you who were at the Mobile quarterly review heard me mention
>>> Facebook Lite, an app that's designed especially for the developing world.
>>>
>>> Notably, their app has a lot of optimisations which make it good for
>>> users in developing world:
>>>
>>>- It's only 252kB, good for limited data plans.
>>>- It supports down to Android 2.2, good for older devices.
>>>- It's data-efficient, good for 2G connections and for people on
>>>limited data plans.
>>>
>>> From a development perspective, some advantages are:
>>>
>>>- You no longer have to support older versions of Android in your
>>>main app.
>>>- You can tailor the performance of the lite app to the older
>>>devices so it's faster.
>>>- You can tailor the features of the lite app to the developing
>>>market.
>>>
>>> So obviously there are a lot of advantages for our users if we do this.
>>> And, selfishly, I can't stress enough how much dropping Android 2.3 from
>>> our current app would speed up development. As an example, almost all of
>>> the edge cases with lead images occurred on 2.3 devices, and they required
>>> quite a lot of investigation and hacking to fix them up. Obviously we've
>>> not dropped 2.3 so far because it's a very strategically important part of
>>> our user base, which I'm sure Carolynne can attest to!
>>>
>>> I'd say that we should put some serious thought into whether we'd prefer
>>> to have a Wikipedia Lite app for the developing world, rather than our
>>> current "one app to rule them all".
>>>
>>> Comments? Questions?
>>>
>>> Dan
>>>
>>> --
>>> Dan Garry
>>> Associate Product Manager, Mobile Apps
>>> Wikimedia Foundation
>>>
>>
>>
>
>
> --
> Carolynne Schloeder
> Director Global Mobile Partnerships
> Wikimedia Foundation
> +14154077071
> skype: cschloeder
>
> 

[WikimediaMobile] [Android] App update

[Dmitry Brant]

Our latest update to the official Wikipedia Android app is now available on
the Google Play Store! [1]  Here's a high-level overview of the features
introduced in this release:

* Lead images -- When navigating to an article, the app now displays the
most relevant image from the article at the very top, with the image
expanded to fit the width of your screen, and the title of the article
overlaid onto it.

* Image gallery -- Tap on any image in an article (including the lead
image) to see a full-screen gallery where the image may be panned and
zoomed. You may also "swipe" left and right to browse through other images
that are part of the article.  There are also options, accessible from the
toolbar on the top right, for sharing the image to your favorite social
media apps, saving it directly to your device, showing miscellaneous
information (Exif) about the image, and navigating to its File: page on
Wikipedia.

* Descriptions from Wikidata -- The app is now integrated with Wikidata [2]
to provide quick descriptions next to search results, as well as in Nearby
results, in disambiguation links, and in further reading suggestions.

* Search enhancements -- We have improved the search experience (accessible
from the top toolbar) to intelligently incorporate search results from
title-only searches, as well as full-text searches, so that typing a search
term will give you the most relevant result.

* Disambiguation and "page issues" links have been improved and restyled.
* Suggestions for further reading are provided at the bottom of articles.
* Infoboxes and other tables contained in articles are now collapsed by
default.
* The toolbar at the top has been restyled to follow the new Material
Design guidelines introduced in Android 5.0.
* When editing, templates are shown in a different color to help
differentiate between the template and regular text.

Enjoy!

--
Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering

[1] https://play.google.com/store/apps/details?id=org.wikipedia
[2] http://wikidata.org
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikipedia Beta Android app update

[Dmitry Brant]

Note also that yesterday's beta update should fix the lead image
clickability issue (that you raised (thanks!)), which may have been
contributing to the confusion/frustration.

We don't consider the alignment of certain images to be a road block to
releasing this feature because:
a) it takes one extra tap to view the full image.
b) most images are not poorly aligned (or alignment is irrelevant)
c) we'll be able to make incremental improvements to the functionality at
any time afterwards (including any of Monte's excellent ideas). As others
have said, because of the staggering diversity of our content, we can't
possibly account for all edge cases; but we also mustn't let that stifle
our progress.


On Sat, Dec 20, 2014 at 7:16 AM, Andy Mabbett 
wrote:

> On 20 December 2014 at 04:04, Monte Hurd  wrote:
>
> > what about the following ideas:
>
> Thank you for the constructive suggestions. I'd be agld to see
> anything whcih offers a improvement over the current beta
>
> > We could top align or align nearer the top. Experimenting with this has
> seemed to produce fewer edge cases for me. (I'm implementing the same
> functionality in the iOS app.)
>
> That won't work for images like
> https://en.wikipedia.org/w/index.php?title=File:Nycticebus_coucang_002.jpg
> (the Slow Loris example discussed here recently)
>
> > We could, if the article image dimensions are not conducive to being
> cropped, use the next image in the article which is.
>
> I infer form that that the problem is largely with portrait format images?
>
> > We could, instead of showing a single image in the cropped area, show a
> mosaic layout of the main image and a few others from the article scaled
> and sized to present a seamless bird's eye gallery in the crop box.
>
> That might work; but the detail might also become very small - and
> some infobox images are already mosaics.
>
> > We could animate a cross fade between all of the article images in the
> crop box.
>
> > We could, if we detect an image ill suited to the crop box, slowly pan
> from center to top left, then top right, then bottom left, then bottom
> right, then back to center.
>
> > We could start the image zoomed out such that no cropping is evident,
> with black bars in the narrower dimensions margins, the zoom in to aspect
> fill the crop box.
>
> These three  (and your subsequent " rotational 3D transform" idea)
> would need to satisfy WCAG guidelines on movement; and be tested by
> people with susceptibility to such.
>
>
> --
> Andy Mabbett
> @pigsonthewing
> http://pigsonthewing.org.uk
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Wikipedia Beta Android app update

[Dmitry Brant]

Hi Andy,

Thanks for uploading the screenshots!
Image #1 looks like a bona fide bug that we'll need to investigate.
However, the other images being suboptimally aligned simply exposes the
fact that we're not always able to detect the "best" possible alignment for
the image (our face detection algorithm cannot yet detect faces of
wallabies, owls, or lorises!).  For now, all we can do is default to
centering the image in that viewing area.  You may still tap on the image
to view it in full-screen mode.

(We'll also investigate the other issues you mentioned.)


-Dmitry


On Thu, Dec 18, 2014 at 4:55 PM, Andy Mabbett 
wrote:
>
> On 17 December 2014 at 21:12, Dmitry Brant  wrote:
>
> > * Lead Images -- When navigating to an article, the app now displays the
> > most relevant image from the article at the very top, with the image
> > expanded to fit the width of your screen, and the title of the article
> > overlaid onto it.  This provides a much improved visual context of the
> > article, and a better entry point into starting your reading experience.
> > (We're even doing face-detection in the image, so that photos of persons
> are
> > properly aligned in the viewing area)
>
> I've found a number of bugs with this (all on HTC Desire HD, running
> Android 2.3.5, native browser), which can be seen in:
>
>
> https://commons.wikimedia.org/wiki/Category:Wikipedia_mobile_app_beta_bugs_-_2014-12-18
>
> They include text over key parts of images (images numbered 3 and 4)
> and badly cropped images (2, 5, 6 ,7),
>
> (Image 1 shows a different problem, with the featured article.)
>
> > * Image Viewer -- Tapping on any image in an article (including the lead
> > image) will take you to a full-screen image viewer where the image may be
> > panned and zoomed.
>
> I found this happened when I tapped on other parts of the page, even
> when the image was scrolled off-screen.
>
> > * Wikidata descriptions in Nearby search results.
>
> When will we get the pins-on-map view back?
>
> --
> Andy Mabbett
> @pigsonthewing
> http://pigsonthewing.org.uk
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Wikipedia Beta Android app update

[Dmitry Brant]

Hi everyone,

We're very excited to bring you our latest update to the Wikipedia Beta
app, which should be available on the Google Play Store shortly[1].

The updated app packs a ton of awesome new features, the biggest of which
are:

* Lead Images -- When navigating to an article, the app now displays the
most relevant image from the article at the very top, with the image
expanded to fit the width of your screen, and the title of the article
overlaid onto it.  This provides a much improved visual context of the
article, and a better entry point into starting your reading experience.
(We're even doing face-detection in the image, so that photos of persons
are properly aligned in the viewing area)

* Image Viewer -- Tapping on any image in an article (including the lead
image) will take you to a full-screen image viewer where the image may be
panned and zoomed. It also displays the caption, as well as author and
license information, overlaid on top of the image (tap once on the image to
make the descriptions slide away).  There are also options, accessible from
the toolbar on the top right, for sharing the image, saving it to the photo
gallery on your device, showing miscellaneous information (Exif) about the
image, and navigating to its File: page on Wikipedia.

* Search enhancements -- We have improved the search experience (accessible
from the top toolbar) to intelligently incorporate search results from
title-only searches, as well as full-text searches, so that typing a search
term will give you the most relevant result, without having to switch
between Title and Full-text search.

More minor enhancements include:

* Wikidata descriptions in Nearby search results.
* Improved design of collapsed infoboxes and tables.
* Improved design of the main toolbar and search interface.
* Now bundling license information for open-source libraries that we use in
the app (accessible from the More -> About screen)
* Now using ProGuard in some portions of the app package, making it a bit
smaller in size.
* Numerous bug fixes for crashes and compatibility with various device
types.

We hope you enjoy using the updated app, and as always, we welcome your
feedback!
Cheers,

Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering

[1] https://play.google.com/store/apps/details?id=org.wikipedia.beta
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Did something change about prefix search today?

[Dmitry Brant]

Note also the bug that I filed today:
https://bugzilla.wikimedia.org/show_bug.cgi?id=73623


On Wed, Nov 19, 2014 at 6:14 PM, Monte Hurd  wrote:

> Confirmed with Chad that it's related to the Cirrus Search update that
> just went live. I asked him if he wanted me to open and bug and he said he
> will - he's still investigating.
>
> On Wed, Nov 19, 2014 at 2:52 PM, Bernd Sitzmann 
> wrote:
>
>> Monte, The screenshots show title search (prefixsearch). I'm suprised
>> that prefixsearch would be affected by any full text search (
>> CirrusSearch/ElasticSearch) changes. I thought those would be
>> independent systems.
>>
>> -Bernd
>>
>> On Wed, Nov 19, 2014 at 3:39 PM, Monte Hurd  wrote:
>>
>>> Not yet. Will file one once I have a bit more info about what the issue
>>> is.
>>>
>>> On Wed, Nov 19, 2014 at 2:33 PM, Tomasz Finc 
>>> wrote:
>>>
 Do we have a bug to track whatever the issue might be ?

 On Wed, Nov 19, 2014 at 2:30 PM, Monte Hurd 
 wrote:
 > I spoke with Chad about it and he's confirmed the issue and is going
 to
 > discuss with Nick and get back to me.
 >
 >
 > On Wed, Nov 19, 2014 at 2:07 PM, Tomasz Finc 
 wrote:
 >>
 >> I'd check with Chad and Nick handling todays CirrusSearch deployment.
 >>
 >> --tomasz
 >>
 >> On Wed, Nov 19, 2014 at 1:55 PM, Monte Hurd 
 wrote:
 >> > Here's what searching for "fish" returned yesterday:
 >> >
 >> >
 >> >
 >> >
 >> >
 >> >
 >> > And here's what I get today:
 >> >
 >> >
 >> >
 >> >
 >> > ___
 >> > Mobile-l mailing list
 >> > Mobile-l@lists.wikimedia.org
 >> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
 >> >
 >
 >

>>>
>>>
>>> ___
>>> Mobile-l mailing list
>>> Mobile-l@lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>>
>>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] availability of apps beta installation instructions

[Dmitry Brant]

Done!
https://www.mediawiki.org/wiki/Wikimedia_Apps




On Sat, Nov 15, 2014 at 2:24 PM, Monte Hurd  wrote:

> The signup link for the iOS app:
>
> http://flig.ht/1dhqz8j
>
>
>
>
> On Nov 15, 2014, at 11:15 AM, Amir E. Aharoni <
> amir.ahar...@mail.huji.ac.il> wrote:
>
> Hi,
>
> I am testing the beta apps for both Android and iOS. If I recall
> correctly, I got the installation instruction for them by email. I wanted
> to suggest testing them to somebody, but I couldn't find convenient
> instructions for doing this.
>
> I'd expect to find them somewhere on
> https://www.mediawiki.org/wiki/Wikimedia_Apps or on
> https://www.mediawiki.org/wiki/Mobile , or by searching "ios app beta" on
> mediawiki.org, but I couldn't find anything.
>
> Can these be posted in some convenient place at mediawiki.org, please?
>
> Thanks!
>
> --
> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> http://aharoni.wordpress.com
> ‪“We're living in pieces,
> I want to live in peace.” – T. Moore‬
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Server-side face detection

[Dmitry Brant]

Just throwing this out there:
Would it be possible to have a script that crawls through images on
Commons, detects faces in the images, and embeds the x,y position of the
face(s) into the File page of the image (or into the Exif data of the
image) (and makes this information available via the API)?

For a little context -- in our mobile apps, we'll be featuring images
related to the article that the user is browsing; however, the way that
we're cropping the images sometimes has the side effect of cropping out the
face of the subject (when the face is far from the center of the image).
Even though we can do face detection locally on the user's device, it can
be a bit slow and a bit intensive.  It would be great if this task was
offloaded, and the face position was returned right along with the image
itself...


-Dmitry
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] towards Android 5.0

[Dmitry Brant]

I've been digesting the new updates introduced in Android 5.0, and it looks
like there's at least one thing that we'll need to do relatively soon, if
we want to embrace the latest libraries and components.

In the new (v21) AppCompat library, it looks like they're gradually
deprecating the use of ActionBar, in favor of the more general "Toolbar".
Don't worry - the work we've done towards using a native ActionBar was not
in vain; there's a simple and straightforward migration path from ActionBar
to Toolbar.  Nevertheless, it might take ~2-3 story points to transition to
the new Toolbar, which I suggest we try to squeeze in during the next
couple sprints.

Visually it won't be much different, except for a three-dot overflow icon
(instead of three squares), and a slick new slide-out animation in the top
left corner (see attached screen-grab).
​​​
 device-2014-10-26-122152.mp4

​
The most (relatively) annoying thing is that the ActionBar in the v21
library no longer has a built-in ProgressBar, which we've been using
extensively, so, that'll take just a bit of restructuring.

All of this will allow us to start building the app with the new v21
library, and use the Material theme, and future-proof more of our code!

​
-Dmitry
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Android App production release

[Dmitry Brant]

Yep! I've updated the release history:
https://www.mediawiki.org/wiki/Mobile/Release_history#Apps



On Tue, Oct 14, 2014 at 5:22 PM, Tomasz Finc  wrote:

> Is the latest release r84? I can't tell from looking at
> https://www.mediawiki.org/wiki/Mobile/Release_history#Apps
>
> I'm assuming so given the date naming
>
> --tomasz
>
> On Tue, Oct 14, 2014 at 12:30 PM, Dmitry Brant 
> wrote:
> > Good news, everyone!  We've just released a new production version of the
> > Wikipedia Android App to the Google Play Store.  Here are some of the
> major
> > highlights:
> >
> > - Nearby: Learn more about what's around you by getting links to articles
> > about things that are near your current location. (Location services are
> > used only by this feature)
> > - Added a one-time Table of Contents tutorial screen.
> > - Rolled up "page issues" boxes into a link that shows them as a popup
> > dialog.
> > - Rolled up disambiguation links into a single link that shows them as a
> > popup list.
> > - Frequently-used languages are now kept at the top of the list, for
> easier
> > selection.
> > - Improved page loading speed and data usage by using compression in
> network
> > requests.
> > - Updated language translations.
> > - Numerous miscellaneous bug fixes.
> >
> > As always, you can download the app through the Google Play Store:
> > https://play.google.com/store/apps/details?id=org.wikipedia
> >
> > ...or download the APK directly:
> >
> https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.0-releasesprod-2014-10-14.apk
> >
> >
> > Cheers,
> >
> > Dmitry Brant
> > Mobile Apps Team (Android)
> > Wikimedia Foundation
> > https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
> >
> >
> > ___
> > Mobile-l mailing list
> > Mobile-l@lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/mobile-l
> >
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

[WikimediaMobile] Android App production release

[Dmitry Brant]

Good news, everyone!  We've just released a new production version of the
Wikipedia Android App to the Google Play Store.  Here are some of the major
highlights:

- Nearby: Learn more about what's around you by getting links to articles
about things that are near your current location. (Location services are
used only by this feature)
- Added a one-time Table of Contents tutorial screen.
- Rolled up "page issues" boxes into a link that shows them as a popup
dialog.
- Rolled up disambiguation links into a single link that shows them as a
popup list.
- Frequently-used languages are now kept at the top of the list, for easier
selection.
- Improved page loading speed and data usage by using compression in
network requests.
- Updated language translations.
- Numerous miscellaneous bug fixes.

As always, you can download the app through the Google Play Store:
https://play.google.com/store/apps/details?id=org.wikipedia

...or download the APK directly:
https://releases.wikimedia.org/mobile/android/wikipedia/stable/wikipedia-2.0-releasesprod-2014-10-14.apk


Cheers,

Dmitry Brant
Mobile Apps Team (Android)
Wikimedia Foundation
https://www.mediawiki.org/wiki/Wikimedia_mobile_engineering
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Release candidates!

[Dmitry Brant]

Build was cut for Android!
https://play.google.com/store/apps/details?id=org.wikipedia.beta



On Tue, Oct 7, 2014 at 7:43 PM, Monte Hurd  wrote:

> Build was cut for iOS.
>
> Signup link for Wikipedia iOS app Testflight betas here:
> http://tflig.ht/1dhqz8j
>
> On Tue, Oct 7, 2014 at 4:18 PM, Dan Garry  wrote:
>
>> Hi everyone,
>>
>> As mentioned at the standup yesterday, let's get our next release
>> candidates for the apps in order!
>>
>> On iOS, this release candidate should include:
>>
>>- UI scaling for larger devices
>>- Fix for the web view loading half way down the screen on slow
>>connections
>>- Page load indicator
>>
>> On Android, this release candidate should include:
>>
>>- Page issues and disambiguation rolled up into a button under the
>>page title
>>- Onboarding for the table of contents
>>- Nearby, a feature that lets you see articles about things you're
>>near
>>
>> Let's aim to get these release candidates in the appropriate channels
>> (TestFlight for iOS, Wikipedia Beta for Android) by end of day tomorrow
>> (Wednesday), so that we can get them submitted for release at the start of
>> next week.
>>
>> Thanks!
>>
>> Dan
>>
>> --
>> Dan Garry
>> Associate Product Manager, Mobile Apps
>> Wikimedia Foundation
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Thinking about offline search within our native apps

[Dmitry Brant]

> I thought this is something solved for years now with applications like
kiwix and Zim format?

Looking at the Kiwix app for Android, it doesn't seem to have full-text
search within articles (unless I missed it). I assume that this was left
out of the Android version for performance reasons.  So, this is precisely
the problem that would need to be solved...

-Dmitry

On Tue, Sep 30, 2014 at 3:05 PM, rupert THURNER 
wrote:

> I thought this is something solved for years now with applications like
> kiwix and Zim format?
>
> Rupert
> On Sep 30, 2014 11:27 PM, "Tomasz Finc"  wrote:
>
>> As the zero team starts to think about pre-loaded content the question
>> of how search will function within an off line environment has come
>> up. While it'll be up to each individual community to think about the
>> size of the pre-loaded we should think about these collections being
>> longer than a user would want to scroll through given only our article
>> title search.
>>
>> Thus i'm eager to get a discussion going abut how we would support the
>> following users story
>>
>> "As a user who has a Wikipedia pre-loaded device with little or no
>> internet connectivity, I would like to search by article text, so that
>> I can find multiple articles that could be relevant to me"
>>
>> Given this, an article title search is not good enough.
>>
>> * What would we have to change about our underlying data storage
>> architecture to do full text search?
>> * How fast would it be?
>> * Would it scale to 100's/100's/etc on articles ?
>> * What would the user experience look like?
>> ...
>>
>> * ... other bits i haven't thought about ?
>>
>> This is not at a resourced feature level discussion yet but I'd like
>> to get some engineering thoughts on it before we get there.
>>
>> --tomasz
>>
>> ___
>> Mobile-l mailing list
>> Mobile-l@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>>
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] [Apps] Featuring the app in Google Play

[Dmitry Brant]

It's all of these, as well:

https://trello.com/c/5WejUXDj/1-5-rewrite-page-browsing-activity-as-fragment-instead
https://trello.com/c/l2ouTvnf/2-5-make-every-other-activity-launched-from-nav-bar-into-fragments
https://trello.com/c/OOtykxBl/3-5-make-the-search-bar-into-an-actual-actionbar




On Thu, Sep 18, 2014 at 10:34 AM, Federico Leva (Nemo) 
wrote:

> Dan Garry, 15/09/2014 22:28:
> > Quick update, here. We received some feedback from Google Play,
>
> Nice.
>
> > and
> > we're working on implementing it all in this sprint. Check out our
> > sprint 40 Trello board
> > <
> https://trello.com/b/fuDbiOqN/mobile-app-sprint-40-android-insert-theme-9-15
> >
> > if you want more info.
>
> Couldn't find anything there, unless it's
> https://trello.com/c/DpHf0vu0/4-1-add-xxxhdpi-launcher-icon
>
> Nemo
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Re: [WikimediaMobile] Pulling the Commons app

[Dmitry Brant]

Done :'(


On Tue, Sep 16, 2014 at 3:14 PM, Dan Garry  wrote:

> I think it's now time to say goodbye to the Commons app. We bid you adieu,
> Commons app. *wipes tear from eye*
>
> Let's unpublish the app in both the App Store and Google Play.
>
> Dan
>
> On 10 September 2014 16:24, Dan Garry  wrote:
>
>>
>>
>> On 10 September 2014 12:02, Erik Moeller  wrote:
>>
>>> Sounds good from my end. IMO it'd be great to have a standard way to
>>> do this (handle trademark permissions / branding) in cases of
>>> community-created/maintained tools that are published through the app
>>> stores, since it'll come up again (and did before with the WLM app,
>>> kind of). But we can solve for it in this case if there's actually
>>> someone who wants to take it over.
>>>
>>
>> Howie and I did briefly discuss using this as a testbed for app
>> sunsetting, but we decided against it as the nature of an app (static code
>> on a remote device) makes it difficult to do things like banners announcing
>> the app is being sunset unless you thought of it ahead of time (which
>> wasn't the case for any of our apps).
>>
>> I think the best bet for us here is to document the process as we go,
>> then see what our pain points were and figure out how the process could be
>> improved in the future.
>>
>> Thanks,
>> Dan
>>
>> --
>> Dan Garry
>> Associate Product Manager, Mobile Apps
>> Wikimedia Foundation
>>
>
>
>
> --
> Dan Garry
> Associate Product Manager, Mobile Apps
> Wikimedia Foundation
>
> ___
> Mobile-l mailing list
> Mobile-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
>
___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l