Mobile/2013 strategy planning



For previous strategy planning, see: Mobile/2013 strategy planning/Archive

Ask: Please look through the background, current and planned workflows to make sure we're all on the same page with what we're working on in the short-term. After you've done this, please make sure to add (or +1) at least one new upload or other feature idea. These rough ideas will be turned into stories for next quarter during our team planning session in late March; only you can ensure that your brilliant ideas make it into our roadmap!

Background
The mobile team is working to reach its target of 1,000 unique uploaders per month at the end of this fiscal year. We’ve already built some features and are planning some others – you can see the ones we’ve already created below in Current upload workflows with some early estimates of their impact, as well as ones we could potentially work on through the end of Q3/beginning of Q4 in Potential/planned workflows.

However, we should still be prepared in case we fall short of our goal with Other upload ideas for getting more users to upload via their mobile device. In the event that we do reach our goal early, we may want to explore new projects like editing and curation/micro-contribution. See Other contributions for those.

Current upload workflows

 * Lead image upload CTA

A call to action to upload an image to articles that have no images or infoboxes in the lead section.


 * Uploads dashboard

A call to action to donate an image to Commons via a persistent link in the left nav. Not associated with any articles.


 * Upload/share via Commons (app)

The ability to take photos and upload them to Commons, and convert existing photos into the appropriate format and share via Commons.

Impact
As of March, we have about 40 unique uploaders a week via web (from the two upload workflows) and 30 via apps, for a projected total of ~300 unique uploaders per month.

In the short term:
 * 1) A login-related bug is depressing the number of successful web uploaders
 * 2) The Uploads dashboard is still in Beta
 * 3) The apps are still very new and haven't been widely publicized yet

After the bug is fixed and Uploads is deployed to full mobile web, the number of web uploaders should go up to at least 75 per week (the total number of unique users who currently started the upload process) from lead article workflow, and potentially 150 per week for uploads dashboard (total number of users who started the upload process X 2 for scale from beta to full mobile web)

This will bring us up to a projected 900 unique uploaders a month. If we get 100 total apps users per month, we might make it to our goal of 1,000 unique uploaders/month!

Showing upload features to logged out users as hooks into login/signup could also increase the impact of these features, netting an additional 500 users per week signing up via the two upload hooks (extrapolating from the watchlist star data – 3,000 users a week signing up from the star, which is on all articles), netting 50-100 extra uploaders per standard conversion rate

Potential/planned workflows

 * Nearby

A call to action to add images to articles nearby that lack them.


 * Non-lead image uploads

Give users the ability to add photos to articles that already have images or infoboxes.

Impact
We don't currently have data on the Nearby upload process, but media attention around the early alpha prototype shows that it will may pique new user curiosity/engagement.

Widening the heuristic for in-article uploads feature will definitely have an impact. Currently, based on a random sample of 50 articles on English Wikipedia, the lead image upload button only shows up on about 18% of articles. We could explore widening the heuristic to include:


 * Very short stubs, which current don't register as needing images (about 10% of enwiki articles)
 * Articles with infoboxes but no images in lead section (about 48% of enwiki articles)
 * Articles that already have images (about 24% of articles)

Based on this data, it probably makes sense to start by figuring out section-level uploading.



Upload a similar photo
On photo pages themselves we might want to encourage photo uploads from there. For instance if I am looking at a photo of the white house imagine a button "Upload your photo of the White House"

Suggest a photo for this page
Currently we only show the add photo call to action on pages that need photos. There is an alternative for photos which already have one! When they already have one, show the call to action (maybe smaller or more hidden) but with the text "Suggest a photo for this page". The workflow is exactly the same except one difference - the photo is tagged with the categories of the current article and the name of the current article and a link is added to the article talk page 'Photo suggestion: Link to photo'. The idea being that editors can take into account these suggestions.

