Mobile Gateway/Features & Roadmap

There is currently a lot of overlap with possible Wikipedia App features that needs to be consolidated

= Roadmap =

currently drafting
 * Q4F2010 - Port Ruby Gateway & launch on all production Wikis.
 * Q1F2011 - Work on first contribution feature

Reading

 * Reading of articles - scrolling should be easy; collapse sections
 * Viewing edit history
 * Viewing discussion pages
 * Watchlists
 * Viewing of infoboxes
 * Easy search - Large search box that is easy to select (on a touch or keyboard phone) and easy to type

Sharing

 * Share via email or social network

Offline

 * Queueing
 * Save articles for offline reading

= Community =


 * Easy access to whats happening on Wikipedia now (http://en.wikipedia.org/wiki/Wikipedia:Community_portal)
 * Signpost (http://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost)
 * Village Pump (http://en.wikipedia.org/wiki/Wikipedia:Village_pump)
 * Article trending
 * Meetups near me geo lookup

= Contributing =


 * Rate an article
 * Grammar and spell checking
 * Geo-tagging articles/media
 * Sentence editing
 * Uploading media

Admin

 * Ability to do admin actions
 * Revert
 * Undo
 * View article rating dashboard

= Experience =

Slow Speed Smart phones
We need to be able to support smart phones that are still on slow networks. In order to facilitate that we could:


 * Removing images
 * Trimming javascript

Mobile phone identification
It appears that many (too many) phones are not being tracked to our mobile gateway resulting in a bad user experience via our computer-optimized platform. We need to have the capability to identify most, if not all, mobile phones and automatically serve them through the mobile gateway (either mobile. or m.). Ideally, we would have access to a third party directory service that would enable us to automatically identify all mobile models without needing to hand code each one.

Apps for the big four
Rapid growth of smartphones and shift to apps as a primary means of accessing sites means that we face a risk of losing users if we don't have a presence in the Apps marketplace for the big four platforms (Android, iOS, Windows, Blackberry)
 * First priority among these is a simple Android app (similar to our iOS app)

APIs
Major leverage opportunity for our projects is to provide third parties with a strong set of APIs that are well documented and easy to work with. Also, we need to start getting analytics on the usage of our APIs as well as the traffic generated through large mirrors (e.g., Facebook)