Don't be very deep, so far, just have some simple games. It feels that simple J2ME does not have much place worth research. There are too many restrictions.
The CPU speed is too slow, so the optimization of the code is very important, everything running on the simulator is completely operational. I want to do a game, in addition to those on the PC, this is the biggest challenge. Step gradually optimize your code to the point where you can run smoothly, full challenge.
In addition, if you do a network application, it is more troublesome. Midp1.0 does not require support socket, only support http, it doesn't feel there is nothing, when I discovered with my brothers, I found it according to the network model, Socket is the next protocol of HTTP, why not support? I think this is a mobile phone interface problem. He has its own set of things. Whether it is Socket or HTTP to mobile phone should be the same level. Unlike the PC. Therefore, the network application on the mobile phone seems to be HTTP, combined with a similar server such as servlet, is still sufficient in terms of performance, and there is too much additional information in HTTP. The information utilization is not high, the PC does not matter, but it doesn't matter, The GPRS network is more obvious in k to count.).
Also, there is no file in the standard MIDP, only records. It is really not used. The specific limit is not seen, but from the WTK's demo, it seems to be very simple, which means that there is not much thing. But it should be available on general data storage. It seems that which manufacturer's API has a class read class.
The manufacturer's API is very important to the development, especially some things that have been dealt with mobile phone hardware, send text messages (did not have done), vibration, background light, sound, etc., specific to check the manual, think this NOKIA is well done (actually there is no use of other manufacturers).