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
According to http://mobile-reportcard.wmflabs.org/graphs/ui-daily
on Thursday 23rd October (deployment day) both last modified links to
history and profile suffered a huge dip in clicks.
The dip seems to half both counts, which makes me theorize that we
were accidentally logging clicks here twice. The microtap code got
merged on Tue Oct 14 so would have gone out to mediawiki.org 16th and
then enwiki 23rd and caused a lot of issues so could be responsible
for this too..
If this is responsible, does this mean we made these 2 links
unclickable for half our audience or did we simply just fail to log
events for these 2 features? Or were we logging two events for a
single event?
Note, micro tap was reverted Thu Nov 6. I'm not sure if and when this
revert made it out to wikis. I'm not sure if we can expect the graph
to recover or stay plateaued.
Any more concrete ideas/theories?
Were there any notable code changes around that time to this part of code?
I've gotten some great review feedback from Gilles on the desktop-web
integration of my ogv.js JavaScript & Flash compatibility layers for Ogg
Theora/Vorbis media files -- thanks Gilles!
* libraries: https://gerrit.wikimedia.org/r/#/c/165477/
* desktop integration: https://gerrit.wikimedia.org/r/#/c/165478/
These are getting pretty close to ready to land, I think.
I would love to get some review on the mobile overlay I've whipped up as
well. This supports both native WebM playback (Android Chrome, Android
Firefox, Firefox OS) and ogv.js playback (iOS 7/8 Safari).
* mobile overlay: https://gerrit.wikimedia.org/r/#/c/165479/
* Live demo: https://ogvjs-testing.wmflabs.org/
A few open questions:
1) Is this the right way to do mobile overlay code? (It's basically a rip
of the existing photo viewer overlay in MobileFrontend, but lives in
TimedMediaHandler.) Is the overlay interface stable enough for other
extensions to use it for mobile-specific features? (I had to make updates
for object-model and template things that changed since this summer.)
2) Is the inline icon too huge/ugly here for audio files? Should it be
arranged differently, or display the player inline instead of as an overlay
for audio?
3) Should more controls be added to the overlay's bottom toolbar, such as
manual resolution selection or an 'Open in VLC' link to support HD playback
on iOS?
4) Should we autoplay when opening the overlay, or require a second tap?
5) How should we handle devices with no native playback that are either too
slow (iOS 6 Safari) or lack necessary features needed for the player
(Windows Phone)?
Current known bugs in the mobile overlay:
* CPU speed check not yet integrated to force to lowest resolution for old
iPhones/iPads (this exists on the desktop integration, just needs to be
moved to common code)
* autoplay doesn't seem to work with native playback right now
-- brion
The Android app Alpha builds[1] are working again.
Note that the alpha builds are based on the latest code that got merged, so
they should be considered less stable than the beta or production releases,
of course.
Cheers,
Bernd
[1] AaA: https://android-builds.wmflabs.org/
As you know, Vibha and I went to the material design conference today at
Google San Francisco. In short, I'm sold. Material design, hoo!
I took longer form notes in an etherpad
<http://etherpad.wikimedia.org/p/MaterialDesignConference>, but here's the
long and short of it in the form of four principles:
1. *Tangible surfaces:* Your phone is not a view port into an alternate
world. The UI of your app should feel tangible, like little bits of paper
moving around the screen.
2. *Print-like design: *UI elements should be like print on paper. Use a
consistent hierarchy for your information.
3. *Meaningful motion: *UI panels should never come out of nowhere; the
motion and interaction conveys how everything you're looking at is
connected together.
4. *Adaptive design: *Having a consistent UI across devices of all size
does not mean making everything have the same layout.
I realise this all sounds very high level, but it resonated with me quite a
lot. Google has even incorporated these principles into their apps on iOS,
such as Google Maps which is now using material design!
I'm currently trying to find the exact presentation that was shown today,
but in the mean time you can look at this for more info:
http://www.google.com/design/spec/material-design/introduction.html
More to come!
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
I'd like to encourage every engineer in the Mobile Team to take five
minutes, go to GitHub, and link your Wikimedia email address with your
GitHub account. Once you've done that, all your commits that are merged
will be automatically attributed to you the repository GitHub mirrors.
This is particularly important for the Mobile Apps Team as we love to point
people to GitHub so they have a one-stop shop to get their development
environment set up, and there are few people missing from the list of
contributors to the apps!
Thanks,
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
Hey everyone,
The apps don't have much a volunteer developer base when you compare them
to other MediaWiki projects. This is partially because the technology stack
is different (Java/Objective C app, as opposed to PHP website). But we have
lots of eager volunteer developers out there, and we should engage with
them!
To help accomplish the above, I've signed myself up to give an intro to
mobile app development at the MediaWiki Developer Summit in January. It'd
be great if those engineers on the mobile apps team who are interested and
attending the summit could sign themselves up as well, so that we can help
people who are interested. Or, if you're not an engineer but you're
attending and you're curious, sign up too!
Here's the link:
https://www.mediawiki.org/wiki/MediaWiki_Developer_Summit_2015#Developing_m…
Thanks,
Dan
--
Dan Garry
Associate Product Manager, Mobile Apps
Wikimedia Foundation
Hi,
Is there a reason why section edit icons only appear at <h2>s in
MobileFrontend?
When editing from my phone, I'd love to have them on all sections, but
maybe I'm missing something.
Hi, WikiGrok[0] has been successfully deployed to the English Wikipedia.
Along with it a first campaign[1] was deployed. Now database is being
slowly populated with suggestions:
MariaDB [enwiki_p]> select page_title, pp_value from page, page_props where
pp_page=page_id and pp_propname='wikigrok_questions_v1' limit 100;
+-------------------------+------------------------------------------------------------------------------------------------------+
| page_title | pp_value
|
+-------------------------+------------------------------------------------------------------------------------------------------+
| Richard_Branson |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Tina_Fey |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Jon_Stewart |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Bill_Maher |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Jeff_Foxworthy |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Evadne_Price |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Dominic_Guard |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Dilsa_Demirbag_Sten |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| J._Douglas_MacMillan |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Carol_Bowman |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Lianella_Carell |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| G._K._Reddy |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Liù_Bosisio |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
| Matilde_Rodríguez_Cabo |
a:1:{s:6:"author";a:2:{s:8:"property";s:4:"P106";s:9:"questions";a:1:{s:7:"Q482980";s:6:"author";}}}
|
+-------------------------+------------------------------------------------------------------------------------------------------+
14 rows in set (0.42 sec)
Pages are getting updated when edited (null edit works, but not
action=purge). According to estimations made with WikiData Query[2], the
number of potentially affected pages is approximately 33,000. If really
needed, we could whip up a script to null-edit these pages from server side
in a controlled manner, but I would like to have more data on performance
and memory consumption first.
== Monitoring ==
* Graphite: MediaWiki -> WikiGrok
* Exceptions from WikiData: type:mobile in Logstash.
== Firefighting ==
Most of potentially performance-scary/error causing code with can be
disabled by commenting out $wgWikiGrokSlowCampaigns in
wmf-config/mobile.php. If shit hits fan really hard, whole extension can be
disabled through the usual means, with $wmgUseWikiGrok.
== Next steps ==
I'm working on DB storage for questions[3] which will allow us to avoid
abusing page_props and give features such as "find me pages that could use
this type of fixes" and "find me a random page to fix".
----
[0] https://www.mediawiki.org/wiki/Extension:WikiGrok
[1] https://gerrit.wikimedia.org/r/#/c/170453/
[2] http://wdq.wmflabs.org/
[3] https://gerrit.wikimedia.org/r/170263
--
Best regards,
Max Semenik ([[User:MaxSem]])
Dear Android app users,
I just published new beta[1] and production[2] app releases, which should
be available through the store in a couple of hours. The changes are just
bug fixes. No new features this time. Here are the changes:
- Fixed possible crash during editing.
- Fixed possible crash when retrieving Nearby pages.
- Fix possible crash when detached from activity.
- Fix top padding for 2.3 devices. Top of the screen was cut off.
-Bernd
[1] https://play.google.com/store/apps/details?id=org.wikipedia.beta
[2] https://play.google.com/store/apps/details?id=org.wikipedia