Mobile-l

mobile-l@lists.wikimedia.org

4 participants
6884 discussions

Beta of Wikipedia 5.0.0 for iOS
by Joshua Minor 22 Dec '15

22 Dec '15

Hello, Since last quarter the WMF’s iOS team [1] (part of the Reading product group) has been working on a major version update to our iOS app [2]. Rather than adding new features to the existing app, the team took on the goal of re-thinking our mobile readers, and how we could provide them with a delightful, app-specific, experience that will keep them reading Wikipedia on iOS. After an extended alpha period we’re ready to share that work with you, and we’re looking forward to your feedback! Sign up for the Beta by registering here: https://goo.gl/forms/hNxPJah57p Once we are approved by Apple, you will receive a notification to install the beta via the TestFlight platform. I will also be giving a walkthrough of the app, as a lighting talk tomorrow at 11 PST. It will be one of several to the WMF’s monthly lightning talks for Dec, which will stream here: http://www.youtube.com/watch?v=cIqhGxtXFbg Thanks, Josh Minor Product Manager, Reading ==More info[3]== What’s New? Our aim was to give our users an easier and more inviting way to discover and read Wikipedia on iOS, and find experiences to keep them engaged. So, there are few new features or changes to the core features, but an all new look-and-feel, and many changes to navigation around that core. 5.0 is a complete overhaul from the ground up, but some major highlights include: - New Explore screen, a mobile-friendly way to enable that Wikipedia moment of serendipity - “First time user experience” that helps users get oriented and configure the app - All new user interface look-and-feel - Tab based navigation for one tap access to your History and Saved pages - Redesigned reader experience, with new page information and table of contents - Easy access to language switching while searching and reading Why is the app so different than the previous one? Although the existing iOS app is well reviewed, and has been featured by Apple, it has never been able to build a sizable audience. Compared to other content sites on the internet, our official apps have not been able to keep our iOS users engaged as they shifted from desktop browsers to mobile apps. In order to “try again” to see if we could engage readers, and also keep them engaged, we’re trying a totally new way of presenting ourselves on iOS. You can read a lot more about this on our project wiki [2] and in this product presentation [4]. What’s this Explore thing? The app’s Explore screen is a new, mobile friendly, way to experience the joy of discovery on Wikipedia. It mixes community curated content (from the en.wikipedia Main Page and Commons) with personally relevant content (based on articles you’ve read and your device location). All this is compiled locally on device and presented in a UI paradigm that is friendly to short, touch based sessions for casual consumption of media. It is an attempt to find a new way to engage, and re-engage, readers on a regular basis, by providing them a wide variety of dynamically changing content, presented in a familiar format. We think it can be very powerful way to enable mobile users to have that magic Wikipedia moment of discovery. Where’s my favorite old feature? Many features that were previously part of the “W” menu are now included in the Explore page. Random articles and articles near your location can both be found by exploring your feed. Other parts of the app now live in the main tab bar (Recent and Saved pages), or in the upper bar (Settings). Not finding something you loved? Fill out our feedback form and let us know [5]. What’s missing? Known issues? - Feed language and site: Currently the Explore page takes its content from your current “site”, based on your current search language. We will need to add more nuance to our site and language controls. If you are a multilingual user of the app, we’re particularly interested to get your feedback. - The app can be overly aggressive about updating/refreshing content. We erred on the side of getting the “latest” content. - Some localizations and RTL language support are incomplete (especially on iOS 8). We are actively working on this. - Navigation issues: although the tab based main interface has been well liked by users, the new navigation flows have introduced some inconveniences for longer sessions and quickly accessing some less frequently used but much loved features. We look forward to hearing from you about what you like, and don’t, about the new navigation. How can I give feedback? We have a feedback form you can fill out (anonymously) here [5] or on the project’s wiki talk page here [2]. The team will also be at the wiki dev summit <https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit_2016>, if you want to talk IRL! [1] - https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/iOS [2] - https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Why_5 [3] - Also available on wiki at https://www.mediawiki.org/wiki/FAQ_about_5.0 [4] - https://commons.wikimedia.org/wiki/File:IOS_Wikipedia_App_5.0_Update.pdf [5] - https://docs.google.com/a/wikimedia.org/forms/d/1NDBPJvWZ0idh9OuQ8pt684c9Mw…

2 2

Cross-post: pageviews.js—A JavaScript Client Library for the Wikimedia Pageviews API for Node.js and the browser
by Adam Baso 22 Dec '15

