Wikimedia Mobile engineering/Features

This page is intended as a whiteboard for collecting feature ideas and taking a first step at organizing them. Please no deletion here.

All features below are general, although some may be more relevant to an app, and some more to the mobile site. The intention is to bring all forms of mobile access up to a minimum level of functionality and usability.

Imminent on mobile site

 * Search suggestions 19956 – developed by a user, will be released soon
 * Inter-wiki language links 19834 – main request from new mobile gateway feedback
 * Beta release opt-in required to see new features, go to opt-in
 * Mobile switch-over of other wiki sites 32272 - requires community participation and here are instructions
 * Full-screen search 32701
 * Puppet monitor to ensure that our customized varnish logging daemon is always running RT ticket 2060

Android app

 * Version 1.0 includes "Nearby me" article search
 * Version 1.0 tracking bug 31447
 * Version 1.1 tracking bug 31805
 * Localization (Turkish, Russian and others) 32265

Immediate next steps

 * Finish first implementation of search suggestions (full-screen and better plus graphic)


 * SSL and login - first step toward editing and other forms of participation, then other features become possible, and hopefully some of these will motivate readers to login


 * Photo upload for existing editors, to Commons only, app prototype (may be based on Weekend of Code contributions)


 * Possible tie-in with articles near me or a known article (some way of identifying photos for certain articles)


 * Possible staging area for uploads with curation method, or just part of normal workflow on Commons initially


 * Photo upload solution for iPad, such as making the main uploader functional or a link from normal site to iPad app


 * Here is the page for recent feedback on the Upload Wizard from Wiki Loves Monuments: Upload Wizard Feedback


 * Add beta opt-in to main mobile site and opt-out to beta mobile site


 * Possible performance issues - JS/CSS bundling, latency history reporting


 * Possible Mood bar on beta site

India Hackathon
Help make mobile Wikipedia a world-class mobile experience. There is so much to do, and the results will directly benefit users in India. Here is a high-level summary:


 * Participatory features and apps - Make mobile Wikipedia editing-friendly and more engaging, in ways that really make sense on mobile devices. These features are among the most groundbreaking in the Mediawiki world - help our mission of retaining and growing the editor user base!


 * Carrier solutions - Wikimedia staff are actively engaging carriers around the world in groundbreaking projects such as WIkipedia Zero, which gives mobile users in developing countries free access to Wikipedia - that includes India!


 * UI and Usability - Our UI experts will be on hand to help you craft some exciting changes to the overall user experience and any new ideas you may have.


 * Languages on mobile - Among other vital tasks, help create the page visitors see when they access Wikipedia in India - feature Indic languages and tailor the design to an Indian audience.

