The Mobile Apps team just met and discussed the timeline for the release of
the new Android & iOS Wikipedia apps. We've decided to descope a bit and
decouple the two platforms from each other. Our first release will be
beta app on June 4th*, and our end-of-fiscal-year goal is shipping the *fully
fledged Android app on June 25th. *We'll still be working on the iOS app,
but it won't be released to market until next fiscal year (e.g., July).
We're biting off an ambitious chunk of work in our MVP of the retooled apps
(improving the reading experience, adding an editing workflow, supporting
Zero users), and doing all of this for both platforms with a small (but,
luckily, swiftly growing!) team, while maintaining consistent design/UX and
leveraging platform-specific capabilities has been tough. There are a
number of deciding factors in making the choice to focus on shipping to
Android first, including:
* We currently have more Android engineers than iOS, so we can move faster
on that end.
* Android users are a slightly higher percentage of our total current app
* Android is more critical for the Wikipedia Zero program.
* The Android release process is faster and easier for pushing out small
bug-fixes, which we'll almost certainly need to do a lot of as soon as we
put anything out there in front of a wide audience.
* iOS comes with higher user expectations on the UI/UX side, and we need a
bit more time to ensure our product meets those expectations.
We'll probably want to mention some of this in external-facing
communication about the new app and the release, since the Global North app
market is still pretty iOS-centric and people might want to know why we're
not targeting that audience first :)
If you have any questions or concerns, please let me know. And I'll be in
touch with Comms to continue the discussion on communication strategy --
we'll probably want some social media attention to announce the beta
release & get more beta testers excited about getting their hands on the
Product Manager, Wikimedia Foundation
During the Zurich hackathon, DJ Hartman, Aude and I knocked up a
generic maps prototype extension . We have noticed that many maps
like extensions keep popping up and believed it was time we
standardised on one that all these extensions could use so we share
We took a look at all the existing use cases and tried to imagine what
such an extension would look like that wouldn't be too tied into a
specific use case.
The extension we came up with was a map extension that introduces a
Map namespace where data for the map is stored in raw GeoJSON and can
inclusion of maps in wiki articles via a map template.
Dan Andreescu also created a similar visualisation namespace which may
want to be folded into this as a map could be seen as a visualisation.
I invite Dan to comment on this with further details :-)!
I'd be interested in people's thoughts around this extension. In
particular I'd be interested in the answer to the question "For my
usecase A what would the WikiMaps extension have to support for me to
Thanks for your involvement in this discussion. Let's finally get a
maps extension up on a wikimedia box!
I'm Dan, and I'll be your Product Owner for this product. Please keep your
arms and legs inside the sprint at all times, and please be sure to read
the sprint safety instructions stored in /dev/null. :-)
As mentioned last week, the next two sprints will be split by platform.
This sprint, iOS will have its design overhauled and we'll work on Android
bugs. Next sprint, we'll flip things, and Android will be have the design
overhaul and we'll work on iOS bugs.
Our wonderful designers have provided us with more finalised mockups for
the iOS redesign. They're available here: Mockup
, Mockup 2<https://trello-attachments.s3.amazonaws.com/52e98a603e6d08a53861025b/52e98c…>
Let's get to work! Let me know if you've got any questions.
Associate Product Manager for Platform and Mobile Apps
On Tue, May 13, 2014 at 1:22 PM, Jon Robson <jrobson(a)wikimedia.org> wrote:
> Thanks for documenting this Chris!
> I'm not sure if this should be a bug - maybe uploads to
> Special:Uploads of this form should show an error message saying "We
> already have this photo." ?
I am tempted to leave it the way it is and just have the test check the alt
text of the thumbnail image rather than the href value. That would
validate that the steps to upload are working properly.
> That aside how can we ensure each of the images uploaded is unique?
> This test should be testing the case where an upload is unique..
I tried running this test using the shared image upload code to upload
unique(ish) images. But doing that shows a modal dialog that says
"Warning! This photo looks suspicious. If it's not a photo that you took,
please do not upload it. Do you still want to continue?"
I also get that modal dialog uploading images manually.
We could make the test dismiss the modal dialog, but it would be better if
we did not see the modal dialog at all.
Heads up that last week we ended up estimating sprint 31. Mailing here
Android engineers notice that most of the stories in the sprint are
*not* estimated as they are bugs and thus a drag on velocity. This was
the team norm we adopted many months ago. It'll be especially
noticeable this sprint as we have a ton of defects to fix on Android.
Let me know if you have any questions especially if you're traveling