Drupal Mobile

Check out this sweet little jQuery script I found recently. It switches classes and ID names based on browser width. It's pretty slick and even features a built in debug mode.
http://www.csslab.cl/2009/07/22/jquery-browsersizr/

We need to start thinking and talking about what approaches we're going to take in Drupal 8 with regards to design for mobile.

My own opinion is that we should probably be looking really closely at responsive design and how we might apply or adapt the patterns emerging in that field. The idea of "one web" and a unified design and user experience independent of device appeals to me. I don't want an impoverished mobile experience, so please don't assume what I want to see or do just because I'm on a tablet or handset.

Content Types:
Page
Press Item
Accordion Menu Item

Modules:
Mobile Tools - Using Theme Switching
Wurfl
Views
Views Accordion
Twitter_Pull

Themes:
mobile garland - 3 subthemes for Superphone, Feature Phones, Smartphones
RootCandy for Admin

Does anyone have experience with the Domain module and mobile sites? I can't seem to get the current site to understand which belongs to the regular site and what belongs to the mobile. And when the module creates a Mobile Home menu and it doesn't work, I'm baffled.

In this thread the question is asked if a music distribution or separate modules is the best way to achieve turn key functionality needed for a music site. The answer, I believe, is an alternative path.

The alternative path is to abstract things out into an application layer, with Features. There is lots of info about Features on the project page (and it shares some ideas with the now defunct Patterns module), but conceptually this graphic sums it up best:

Having had some experience working with Features this year, I can tell you it is pretty raw. A Feature has hooks and functions to turn on and off things on your site. At its simplest, it will turn on a few modules and change a few defaults. At its most complex, it will need to manually override database variables. It's messy development and takes time. But the real beauty is that it allows developers to focus on functionality instead of technicality. It also allows independent development of features that, combined, can achieve something that looks like a distribution. And for the user, they don't need to know how it works, they just need to know what it can do.

We are lucky, since we have already identified some useful features needed for an art & music Drupal site / mobile application, and perhaps the next step is to refine and prioritize the list.

I recently worked on a photography site that needed both desktop galleries and mobile galleries.

For the mobile image gallery, I wrote a views row style plugin to format a thumbnail image, a main image and a caption area. Though for this site, the caption area is not used much yet.

This is intended to be an initial set of resources for those looking at getting started in this exciting area of drupal/mobile app development.

These resources are largely the work of Sumit Kataria of Civic Actions and my interest and excitement stem from this awesome presentation at Drupalcon SF2010 http://sf2010.drupal.org/conference/sessions/developing-apps-iphoneipada...

The presentation is broken down a little further with some provided code samples and an adjusted json server module.