22 Dec '15

Interesting! Also, so is this: http://top.hatnote.com ---------- Forwarded message ---------- From: *Thomas Steiner* <tomac(a)google.com> Date: Tuesday, December 15, 2015 Subject: [Wiki-research-l] pageviews.js—A JavaScript Client Library for the Wikimedia Pageviews API for Node.js and the browser To: Research into Wikimedia content and communities < wiki-research-l(a)lists.wikimedia.org> Cc: Analytics List <analytics(a)lists.wikimedia.org> Dear all, First and foremost, thanks for making the Wikimedia Pageviews API available; your work is highly appreciated and super useful! As a modest "thank you", I am happy to release the JavaScript client library pageviews.js for Node.js and the browser to make working with this API easy for JavaScript developers. Please find the code and all instructions at [1]. The library adds some convenience functions (getting batch pageviews and limiting the number of results) that were inspired by Dan Andreescu's Python library [2] and is Promise-based: === var pageviews = require('pageviews'); // Getting pageviews for a single article pageviews.getPerArticlePageviews({ article: 'Berlin', project: 'en.wikipedia', start: '20151201', end: '20151202' }).then(function(result) { console.log(JSON.stringify(result, null, 2)); }).catch(function(error) { console.log(error); }); // Getting top-n items ranked by pageviews for multiple projects pageviews.getTopPageviews({ projects: ['en.wikipedia', 'de.wikipedia'], // Plural year: '2015', month: '12', day: '01', limit: 2 // Limit to the first n results }).then(function(result) { console.log(JSON.stringify(result, null, 2)); }).catch(function(error) { console.log(error); }); === On a more technical note—trying to be a good citizen [3]—the client library sets an identifying User-Agent header in Node.js mode. However, trying to set the corresponding X-User-Agent (note the "X-") header from a browser context (XMLHttpRequest cannot override the browser's intrinsic User-Agent for security reasons), this fails with an error message "Request header field X-User-Agent is not allowed by Access-Control-Allow-Headers in preflight response". Maybe you could change your CORS settings and include X-User-Agent in your Access-Control-Allow-Headers?! Hope this is useful. Thanks, Tom -- [1] pageviews.js: https://github.com/tomayac/pageviews.js [2] python-mwviews: https://github.com/mediawiki-utilities/python-mwviews [3] User-Agent requirement: https://wikimedia.org/api/rest_v1/?doc -- Dr. Thomas Steiner, Employee (blog.tomayac.com, twitter.com/tomayac) Google Germany GmbH, ABC-Str. 19, 20354 Hamburg Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle Registergericht und -nummer: Hamburg, HRB 86891 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.29 (GNU/Linux) iFy0uwAntT0bE3xtRa5AfeCheCkthAtTh3reSabiGbl0ck0fjumBl3DCharaCTersAttH3b0ttom.hTtP5://xKcd.c0m/1181/ -----END PGP SIGNATURE----- _______________________________________________ Wiki-research-l mailing list Wiki-research-l(a)lists.wikimedia.org <javascript:;> https://lists.wikimedia.org/mailman/listinfo/wiki-research-l

2 1

Re: [WikimediaMobile] [Analytics] Stopping eventlogging events into MobileWikiAppShareAFact table
by Adam Baso 22 Dec '15

22 Dec '15

Replacing mobile-tech with mobile-l (internal mobile-tech list discontinued). On Tuesday, December 22, 2015, Nuria Ruiz <nuria(a)wikimedia.org> wrote: > Team: > > As part of our effort of converting eventlogging mysql database to the > tokudb engine we need to stop eventlogging events from flowing into the MobileWikiAppShareAFact > table, we are using this one table to see how long the conversion will take > in order to plan for a larger outage window. > > > Let us know if data should be backfilled as it can be, we anticipate > events will not flow into table for the better part of one day. > > > Thanks, > > Nuria > > >

1 0

User essay about editing Wikipedia on a smartphone using the desktop version
by Tilman Bayer 16 Dec '15

16 Dec '15

Interesting, if lengthy essay: https://en.wikipedia.org/wiki/User:Cullen328/Smartphone_editing The author's assertion "In my experience, many productive mobile device editors prefer the desktop site" is actually open to empirical testing. Has anyone every tried to find out the percentage of edits from mobile devices that use the desktop version? These observations on the talk page about the shortcomings of the mobile web interface for curation purposes are also worth reading: https://en.wikipedia.org/wiki/User_talk:Cullen328/Smartphone_editing#PamD.2… -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB

