But this is where you need to be very, very careful. Now you could, of course, write one application and it would be servable on both the desktop and the mobile devices. And that's the whole idea about the multi-channel thing. But, I typically end up cautioning people because your mobile application is rarely the same application as your desktop application. Even if from a rendering perspective you could make it work, you typically want a different UI flow for your mobile users, different information presented for your mobile users, then for your desktop users.

An example I always give, is an inventory application. Say you have a desktop inventory application. You could translate that to a wireless mobile inventory application, but the point is, it's two different jobs that are going to be using these two applications. The clerk at the desk is sitting there generating orders, managing or processing purchasing orders whereas the mobile user's inventory application is out in the warehouse picking from the shelves. It's two different things. It's called an inventory application, both for the desktop user and the mobile user but it's two different things they're doing; they have different jobs. So very often, you have to think about the mobile job as very different and requiring a different UI flow and different information, different application logic then the desktop one.