warriormill

Short answer yes, why not? The key is to come up with what you expect your user to get put off it; and then from the point of view of the user, and what they expects out of it. The intersection of the two sets gives you the minimum required to successfully go mobile.

Going mobile can mean different things and because of that implementation may vary. In most cases it means a mobile version of the current offering via a mobile browser. Now I chose my previous words carefully because mobile could mean two things; a mobile application or a mobile website.

Mobile Web Site

This is a mobile version of the standard website. It may or may not contain all the information the main website has. Mobile sites currently are stripped down with plain html and css, currently only next gen phones such as the iPhone, android and windows mobile 8 phone support more complex CSS and javaScript. Even though this is quite a limitation it those not mean that you cannot have a usefull and compelling mobile site that runs on even a cheap prepaid phone. The key is to simplify and keep it clean.

Mobile Applications

Mobile applications fall under two buckets:

1. Mobile Web Application: This is a mobile website that is not just informative but provides some functionality to the user.
2. Phone OS Application: Most phones use the JAVA ME framework for developing and running application on you phone. The iPhone uses objective-c and cocoa for its rich applications, And Windows Mobile Phones use the .Net Compact Framework.

The hard part is figuring out exactly where your demographics lie and the proper method of content delivery.

I recently discovered a iphone app from WildCardNetworks.
This nifty little apps lets you store calling card with access numbers and pin  so that then you only have to pick numbers from your contacts with you ever having to put the pin in ever again. This has improved my frustration when dialing international…since i have to do it every day.