2 1

Mobile web and the curious case of the peacock butterfly
by Pine W 15 Dec '15

15 Dec '15

This page [1] isn't updating in mobile web even with the purge command. The desktop version of the page is current. Any ideas of what's happening here? Thanks, Pine [1] https://en.m.wikipedia.org/wiki/Wikipedia:Featured_picture_candidates/Peaco…

6 9

simple english
by Jon Katz 15 Dec '15

15 Dec '15

Hi Folks, TLDR: want to introduce the idea of surfacing simple english version of wikipedia in a more prominent way to test if this appeals to our readers. no timeline, no action items, just an intro to the concept and a request for feedback/suggestions. *Bakground:* As a refresher/summary, as part of the reading team's strategic process <https://www.mediawiki.org/wiki/Reading/Strategy>, we identified 4 reading strategies that we are exploring and want to test hypothesis that will help us determine which strategies are more impactful. I am reviewing our strategy tests (i.e. tests that can help us determine if a particular strategy is one we should focus on) and came across some notes I made with Abbey (copied) around the potential strategy "Guided Educational Experiences" that I wanted to surface and run by you. This potential strategy is one where the reading team focuses on enhancing learning (comprehension and/or retention) of content. Ideas in this theme include identifying prerequisite articles, a suggested order to reading articles (curricula), simple or practical versions of articles, quizzes or even games. To be clear, this is a potential strategy that we are evaluating along with others, as described here <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Testing#Ab…>. I also want to acknowledge that there have likely been other experiments in this area--if you have specific examples you would like to share, please do so. The test proposed below came about from one such awareness. *The test:* One idea for this strategy was "simplified versions of articles"--versions of articles for readers who were unfamiliar with the topic or lacked a basic educational foundation. That wikipedia articles are sometimes to advanced is not a novel observation, but it's a tough nut to crack. We had originally framed the test as "will editors want to create simplified versions of articles" and we planned on asking them. However the work that James Helman is doing with editors translating medical documents into more practical guides in Swahili [link?] seems to show there is interest here. However, we felt that SimpleEnglish was, in itself, a remarkable test of what is being proposed, even though its focus is on simple wording rather than concept simplicity. The most often-cited problem (anecdote) with SimpleEnglish is that very few readers can find it. This makes sense: someone confused by sophisticated vocabulary or looking for a summary of an article is not likely to check the language list to see if a simple version of the article sits there. So the proposed test would be to surface simple english in a more prominent way and to test if this led to higher comprehension using either quick surveys or a proxy, like pageviews. I added the broad outlines of the test to our strategy test document, here <https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Testing#Cr…> . *The ask:* This is not part of our proposed Q3 plans or even our Q4 plans, but I would like to hear feedback and ideas around how we could effectively integrate it into our plans. One idea would be to implement it on one of the apps, first, since we can move things around there without disturbing as many people. We are open to suggestions. Best, J

2 2

Readership metrics for the fortnight until December 6, 2015
by Tilman Bayer 14 Dec '15

14 Dec '15

