On Tue, 11 Dec 2012 16:57:26 -0800, MZMcBride z...@mzmcbride.com wrote:
David Gerard wrote:
MZMcBride wrote:
Perhaps mobile uploading could use better native support, but again,
is the
cost worth it? Does Commons need more low-quality photos? And even as
phone
cameras get better, do those
On 13 December 2012 10:44, Daniel Friesen dan...@nadir-seen-fire.com wrote:
More importantly while quality is nice, that's not what's really important.
More important than quality is coverage. Getting photos of those things that
we don't have photos for. That is where mobile devices will
Στις 11-12-2012, ημέρα Τρι, και ώρα 19:04 -0500, ο/η MZMcBride έγραψε:
Brion Vibber wrote:
Over on the mobile team we've been chatting for a while about the various
trade-offs in native vs HTML-based (PhoneGap/Cordova) development.
[...]
iOS and Android remain our top-tier mobile
On Tue, Dec 11, 2012 at 8:11 PM, MZMcBride z...@mzmcbride.com wrote:
I think I fundamentally agree with your point, but when I consider that
there is (for example) no API for adding or removing a category from a page
(file or otherwise),
Sure there is, action=edit. Although the client does
Have a link? 'Cheap smartphone' seems a contradiction.
$50 Huawei phones running an ancient Android and only getting cheaper.
Jimbo's all about them.
http://techcrunch.com/2012/12/10/50-android-smartphones-are-disrupting-africa-much-faster-than-you-think-says-wikipedias-jimmy-wales/
On Tue, Dec 11, 2012 at 4:35 PM, Brion Vibber bvib...@wikimedia.org wrote:
Any thoughts? Wildly in favor or against?
From Brion's original email as well as my perspective from being involved
in these projects, I am in favor of shifting to native code for iOS and
Android. Considering the goals
Over on the mobile team we've been chatting for a while about the various
trade-offs in native vs HTML-based (PhoneGap/Cordova) development.
Currently our main Wikipedia apps are all HTML-based:
* Android - HTML + Cordova + plugins
* iOS - HTML + Cordova + plugins
* BlackBerry PlayBook (and later
Brion Vibber wrote:
Over on the mobile team we've been chatting for a while about the various
trade-offs in native vs HTML-based (PhoneGap/Cordova) development.
[...]
iOS and Android remain our top-tier mobile platforms, and we know we can do
better on them than we do so far...
Any
On 12 December 2012 00:04, MZMcBride z...@mzmcbride.com wrote:
Looking at the big picture, I don't think we'll ever see widespread editing
from mobile devices. The user experience is simply too awful. The best I
think most people are hoping for is the ability to easily fix a typo, maybe,
but
On 12/12/12 01:04, MZMcBride wrote:
Looking at the big picture, I don't think we'll ever see widespread editing
from mobile devices. The user experience is simply too awful. The best I
think most people are hoping for is the ability to easily fix a typo, maybe,
but even then you have to assess
On 12 December 2012 00:22, Platonides platoni...@gmail.com wrote:
David Gerard wrote:
OTOH, see recent coverage of Wikipedia in Africa, where it's basically
going to be on phones. Cheap shitty smartphones. That the kids are
*desperate* to get Wikipedia on. Do we want to make those readers
Small (native) apps can do Wikimedia work quite effectively using the api
Upload image
File categorisation
New page patrol
Flagged revs/Pending changes
OTRS
John Vandenberg.
sent from Galaxy Note
On Dec 12, 2012 7:04 AM, MZMcBride z...@mzmcbride.com wrote:
Brion Vibber wrote:
Over on the
Platonides wrote:
On 12/12/12 01:04, MZMcBride wrote:
Looking at the big picture, I don't think we'll ever see widespread editing
from mobile devices. The user experience is simply too awful. The best I
think most people are hoping for is the ability to easily fix a typo, maybe,
but even then
John Vandenberg wrote:
Small (native) apps can do Wikimedia work quite effectively using the api
Upload image
File categorisation
New page patrol
Flagged revs/Pending changes
OTRS
I think I fundamentally agree with your point, but when I consider that
there is (for example) no API for
We've gone a bit off topic into the question of whether we should spend any
time on mobile at all, it seems. :)
On Dec 11, 2012 5:11 PM, MZMcBride z...@mzmcbride.com wrote:
I think I fundamentally agree with your point, but when I consider that
there is (for example) no API for adding or
Brion Vibber wrote:
We've gone a bit off topic into the question of whether we should spend any
time on mobile at all, it seems. :)
Well, I think that's expected when the question was (broadly) where do we go
from here? I think native or non-native support is a false dichotomy:
there's a
16 matches
Mail list logo
