Guys, is "porting mobile games" to 1 handlet and 1 another, and so... that big deal? I mean... port it to Nokia 7250 and Nokia 7250i will bring me that many problems? Of course, we want to focus as many handsets as we can, and i know that porting the game for a motorla handset will be diferent that porting the same game to a nokia... but, whats the best solution? What are the common and the diferent features that mostly can bring problems to the process? For example, the api... the processor... and so and so. Are there any tutorials about the subject? thanks.

Most studios employ an SQL database that lists every model they support along with the screen sizes, APIs, keyboard mappings, audio capabilities, etc. A Python script would take a generic version (or one of the many generic versions) and run it through the database script to modify it for the handset. Then the resulting executable is loaded onto the matching device for testing. In most cases it works, but there are many devices which require hand-tuning and debugging. This is how Morpheme and JAMDAT does it, btw. But those guys have been doing it for years and thus each new handset in the market is incremental work for them. Building this database and the toolchain from scratch is a very costly proposition. You can buy the whole toolchain from guys like Tira Wireless (http://www.tirawireless.com), if you want to save on time and efforts. Tira lists 500 handsets in its database, btw.

You will get most of the surprises in supported APIs and keyboard mappings. If you think there is only one API for music and sound, think again. Each carrier and each handset manufacturer has preferred set of APIs. Add to this multiplayer APIs and 3D APIs and multimedia APIs etc, you end up with a lot of combinaison and permutations to deal with. No wonder the whole market is fragmented and developers are pulling their hair out.

thanks an interesting point. thanks mate. Now, i'm not developing a multiplayer-3d games. I'm using polyfonic music and some wav sound... that reduce the list only to music and sound api?

By the way, the publisher is the one that do that job? isn't it? thanks.

The publishers/developers I spoke to budget 3-4 months to make a version on one handset and another 2 months to port over to all the other (or at least a reasonable number of other) handsets out there so yes it is actually quite a big deal (50% again on your project development time).