Hi all, here is the usual look at our most important readership metrics. This time examining, among other things, pageview changes in various countries, such as the effect of a brief block in China and of the sudden popularity of a Greek expression derived from Latin. The Android has been seeing a prolonged decrease in downloads, which fortunately were offset recently by a more positive development. With this issue we are changing the scope of this report from a timespan of one week to two weeks (a fortnight <https://en.wikipedia.org/wiki/FFF_system>) or four weeks, see further remarks below. Most of the metrics here are now being updated weekly on the new Product page <https://www.mediawiki.org/wiki/Wikimedia_Product#Reading>. Before we go to the usual data, a note (for those who haven’t seen it yet) that Wikistats <https://stats.wikimedia.org/> has now been upgraded to the new pageview definition, see the announcement <http://infodisiac.com/blog/2015/12/wikistats-upgraded-to-new-page-view-defi…> by Erik Zachte. (All numbers below are averages for November 23-December 6, 2015 unless otherwise noted.) Pageviews Total: 527 million/day (-2.4% from the previous fortnight) Context (April 2015-December 2015): (see also the Vital Signs dashboard <https://vital-signs.wmflabs.org/#projects=all/metrics=Pageviews>) A notable weekly drop of -2.2% in the week until November 29, followed by another -0.2% in the week until December 6. Desktop: 56.6% (week until Nov 22: 57.2%) Mobile web: 42.2% (week until Nov 22: 41.6%) Apps: 1.2% (week until Nov 22: 1.2%) Context (April 2015-December 2015): <https://commons.wikimedia.org/wiki/File:Wikimedia_daily_pageviews,_mobile_p…> Global North ratio: 77.6% of total pageviews (week until Nov 22: 77.3%) Context (April 2015-December 2015): <https://commons.wikimedia.org/wiki/File:Percentage_of_Wikimedia_pageviews_f…> Out of curiosity about the -2.2% drop, I ran a query for the week until November 29 to find the countries with the largest changes from the previous week (as in some <https://lists.wikimedia.org/pipermail/mobile-l/2015-November/009919.html> previous reports; restricted to those with >1 millions views/day in the week until Nov 29): Greece +21.6% 2.3 m/day South Africa -21.6% 1.2 m/day Ireland -20.6% 2.3 m/day Colombia -15.7% 3.3 m/day Venezuela -10.9% 2.3 m/day Argentina -8.3% 4.9 m/day Philippines -8.3% 3.5 m/day New Zealand -7.3% 1.3 m/day Vietnam -7.1% 2.1 m/day Taiwan -6.9% 6.2 m/day For the top three, I looked at how pageviews developed on a daily basis during the last three month including the week after this large change (until Dec 6): In Greece, the +21.6% rise was the result of an isolated spike from November 23-25. This can be traced to a single page on the Greek Wiktionary which on most days before and after only saw a single-digit number of pageviews, but on these three days received more than 2.8 million: τάλε κουάλε <https://el.wiktionary.org/wiki/%CF%84%CE%AC%CE%BB%CE%B5_%CE%BA%CE%BF%CF%85%…>. It’s about an expression that apparently comes from Latin via Italian (“tale quale”) <https://en.wiktionary.org/wiki/tale_e_quale> and means something like “exactly the same” or “spitting image”. From the form of the spike, it was likely not the result of actual human interest, rather an undetected bot trying to learn exactly the same about exactly the same. In Ireland, the -20.6% drop marked the end of a plateau whose start had actually shown up in the report for the week until November 1 <https://lists.wikimedia.org/pipermail/mobile-l/2015-November/009919.html> already, where the country was the top changer with a 40.2% rise. For South Africa, the -20.6% drop does not form part of a clear pattern. Turning to the week until December 6, there were user reports <https://zh.wikipedia.org/wiki/Wikipedia:%E4%BA%92%E5%8A%A9%E5%AE%A2%E6%A0%8…> starting around December 4 that Wikimedia projects were being blocked in China on desktop more widely than before (the Chinese Wikipedia has been blocked since May 2015). However, as can be seen in the chart below, the block appears to have been short-lived. It has also been mentioned in various media reports (English-language examples: China Digital Times <http://chinadigitaltimes.net/2015/12/minitrue-weekend-block-of-wikipedia/>, TIME <http://time.com/4142305/xi-jinping-china-censorship-world-internet-conferen…>). New app installations Android: 30.6k/day (-28.9% from the previous fortnight) Daily installs per device, from Google Play Context (last two months): Instead of recovering to the level from before the App Store feature from Nov 5-12, installation numbers dropped further until early December. It now appears that this is connected to a sharp decrease in Google search referrals to the app’s store page. We’re looking further into it. The good news though is that the app is currently featured among the Best Apps of 2015 <https://lists.wikimedia.org/pipermail/mobile-l/2015-December/009995.html> in various countries, with a clear effect on download numbers from December 3 on. (We’ll do a full assessment of the impact of this promotion in early January after it ends.) iOS: 4.44k/day (-4.6% from the previous fortnight) Download numbers from App Annie Context (last three months): [image: Wikipedia_iOS_app_daily_downloads%2C_Sep_8%2C_2015_~_Dec_6%2C_2015_(App_Annie).png] <https://commons.wikimedia.org/wiki/File:Day-7_retention_of_Wikipedia_iOS_ap…> There was a 5.4% drop between the week until November 22 and the week until November 29. But this is still higher than in the first week of November, say. App user retention Android: 14.8% (previous fortnight: 15.0%) (Ratio of app installs opened again 7 days after installation, average of daily percentages for installs from the previous week. 1:100 sample) Context (last three months): (NB: In order to have the chart show any potential causal connections more clearly, I’ve changed the x-axis to the installation date instead of the date on which the survival is measured, and added annotations.) iOS: N/A (Ratio of app installs opened again 7 days after installation, average of daily ratios for installs from the previous week. From iTunes Connect, opt-in only = ca. 20-30% of all users) Unfortunately I encountered data quality issues with this metric (again <https://lists.wikimedia.org/pipermail/mobile-l/2015-November/009942.html>). We are in contact with Apple about this. I will leave the metric out of these reports until this is resolved or we have a suitable substitute (we could conceivably track this ourselves via EventLogging, like on Android).Unique app users Android: 1.158 million / day (-3.8% from the previous week) Context (last two months): By now it looks like the App Store feature from Nov 5-12 indeed raised active users numbers a bit, although they have since been steadily decreasing, possibly for other reasons (see above). iOS: 284k / day (+1.0% from the previous fortnight) Context (last two months): The week until November 29 saw an increase of 3.5% compared to the previous week. And in the chart, a little bump can be discerned from November 26 on, which could be related to Thanksgiving in the US (as we know, mobile use tends to be higher on weekends and presumably also holidays). Schedule of this report As mentioned last time <https://lists.wikimedia.org/pipermail/mobile-l/2015-November/009942.html>, we have been rethinking the schedule of this report. New issues will now cover either two weeks or four weeks each (keeping it to a multiple of seven days, considering that most of these metrics show a strong weekly seasonality and comparisons are hence best taking that period into account). The main purpose remains the same as laid out earlier <https://lists.wikimedia.org/pipermail/mobile-l/2015-September/009773.html>: to raise awareness about how these metrics are developing, call out the impact of any unusual events in the preceding week, and facilitate thinking about core metrics in general. Having iterated the selection and presentation of these metrics on a weekly basis since launching this report in September, they have now stabilized a bit. Also, it now appears that the newsworthy items uncovered by examining the development of these metrics can also be covered on a less frequent than weekly schedule. On the other hand, most of these metrics are now also updated weekly as part of the Reading team’s section on the new Wikimedia Product page on mediawiki.org <https://www.mediawiki.org/wiki/Wikimedia_Product>. Feedback and discussion continue to be welcome. ---- For reference, the queries and source links used are listed below (access is needed for each). Unless otherwise noted, all content of this report is authored on behalf of the Wikimedia Foundation and released under the CC BY-SA 3.0 <https://creativecommons.org/licenses/by-sa/3.0/> license. Most of the above charts are available on Commons <https://commons.wikimedia.org/w/index.php?title=Special:ListFiles&offset=20…>, where I’m also uploading PDF versions of previous issues of this report. hive (wmf)> SELECT SUM(view_count)/14000000 AS avg_daily_views_millions FROM wmf.projectview_hourly WHERE agent_type = 'user' AND CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-11-23" AND "2015-12-06"; hive (wmf)> SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, sum(IF(access_method <> 'desktop', view_count, null)) AS mobileviews, SUM(view_count) AS allviews FROM wmf.projectview_hourly WHERE year=2015 AND agent_type = 'user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; hive (wmf)> SELECT access_method, SUM(view_count)/14 FROM wmf.projectview_hourly WHERE agent_type = 'user' AND CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-11-23" AND "2015-12-06" GROUP BY access_method; hive (wmf)> SELECT SUM(IF (FIND_IN_SET(country_code, 'AD,AL,AT,AX,BA,BE,BG,CH,CY,CZ,DE,DK,EE,ES,FI,FO,FR,FX,GB,GG,GI,GL,GR,HR,HU,IE,IL,IM,IS,IT,JE,LI,LU,LV,MC,MD,ME,MK,MT,NL,NO,PL,PT,RO,RS,RU,SE,SI,SJ,SK,SM,TR,VA,AU,CA,HK,MO,NZ,JP,SG,KR,TW,US') > 0, view_count, 0))/SUM(view_count) FROM wmf.projectview_hourly WHERE agent_type = 'user' AND CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) BETWEEN "2015-11-23" AND "2015-12-06"; hive (wmf)> SELECT year, month, day, CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")), SUM(view_count) AS all, SUM(IF (FIND_IN_SET(country_code, 'AD,AL,AT,AX,BA,BE,BG,CH,CY,CZ,DE,DK,EE,ES,FI,FO,FR,FX,GB,GG,GI,GL,GR,HR,HU,IE,IL,IM,IS,IT,JE,LI,LU,LV,MC,MD,ME,MK,MT,NL,NO,PL,PT,RO,RS,RU,SE,SI,SJ,SK,SM,TR,VA,AU,CA,HK,MO,NZ,JP,SG,KR,TW,US') > 0, view_count, 0)) AS Global_North_views FROM wmf.projectview_hourly WHERE year = 2015 AND agent_type='user' GROUP BY year, month, day ORDER BY year, month, day LIMIT 1000; SELECT country_code, changeratio, ROUND(milliondailyviewsthisweek,1) AS milliondailyviewsthisweek FROM (SELECT country_code, ROUND(100*SUM(IF(day>22 AND day<30, view_count, null))/SUM(IF(day>15 AND day < 23, view_count, null))-100,1) AS changeratio, SUM(IF(day>22 AND day<30, view_count, null))/7000000 AS milliondailyviewsthisweek FROM wmf.projectview_hourly WHERE year = 2015 AND month = 11 AND agent_type = "user" GROUP BY country_code) AS countrylist WHERE milliondailyviewsthisweek > 1 GROUP BY country_code, changeratio, milliondailyviewsthisweek ORDER BY ABS(changeratio) DESC LIMIT 10; https://console.developers.google.com/storage/browser/pubsite_prod_rev_0281… (“overview”) https://www.appannie.com/dashboard/252257/item/324715238/downloads/?breakdo… (select “Total”) SELECT LEFT(timestamp, 8) AS date, SUM(IF(event_appInstallAgeDays = 0, 1, 0)) AS day0_active, SUM(IF(event_appInstallAgeDays = 7, 1, 0)) AS day7_active FROM log.MobileWikiAppDailyStats_12637385 WHERE userAgent LIKE '%-r-%' AND userAgent NOT LIKE '%Googlebot%' GROUP BY date ORDER BY DATE; (with the retention rate calculated as day7_active seven days later divided by day0_active from the install date) https://analytics.itunes.apple.com/#/retention?app=324715238 hive (wmf)> SELECT SUM(IF(platform = 'Android',unique_count,0))/7 AS avg_Android_DAU_last_week, SUM(IF(platform = 'iOS',unique_count,0))/7 AS avg_iOS_DAU_last_week FROM wmf.mobile_apps_uniques_daily WHERE CONCAT(year,LPAD(month,2,"0"),LPAD(day,2,"0")) BETWEEN 20151123 AND 20151206; hive (wmf)> SELECT CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, unique_count AS Android_DAU FROM wmf.mobile_apps_uniques_daily WHERE platform = 'Android'; hive (wmf)> SELECT CONCAT(year,"-",LPAD(month,2,"0"),"-",LPAD(day,2,"0")) as date, unique_count AS iOS_DAU FROM wmf.mobile_apps_uniques_daily WHERE platform = 'iOS'; -- Tilman Bayer Senior Analyst Wikimedia Foundation IRC (Freenode): HaeB

1 0

Best Apps 2015
by Jan Ainali 13 Dec '15

13 Dec '15

One of the best apps in 2015 in Google Play! https://play.google.com/store/apps/collection/promotion_3001cd4_apps_bestof… Well done! *Kind regards,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>

5 4

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

11 Dec '15

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.… [3] https://phabricator.wikimedia.org/T121236 [4] https://www.mediawiki.org/wiki/Wikimedia_Apps/Team/Wikipedia_Android_app_ha…

1 0

Reading department planning for next quarter
by Moushira Elamrawy 10 Dec '15

10 Dec '15

Hello Everyone, Hope you are enjoying the approach of the end of the year. In the last 3 months the reading team has worked on a process for open strategy planning [0], in order to define priorities, and align tests and products that the team works on, with broader movement goals. Given the strategy work, planning for Q3 (the next quarter: Jan - March) is different; the team is sharing its roadmap for Q3 and Q4 [1], as well as the actions planned for Q3 [2] early on. Despite of the strategy work and planning, these documents are still work in progress; adaptations and changes are likely to take place, given the time frame and tests included. However, the team is sharing early in order to accommodate feedback. You can also add suggestions for Q4 (Apr - Jun), as long as they align with the roadmap. This is the first team the team shares its plans early and openly, and allows room for feedack and suggestions in future planning. We trust that the open process will help with better engagement and more lessons to learn on best practices. Enjoy December! All the best, M [0] https://www.mediawiki.org/wiki/Reading/Strategy/Strategy_Process/Testing [1] https://www.mediawiki.org/wiki/Reading/Roadmap [2] https://www.mediawiki.org/wiki/Reading/Quarterly_Planning/Q3 [3] https://www.mediawiki.org/wiki/Reading/Quarterly_planning/Q4

3 3

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

Mobile-l