Here at Unkasoft we've divided our development in two quite different sections:

- On the one hand, we've got a tools departament, where we work in our product called Battlewizard. Soon, we'll tell you more about it (you'll get bored :) but in advance I'll tell you it's a complete system to develop mobiles games avoiding the hell of device portability between different vendors, screen sizes, capabilities, etc.

- In the other hand, we've got the games division, where we use Battlewizard and its J2ME API to develop our final games (one of them in test phase, two more in programming and another one in design phase). This allows us to mantain only one single code base for all target devices, and our final games runs in a wide range of phones (this is one of the keys sides that all operators take into account). This isn't usual in mobile development world, even there're dev firms (like GameLoft) that have one codebase for each target device, and each codebase with its own manager. At small studies like ours, that schema isn't feasible and we think that isn't the best approach to fragmentation problem.

That's all about programming.
Then, we've got a QA department, where we test both Battlewizard and our final games for all supported devices.
This is a real muddle! Think about test the same game at 30 different phones (our target is to reach up to 200 supported devices!). You should see Jorge while he's testing two versions of The Fourth Seal with one phone in each hand :)