Key resources

 * Mobile Projects workspace
 * MobileFrontend extension for MediaWiki (the code that powers Wikimedia's mobile sites)
 * MobileFrontend API
 * Live API

Please use bug reports to track progress and make comments.

Features that were worked on at the Hackathon are prefixed with H.

Participatory features and apps
Most of these features rely on mobile login, which is in progress.

H * Articles near me missing photos - part of the Weekend of Code challenge
 * Weekend of Code submissions
 * 19920 - Articles near me in mobile site
 * Android bugs are details relating to current function in Android app: 31891, 31954, 31956, 31957
 * Yubi on Android

H * Photo upload
 * Weekend of Code submissions
 * "Share with Commons" app:
 * On Android Market:
 * On github:
 * The application adds a "Share with Wikimedia Commons" option to the "Share with" menu that's available in the Android Gallery app. That is, when you're viewing a picture on your phone, you can easily upload that particular picture to Commons through the same process that's used for Picasa and other websites. It doesn't prompt for categories and the license selection is basically just a template field, but it gets the job done. Images uploaded using the app are added to this category:
 * 31979 - Android app
 * 32286 - Mobile Web
 * 31978 - HTML5 Support
 * 24387 - Login
 * 32292 - Notifications system - jeblad prototype and notes
 * Yubi on Android

H * Share or "e-mail to friends"
 * Prefill email, or SMS
 * 24359
 * Ankit


 * Custom map apps
 * Having custom maps that can be developed using GPS data as well as generated and shared via mobile devices could open up contributions to content-specific maps on Wikimedia sites. These custom maps could be incredibly useful to view with articles on places, treks on topics such as hiking in the Himalayas or Alps, tracing historic battlegrounds, or trekking though wildlife sanctuaries. Android recently released an open source app named CustomMaps to help build such apps. Check out Google custom maps.
 * 32274


 * Watchlists - keeping track of watchlists on mobile devices
 * 32290 - Main
 * 24387 - Login
 * 32292 - Notifications system


 * Proofreading annotation on mobile and beyond
 * Annotate articles to edit later, such as typos and simple fixes, requires login
 * 32329 - Main
 * 24387 - Login
 * 32292 - Notifications system


 * Article feedback
 * "Did you find what you were looking for?" (Y/N or comment)
 * Project page
 * Live API search on "articlefeedback"
 * 32293 - Main
 * 32292 - Notifications system


 * Moodbar and comments - seeing Feedback Dashboard and writing comments
 * Feedback Dashboard mock-up
 * Feedback Dashboard project
 * Possibly include some common links (including that user's feedback and the cheatsheet) in a drop-down list to make comments easier to make
 * The experienced editor could easily add that user's talk page to their watch list
 * API for submitting comments is in progress
 * 32304 - Main
 * 24387 - Login
 * 32292 - Notifications system


 * Add GPS coordinates within a location-related category
 * Link up with desktop to refine
 * Needs some API support on main platform
 * 32271

Carrier solutions
H * Show English search result if none in other language
 * Required by notable operator in India
 * Falls back to English Wikipedia only
 * Top 5 languages in India are required, including local content
 * 32541

H * RSS feed of Article of the Day
 * Requested by most operators
 * Easy way to include Wikipedia in the carrier's portal
 * Should we make this like a "self-serve" option?
 * 32699

H * J2ME app
 * This is clearly required in parts of the world where smartphones are not prevalent
 * One Indian operator requested keeping the article history in the app
 * 32700


 * New WAP view
 * Change initial page into intro (of long but constrained length), simple infobox extract, and Table of Contents as simple links (this is a top request from the India and Brazil research)
 * 31714

H * SMS/USSD gateway for Wikipedia access (simple search at first)
 * Related to New WAP view 31714
 * Can push Featured Articles (possibly by carrier)
 * Virtual server on Labs
 * txtWeb sample app
 * 31614
 * Tata set up short code and USSD connection
 * Jeremy Thurgood, Praekelt - USSD app plus final output by SMS
 * txtWeb - enhanced SMS app (infobox, TOC, intelligent summary)
 * API for plain text needed

H * Wikipedia Zero heading banner
 * Simple branded banner for an operator running the Zero program
 * To be added when we detect access from a limited number of known IP addresses
 * Includes basic text of operator name in limited font styles
 * Browser view is without images and WAP view must be supported
 * 32001
 * Abhishek

H * Wikipedia Zero warning
 * When the user selects to view images or an external link, the heading banner changes color to red and a warning message appears, similar to: "You have selected an action that requires a charge for data access, click to continue"
 * 32002
 * Abhishek

H * Wikipedia.org should detect mobile browser and locale
 * A mobile-specific version of this page must be created, or country-specific landing pages
 * Squid layer, med difficulty, Ops support
 * Readers study says people often go straight to Wikipedia.org on mobile, as opposed to Google search, especially in Brazil and India - both quantitative and qualitative
 * Could also use MaxMind for country detection
 * 30389
 * Bob and Deval?

H * Country-specific landing pages
 * India in particular (English and links to other Indic language versions)
 * See Page views by country
 * Related to Wikipedia.org feature under UI and usability, above
 * Once implemented, instructions could be similar to: Mobile homepage
 * 28815
 * Ramakrishnan and Shashand


 * Mobile data usage per person per month
 * To help operators define data usage caps per country or region

UI and usability

 * Horizontal scrolling enabled when content exceeds screen width, typically photos or tables
 * 32123, related to bugs 31931, 22187, 31892.


 * "Did you mean" corrections for search
 * Just surface from form
 * 29560


 * Font sizes preference for Wikipedia Mobile
 * Preset sizes, maybe pinch and zoom later
 * 19921


 * Improved photo handling 1
 * Scale photos to screen width or nearest standard size in the main article view
 * When a photo is clicked and the photo is larger than the screen width, allow horizontal scrolling
 * 31931


 * Improved photo handling 2
 * Filter info page to show a subset of information
 * Allow click to open to show original image at screen width but user can use zoom and scroll as supported natively
 * 31933


 * Wikipedia menu
 * Turn icon into Home link
 * Include Random and inter-language links
 * Some menu items are general Wikipedia features, some are specific to the article
 * 31399


 * Featured Articles (important in India) - or Featured Pictures in Wikipedia menu
 * With inter-language links and other Wikipedia menu items
 * 32269

H * Articles trending on landing page
 * Could be combined with country-specific landing page, below
 * Ramakrishnan

H * Create article stubs offline
 * Like Evernote app

The following three ideas are in mock-ups by Nishank, Vishvwamitra, Maharshi and Sumit from BITS:

H * Related Random using links
 * As opposed to general random, how about related random using links, both from and to
 * Results in more focused discovery
 * 32542

H * Show relationship
 * Two terms, like names of famous people
 * Show links that connect the terms, including the sentences the terms appear in
 * 32543

H * Ranked related links
 * Show from and to links, sorted by various ranking methods, such as:
 * Number of page views
 * Ratings (Article feedback)
 * Last edited
 * Relevance (not currently defined)
 * 32544


 * Saving content for offline reading, and possibly offline editing (Editors and Readers study)
 * Can we use printable version and PDF?
 * HTML 5 and apps for sure
 * Kiwix app is a proof of concept
 * 32270


 * Athena
 * http://www.mediawiki.org/wiki/Athena

Languages on mobile
H * Localize Android app, format needs to be integrated in translatewiki
 * Multi-tiling input app on Android
 * 31467
 * Turkish and Russian done


 * Language prefs in inter-wiki links
 * Tiering languages so most likely languages are at the top of the list, or save most recent languages visited
 * 32254

H * Test Narayam on mobile, which phones don't have jQuery support
 * http://www.mediawiki.org/wiki/Extension:Narayam
 * 32267
 * For input like Narayam extension? For output like the core MediaWiki LanguageConverter features for Chinese, Serbian, etc? Or something else?
 * For input, ideally working on WAP as well, needs more Indic language support

H * Transliteration input extension
 * Currently appears on Hindi Wikipedia
 * Works on iPhone
 * Manish / Mayur mayurdce at gmail dot com
 * Localization team made progress on this with Narayam

H * Dynamic fonts support in mobile gateway
 * Narayam not yet Android 2.3X, rendering engine required
 * 28515

H * Universal language selector and keyboard
 * Arun's mock-up
 * 32539


 * QRpedia

Other possible features are shown below:

Potential new functions

 * Photo upload for articles near me without photos, with some basic photo curation, for current editors only initially - requires login (Weekend of Code may generate some work) - see above


 * Add GPS coordinates within a location-related category, link up with desktop to refine - needs some API support on main platform


 * Augmented Reality with articles near me - like Wikitude app


 * Create a new article - upload a photo and create a stub


 * Article Feedback Tool - current V1 in mobile form, possibly combined with MoodBar or simple calls to action


 * Annotation - see Brainstorm and Wikignome


 * Casual communication - see Brainstorm - should this require login?


 * Featured Articles, Pictures, etc. - can be part of menu upgrade or treated on their own


 * Fundraising mechanisms - one idea is to provide versions of the iOS and Android apps that "cost" money and are really convenient ways to donate

Photo and location ideas
(priority not clear but could be good for Hackathon)
 * Slideshow or swipe-able view of photos in article, and also related images from Commons (when present in an article)
 * Link to related pictures but change language of referral regarding "Wikimedia Commons has media related to..." on main site
 * Photo upload - user-generated into Commons (as part of article editing later), currently part of Weekend of Code and could apply to Wiki Loves Monuments
 * Easy way to curate photos, possibly as part of photo upload or new editor
 * Articles near me missing photos, easily add photos - currently requires GeoNames database
 * Add GPS coordinates within a location-related category, link up with desktop to refine - needs some API support on main platform - see New functions, above 32271
 * Custom map apps - Having custom maps that can be developed using GPS data as well as generated and shared via mobile devices could open up contributions to content-specific maps on Wikimedia sites. These custom maps could be incredibly useful to view with articles on places, treks on topics such as hiking in the Himalayas or Alps, tracing historic battlegrounds, or trekking though wildlife sanctuaries. Android recently released an open source app named CustomMaps to help build such apps. Check out Google custom maps.

Other high priority

 * Browsing history across devices (Readers study), might require login and profile work, or is this search or bookmarks?


 * Device partnerships for "native" Wikipedia search, like on iPhone


 * "Find" function for Wikipedia Mobile 	20146	High - some UX, not too hard


 * Reformatting of Portals (multiple columns formatting too wide)	22187	High - not lock screen? not force squish, prototype


 * Support for collapsed infoboxes and tables in Mobile 	29504	High for featurephones, difficult but less than edit, Articles iPhone app research


 * Summaries - widget to scrape HTML 31612 High for featurephones - slider tool for Webkit scrapes HTML - marked as duplicate of New WAP view, bug 31714 above

Remaining in Bugzilla

 * Auto-complete based on history too 	31598 Low


 * Give projects the opportunity to add mobile specific JS/CSS 	22659	Medium - project-specific, get admin feedback, stylesheet per device


 * Add geolocation functionality to MobileFrontend to support Articles near me 	19920	Medium - HTML5 only, some UX and Open Streetmaps integration, new phones only, already in Android app


 * Support language variants (different language interfaces - same wikipedia) 	21806	Medium - do-able, related to inter-wiki language links


 * Display the categories 	22660	- UX, get feedback


 * Option to permanently see mobile frontend from PC render 	29503 	Medium - last part


 * Distinguish external links from internal links. 	30831	medium - CSS easy


 * Random button for Wikisource 	30902	low - easy workaround Namespace 0


 * Cleanup duplicate CSS for mobile devices 	31050	medium (good idea) - depends on the project for Admin CSS (see bug 22659 above)


 * Links to page history don't surface actual revisions 	29387 Medium - UX, same as edit history below


 * Keep home-random menu expanded after clicking random 	30842 Medium - test on devices


 * Merge search icon into search bar (requires new graphic) 31934

Leading app UI
app overview
 * tabs
 * read later list
 * visual history using article graphics
 * find in page
 * font, brightness, color
 * arrange bookmarks in folders

Internal grab bag

 * Start new article with a photo, stub
 * Keyword search in languages other than English needs improvement (Readers Study)
 * New Page Patrol, possible smartphone app for specific tasks
 * Article rating as entry into annotation and editing
 * Annotation, private or public, separate from discussions and as entry into editing
 * Simple comments or discussion, at minimum notify Talk-page participants of replies - see Brainstorm
 * Citation entry by photo of book - see Brainstorm
 * Photo upload
 * Articles near me missing photos
 * Add GPS coordinates within a location-related category, link up with desktop to refine
 * Curating photos
 * Enlarge/reduce text easily (such as by number keys), with reflow - pitch and zoom easy, presets CSS for featurephones, see bug above
 * Dynamic header/search width to fit multiple screens
 * Voice input search, aka Apple demo (possibly no work required)
 * SMS/USSD gateway for Wikipedia access (simple at first) - HACK, see bug above
 * Wiktionary and WikiNews

Extras from mobile research

 * Auto-complete search – overlaps with Search Suggestions?
 * Transliteration using English is common in India
 * Confirm deletion of bookmarks only (not creation)
 * Multiple tabs
 * wapedia includes an option when clicking on a wikipedia link to open it in the app – Intents on Android
 * Prompt users to add a photo by asking when browsing photos

India and Brazil research

 * Summaries - High for featurephones, see "New WAP view" above
 * More media - yes, but not heavy - see Featured Pictures above
 * Editing - or entry points into editing
 * Language detection - see above
 * Handset detection (already implemented)

App features wishlist
Mobile Projects/App Features & Roadmap

Qgil:
 * Share this – easy with Android Intents, maybe clickable links in browser on iOS
 * Patrol a new article, could be suggested by the app - complex, Brandon
 * Geotag an article
 * Upload and embed photos - comm apps POC Wikisnap exist, basic already in gateway
 * Add comment on discussion page – using newsection edit is simple, LiquidThreads integration longer term - complex
 * Community Portal – learn more about Wikipedia, Things to do, RSS feed of The Signpost - easy Hackathon
 * Editors near you - complex
 * Landing page - based on Last news + On this day + Featured article + Pic of the day + Media of the day - complex?
 * Related articles, leaving genuine links to external articles - External links - low
 * Limit searches and browsing to pages of certain quality - no good UI, not all languages - complex
 * Edit profile – auto-input from device info, insert user banners as gallery?, auto location update, auto update of “Pictures I have loaded from my device” - complex, no SSL concurrently

Ryuch:
 * Proofreading mode, could be similar to or same as annotation - not so complex if simple text, get feedback

Other:
 * SuggestBot to suggest a mobile task - comm dev, based on past contributions
 * LiquidThreads integration

Wikimedia services

 * Bookmark for device pre-install - in progress
 * Search API
 * Share API for upload to Commons - part of upload
 * Accounts and OAuth API - and OpenID, both require SSL on mobile - Medium

Mobile site wishlist

 * View edit history - time, username, edit, then diff (basic diff appears now), clear workflow to see edits
 * Community – Signpost, Village Pump, Article trending, meetups near me - hackathon
 * API usage data and traffic through large mirrors like Facebook (open RFP) - platform, tokens, not so complex but time-consuming

Mobile site testing feedback
Mobile_site_rewrite/Testing


 * Move “Mobile View” to top - UX needed
 * Reduce line-height - CSS percentage, test across devices, UX
 * Keys for navigation - not complex, some UX
 * Content lists non-touch - ?
 * Thumbnail to screen width, or inline if screen is more than 300 pixels wide - UX, store in some standard sizes
 * Mobile editing UI - complex, Trevor, Ines, Brion
 * Change table.metadata to metadata - 31510

iPhone app

 * disable the automatic download of the featured article when launching Wikipedia Mobile for iPhone?