As we found out in London, Drupal's mobile admin interface faces some big obstacles to overcome. If we want to to be able to tackle some of these problems in the next release cycle we need focus, the idea being we don't move on to the next item in till we have the previous one licked. I've whipped up proposal for our road map. This is by no means complete, there is plenty of detail to fill in.
I'm hoping we can work on it together.
Words to live by
Don't let the current interface hold us back
Let's not let the current Drupal UI hold us back during the mobile design phase. For all we know the current UI solution could change drastically in the next two years or the Services Initiative could completely change how we interact with data in Drupal.
Let's aim high. Let's design a great mobile interface for Drupal and then work out how much of it we can get in to core. Maybe we can even design a mobile interface that solves problems more elegantly than the desktop version.
Keep to a high standard of design
The Drupal CMS is a web app. This means it's also a mobile web app. As we begin to solve Drupal's mobile issues we should be asking ourselves "What would we do if this was an iPhone app?". We should be aiming to leapfrog our main competitors, not play catch up with them. Let's aim high.
If the user can't find what they want to do, who cares how easy they can do it? We should start with navigation
- Main Navigation
- Short cuts (think the concept, not the module)
- Landing pages
2. Tasks & User Input
- Drag and drop (Moving menu items and blocks)
- Form Submission
- Form item elements
- Tabular Data
4. Launching on the home screen
Some operating systems give users the ability to add web pages to the home screen to launch as an 'app'. We can take advantage of this local home to enhance the user experience.