Extending the WP MobileAdmin Plugin

[Update] - This plugin is stale

Sorry, but this hasn’t been maintained in a while and is probably unsuitable for use in current versions of WordPress. It’s also unlikely that I’ll be updating it in the future, but the code is out there and I heartily encourage anyone who wants to take it over / fork it to do so.
——————————————————–

This is the place to go to find information on building your own “plugins” to extend the functionality (or add style, etc.) to the WordPress MobileAdmin plugin.

Plugin System Overview

This page will give a basic outline of the plugin (or “sub-plugin”) system used by the Mobile Admin Plugin, including explaining how plugins are loaded.

Writing a new plugin - Basics

This will cover what is needed in order to create a basic plugin that matches a particular browser or browsers, by user agent. The two ways of specifying matching user agents (partial string matches and regular expression patterns) will be explained.

Writing a new plugin - CSS & Javascript

The most common use case for writing your own plugin would be to provide a different look and feel to a particular browser that may have the ability to support more fully featured styles, etc. This will build on the example used in the “Basics” section above, and show how to send custom CSS and/or javascript files for the particular browser(s) that you’re targeting for your plugin.

Writing a new plugin - Advanced

This section will cover the additional options available to you for further altering the structure of the various pages supported in the mobile admin interface, and how basic plugins will inherit behavior from the “default” plugin that you can then override to do nearly anything you’d like.

Anatomy of the “Default” and iPhone plugin [ Coming soon ]

This page will give a detailed breakdown of everything the “default” plugin does. All other plugins extend the functionality provided by the default plugin, so this guide will cover everything the default plugin does, and (where applicable) how the iPhone plugin (as an example) makes slight tweaks to do things differently when necessary but mostly relies on the underlying default plugin behavior.