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.

Imminent
 * Search suggestions 19956 – developed by a user, will be released soon
 * Inter-wiki language links 19834 – main request from new mobile gateway feedback

Bugzilla


 * Dynamic fonts support in mobile gateway 	28515	High - HACK, Nuriam, not yet Android 2.3X


 * Font sizes preference for Wikipedia Mobile	19921	High - pitch and zoom, preset sizes for featurephones


 * "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


 * Add "e-mail to friends" functionality to MobileFrontend (prefill email)	24359	high – include SMS, HACK


 * Did you mean corrections for search 	29560	High - just surface from form, easy - TECH Day? - Arthur


 * 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


 * SMS/USSD gateway for Wikipedia access (simple at first) 31614 High HACK, related to Summaries?


 * 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


 * Log in and "watched articles" list in Wikipedia Mobile 	24387	Medium - login needed, watchlists UX


 * 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)


 * Wikipedia.org should detect mobile browser and locale	28815	Medium - Squid layer, med difficulty, Ops support


 * 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

Internal grab bag
 * 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
 * Citation entry by photo of book - see brainstorm page
 * Articles near me missing photos, and photo upload
 * 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

Parul


 * Auto-complete search – overlaps with Search Suggestions?
 * 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

App Features Wishlist

http://meta.wikimedia.org/wiki/Mobile_Projects/App_Features_%26_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

http://www.mediawiki.org/wiki/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

India and Brazil research
 * Summaries - widget to scrape HTML, High for featurephones, see bug above
 * More media - yes, but not heavy
 * Editing - or entry points into editing
 * Language detection - see above
 * Handset detection (already implemented)