When the development is the platform is Nokia 40, then transplanted to Nokia 60, Moto V, SE, etc., summarizing about several versions. 1. NOKIA 40, uses MIDP1.0 Nokia UI API2. NOKIA 60, uses MIDP1.0 Nokia UI API3. Nokia MIDP2.0, such as 6600, 7610, using MIDP2.0 4. MOTO V version, using MIDP 2.05. SE version, use MIDP2.06. Samsung S100, S200, C100, using MIDP2.0 development experience: 1. The biggest difference between each model is different on the size of the screen. So you can adapt to the screen size 2 in the game. GameApi without using MIDP2.0 will be more convenient to port, as long as it is packaged, and the rotation can be encapsulated. NOKIAUI API and MIDP2.0 support image selection. 2.0 support is better. Note NOKIA 60 does not support creating variable transparent pictures, so you have to replace other methods. 3. The UI API of the NOKIA 6600, 7610 has a problem (picture rotation), so it uses MIDP 2.0 instead of 4. The machine program supporting MIDP2.0 is roughly the same, of which MOTO, SE, SX are almost. But there is also a fine difference. If SE does not support full screen. So the ScreenSizeChanged method is invalid. 5. Talk about sound play. I don't have to use the sound, one is too hard to listen to the capacity limit. Other models can support MIDI and WAV. However, no 2 MIDI models can be played simultaneously, MOTO V and SE can play MIDI and WAV at the same time, and Nokia will not. Finally, send a little feeling: Let MIDP2.0 standard will be popular! Moto V is really a good machine, but it seems that the CPU is slow. Nokia 6600 BUG is too much! SE K700 Performance Very Good! How many things don't have to support these models, feel Very Cool! :)
