Wikipedia is the bomb because of shit like this:
http://en.wikipedia.org/wiki/Mobile_Web

Good background article from 2005, great detail and sociology:
http://www.firstmonday.org/issues/issue5_12/dolan/

Testing if websites are compatible with mobile phones (free tool):
http://ready.mobi

Good Tutorial with Technical Information:
http://dev.mobi/article/content-delivery-mobile-devices

In the past, delivering content to mobile devices has been a very tricky subject. Developers who came into the mobile world were usually confronted with a new and unknown paradigm, where very little information could be found on how to determine devices’ capabilities and to deliver content to them. It was something completely new, and it looked like this information was kept secretly as a precious treasure by those few who had been able to learn it. The aim of this article is to introduce practical examples on how to deliver content to Mobile Devices, making use of sample source code where possible.

In the past, developers had to rely on the very little information that was available on the Internet, and on their own tests via trial and error. Furthermore, the lack of standarisation among phone manufacturers made things even worse, since each of them supported different file formats, and different ways of downloading content, and so on…

As time went by, information slowly started becoming available, communities of Mobile Developers like the wmlprogramming mailing-list were created, and great utilities like WURFL and it’s API’s, WALL, and others came to save us.

Fortunately, each day more resources for Mobile Developers continue to appear. Great examples of this are dev.mobi and .mobi’s DeviceAtlas.

But despite this, we still often lack clear examples on how to achieve certain tasks, or solve particular problems.
So, in this article we present some practical examples on how to deliver content to Mobile Devices, and make use of sample source code where possible.

More Tutorial Stuff
http://contentdeveloper.com/2006/07/delivering-3gp-and-mp3-content-with-sms-text-messaging/

Can the independent Content Developer who is not large enough to ink a deal with one of the major wireless carriers still find a way to easily distribute on demand audio/video content to mobile devices?

I wasn’t sure of the answer to this myself so I’ve been visiting several of the wireless carriers’ retail outlets in the San Antonio area to try out an Open Source SMS Text Messaging Application as a vehicle for delivering audio video content to the current generation of mobile devices.

It’s worth mentioning again that this is a distribution method for the content owner that is not one of the major networks like ESPN Mobile, HBO Mobile on MediaNet etc… Those companies have the resources, scale and relationships in place to form agreements with the wireless carriers that give them placement on the mobile device deck (main menu). Once you get placement on the mobile phone’s deck, a lot of these problems get solved.

This research is more about what can the small to medium sized independent content developer, like a local traditional broadcaster for instance, do today to leverage their audio or video content onto this new distribution platform without one of those negotiated agreements from a wireless carrier in hand.

In short — can you go guerilla with audio video content distribution on the mobile platform? My research so far suggests that things aren’t perfect yet, but there appears to be enough of a critical mass in place to give a qualified yes.

You can deliver your content to their cellphone.

http://developer.att.com/developer/index.jsp?page=goToMarketArticle&id=24100167

WAP Mobile Web Sites and Push Technology

Mobile Web browsing is made possible by the Wireless Application Protocol (WAP), which is a set of standards and specifications that allows a wireless device to access the Internet. Nearly every wireless phone on the market has a built in Web browser that supports WAP, and most of them support the increased functionality of WAP 2.0.

Creating a mobile Web site or a mobile section of your company’s wired Internet site is a great way to advertise your application to mobile customers. Producing a good-looking mobile Web site that gives users a positive experience is a specialized skill similar to the skills required for creating a mobile application. To learn how you can put a mobile Web site to work to promote your application, see Best Practices for Creating a Mobile Section of Your Web Site.

WAP Push Technology

The WAP specification includes WAP Push technology. WAP Push messages can deliver rich content such as images and audio, and they can help persuade customers to respond to your campaign message. With WAP Push protocol, you can send messages and alerts that may include a URL link that the customer can accept to automatically initiate a browser session. From the user’s point of view, WAP Push is simply a mobile Internet page (or WAP page) delivered directly to the user’s device without requiring the user having to start the browser.

WAP Push is the most flexible of the messaging technologies, and most phones support it. However, for older devices, you’ll want to use an SMS message that contains a link to a WAP page.

Mobile Banner Ads

Banner ads are well established on the wired Internet, and they’re becoming increasingly popular among mobile advertisers too. Although mobile screens are small, banner ads do have the advantage of being center stage—because only one ad is displayed at a time, it commands a customer’s attention.

In addition to having eye-catching graphics and copy, your banner ad should behave in ways customers expect when they click it, such as:

* Jumping to a standard landing with explanatory text
* Offering the customer an opt-in for e-mail, SMS, or MMS
* Displaying a phone number for more information (called “click-to-call")
* Providing the company’s address and location information

The process for submitting a mobile banner ad is similar to submitting an ad on the wired Internet. However, since mobile devices have such small screens, many mobile ad companies publish versions of the banners that are tailored directly for a user’s specific device. As a result, you may have to provide the ad in multiple formats (such as BMP, JPG, GIF, and PNG), sizes (usually 120, 168, 216, and 300 pixels wide), and aspect ratios (usually 6:1 and 4:1).

...there’s also a wealth of information about Short Code and Keyword Marketing:
http://developer.att.com/developer/index.jsp?page=goToMarketArticle&id=24100183