Article image galleries
Allow users to add to existing photo galleries in articles, and/or create new galleries in articles and allow users to add to them


 * Pros


 * Galleries could potentially be infinite, allowing anyone to add their own photo of the Golden Gate Bridge to the GGB article


 * Cons


 * Adding this gallery to desktop may break Wikipedian expectations of their role as content curators and be controversial.
 * May potentially have to be a mobile-only feature, which might confuse desktop and mobile users.
 * May require curation/patrolling – higher community workload
 * A lot of engineering effort to create something like this from scratch

Update outdated images
A call to action for users to add a newer version of images that are out of date.


 * Pros


 * Together with Nearby, can expand the set of articles that users can add images to


 * Cons


 * Requires some method of tagging images as outdated
 * Still has some element of serendipity
 * Unknown: how many images are actually out of date?

Associate images with articles
Let users associate an image with an article, which either adds the image to the article or the Commons gallery associated with it.


 * Pros


 * users who upload via left nav probably don't know where their images are going – this would help clarify
 * uploads via the left nav aren't categorized and are therefore hard to find, so it's unlikely someone else will add them to the appropriate article


 * Cons


 * may require multiple workflows (one for articles without images, one for articles with images)
 * will require letting user search/browse, and we know our search isn't great

Your ideas here
Your ideas for upload-related features go here!



Editing
Productizing the editing feature.


 * Pros

Users are currently editing at a fairly high rate for a beta feature, and #s of unique users per month are climbing. Having the edit button on mobile would:
 * help shephard more experienced users into the mobile space
 * potentially help onboard new users, as E3’s experiments have shown that simple copyediting tasks can entice new users
 * be an easy win for raising editor numbers generally (many mobile editors are brand-new users)


 * Still needed


 * work out all the bugs (e.g., periodically causes sections to be blanked, anons are editing despite feature being theoretically gated to logged in only)
 * create a MVP midway point for the edit form – slightly better than the current interface, but not yet VisualEditor quality
 * remove the cruft from the bottom of the form
 * log global contributions, not just enwiki

Adding categories
Give users the ability to add categories to their or other files.


 * Pros


 * files without categories can't easily be found on Commons; adding categories makes them more likely to be discovered and used in an article
 * users who upload many files without categories may receive warnings; we'd help them avoid having a bad bot encounter
 * adding categories can be an easy way to create stickiness, encouraging users to keep coming back to check on their content


 * Cons


 * would require adding a UI layer over markup
 * non-hierarchical Wikipedia categories are not an intuitive thing for web users, who are more used to intersecting tags

Upvote/downvote images
Give users the ability to upvote or downvote images uploaded via mobile. Images that get downvoted too low may be automatically flagged for deletion, and images that are upvoted may appear with a special badge/star on mobile articles and in the user's Uploads view.


 * Pros


 * getting mobile users to start filtering/curating content would take the burden off community members
 * could be a logged out activity that entices readers into creating an account so they can upload
 * this is essentially the idea behind wikiHow's tip curation feature, which is quite popular with users
 * Could settle talk page arguments about which photo is better for use on a certain page.


 * Cons


 * we've never used gamefication in this way – a lot of unknowns from the social/cultural standpoint
 * would be a mobile-only feature for now, which might lead to some desktop/mobile confusion
 * would probably require the mobile file page view, which we've been putting off due to complexity

Mobile GettingStarted
Use the concept of onboarding that E3 is experimenting with on desktop and translate it to mobile web – give newly registered users a small suggested task or a quick tutorial of important logged-in features (e.g., uploading, watchlist)


 * Pros


 * we could repurpose the terrible CentralAuth interstitial page and add something pretty/engaging to it
 * new users need education/guidance about Wikimedia projects, and this would be a good just-in-time way to give it to them
 * we have a rough threshold and framework from E3's work, and the analytics tools to make this a data-driven process


 * Cons


 * could potentially break the workflow of users signing up to do a specific thing
 * don't know how annoying this would be on mobile vs. desktop

Your ideas here
If you have other ideas for features not strictly related to uploads that we should work on in the next quarter, feel free to add them here!


 * 1) Undoing vandalism from the watchlist view

Older planning doc

 * Mobile/2013 strategy planning/Archive