Mobile/QuarterlyReview

Mobile quarterly review (meeting scheduled for 18 March, 2013)

The following is based on the framework that E3 used to structure their quarterly review (slide deck here: https://meta.wikimedia.org/wiki/File:E3-QuarterlyReview-Jan2013.pdf, with some modifications based on lessons learned from that meeting.

Team intro and Annual Plan goals [Tomasz] [10min]

 * 1) who are we?
 * 2) Web [Browser]
 * 3) Jon, Juliusz, Arthur, Max, Michelle, Maryana, Vibha, Munaf
 * 4) Apps [iOS & Android]
 * 5) Brion, Yuvi, Shankar, Tomasz
 * 6) Partner
 * 7) Brion, Dan
 * 8) what are our targets for this fiscal year?
 * 1,000 uploaders / month
 * 1) 4 billion pages / month


 * 1) Potential discussion points
 * 2) Why we split the teams
 * 3) Which user group do we target [Use howies slide]
 * 4) How the teams work together. How they work separately.
 * 5) Massive agile empowered teams
 * 6) Geographically distributed team and how we made this work

Recap of Q1 (Jul.-Sept.) Arthur Richards (talk) [15 mins]

 * 1) Goals
 * 2) To facilitate contributions on mobile devices (high risk, many unknowns, big fiscal year goals, needed to
 * 3) High risk, many unknowns
 * 4) Need to better understand the landscape & tech to fully implement in mobile web/apps
 * 5) Features roadmap
 * 6) WLM app (primary focus)
 * 7) Improvements to mobile web in beta
 * 8) Improved navigation UI
 * 9) Impact
 * 10) First mobile photo uploads via WLM app
 * 11) Widespread usage, facilitated record-breaking photo competition -
 * 12) Proved it was possible, upload-related plumbing to be reused in mobile apps + web
 * 13) Most important milestones achieved for the quarter Wikimedia_Engineering/2012-13_Goals

Recap of Q2 (Oct.-Dec.) Arthur Richards (talk) [15 mins]

 * 1) Goals
 * 2) To facilitate contributions on mobile devices
 * 3) Increasing readership
 * 4) Improving internal infrastructure
 * 5) Features roadmap
 * 6) New mobile nav/chrome pushed to stable for mobile web
 * 7) 'Read in other languages'
 * 8) Experimental contributory features
 * 9) photo upload
 * 10) article editing
 * 11) watchlists
 * 12) log in
 * 13) account creation
 * 14) UI improvements
 * 15) cleanup templates
 * 16) tables
 * 17) random article
 * 18) Geodata (experimental deployment to enwp)
 * 19) Added ultra-experimental 'alpha' for mobile web
 * 20) Impact
 * 21) 
 * 22) much plumbing added for upcoming features
 * 23) some milestones met for internal infra goals Wikimedia_Engineering/2012-13_Goals
 * 24) we have not given this as much attention as contributory features
 * 25) there have been major stumbling blocks with Solr/OSM integration
 * 26) milestones met for contribution goals Wikimedia_Engineering/2012-13_Goals
 * 1) milestones met for contribution goals Wikimedia_Engineering/2012-13_Goals

Goals

 * 1k unique uploaders per month on Wikimedia projects

In production

 * Watchlist (view and add/remove items): used as a hook to draw in both new and experienced editors into the account creation/login funnel


 * Login/account creation: enabling users to log in and use contributory features


 * Login/signup hooks: driving more people into the account creation/login funnel by showing login/signup calls to action from contributory features for logged out users


 * Add image to lead section of article: one-step process for uploading to Commons and inserting thumbnail image into article


 * Donate image to Commons: uploading image to Commons from user's Uploads page


 * Uploads view: view of recent Commons uploads and mobile-friendly file pages


 * Nearby view with upload CTA: view of nearby articles, with upload call to action on those that are lacking images


 * iOS and Android Commons apps: apps that allow power users to upload multiple photos, add categories/custom titles, and share their files to Commons

Impact

 * Watchlist, login, account creation
 * X new accounts created via watchlist star, lead image signup CTA, and Uploads signup CTA this quarter


 * Lead image uploads
 * X images added to articles (not including Nearby)
 * X unique users using this feature (not including Nearby)
 * examples of articles that have been improved by this feature


 * Donate image to Commons
 * X images donated
 * X unique users using this feature
 * examples of images donated by this feature


 * Nearby
 * X images added via Nearby
 * X unique users using this feature
 * examples of articles that have been improved by this feature


 * Total uploads/uploaders
 * some graphs of upload feature usage by user type (e.g., new/existing users)
 * conversion funnel from anon -> registered user -> upload attempt -> uploader
 * qualitative assessment of uploads: what kinds of files did we get?



Successes/challenges

 * Collaboration with other teams: E3, Analytics, Fundraising, QA – success!

To be discovered!

Asks
[Tomasz] [5min] Do we have what we need to meet our goals for Q4? What resources do we need to help us meet those goals?


 * 1) Video tech at the office is moving at a glacial pace
 * 2) Dedicated site reliability engineer
 * 3) Buisness analyst
 * 4) Better recruiting
 * 5) Better testing env. Espeically for performance testing

--- Notes:
 * Quick recap of Q1/2, focus on recap of Q3, plans for Q4