This post originated from an RSS feed registered with Java Buzz
by Fred Grott.
Original Post: JavaME Optimizations
Feed Title: ShareMe Technologies LLC-The Mobile Future
Feed URL: http://www.jroller.com/shareme/feed/entries/rss
Feed Description: A Weblog about Java programming and digital convergence on mobile devices in such areas as P2P and collaborative technology.
There is a reason why I am gathering old JavaONe pfs and slides and Virtual Machine research papers. It is not just oh changing to use Javaolution collection classes optimized for real time but more of what is the average JavaMe developer missing. A JavaME Porting and Game Development company that I discussed these issue with early in 2006 advocates that one doe snot have to worry because with newer faster phones there is no need.
But, that doesn't match logic for two reasons. One, due to ways that javaMe developers earn revenue in producing applications or games we cannot afford to be agnostic towards limiting the devices our game or application deploys on at this moment.
The second reason, comes down to quality of the user experience. If an application game is slow, freezes, or looses memory, and etc it degrades the user experience to the point whereas it destroys the viral marketing that the user completes by praising the product somewhere on internet.
Now, for the bad news. With the exception of the math libraries most JavaME FOSS libraries are not optimized.