paul.nowak wrote: Matt, thanks for the comments. I made an error on the version of Plone. It's 2.5 Plone running on Zope 2.9x.
In regards to the additional products, we have a skin installed and we have a product that we had custom developed for us that connects to a PostgreSQL database. We've looked at slow PostgreSQL queries causing problems and have not been able to find an issue. We've also tested for the case where the PostgreSQL server is down and have not been able to create an issue. We therefor...
In this "year of the mobile web" where pundits everywhere are talking about how "the web is the platform" ....
In this time of "let's get a good enough browser and then mobile will take off" ...
In this time of "Java ME is dead" ...
4 of our 6 first quarter projects have major components in Java ME. These are new applications, from companies who understand the porting issues and the complexities.
Why are they using Java ME?
Because they need to store some of their application logic and/or data locally
Because the app or data needs to be available without the network
Because the application would be dreadfully slow as a web app
Because they are creating a push messaging client that needs more rich interaction than simple SMS (and better interoperability than MMS)
This quarter is not particularly different from other quarters: we get far more work designing applications than designing web sites.
Java has lots and lots of problems. You know what they are. I think they are fixable, and the good news is that we can use the platform now. So many of the browser and widget platform possibilities keep being "just around the corner" and the opportunity is now.
Java ME is going to keep on chugging, maybe even seeing a rebirth, for quite a while yet. SavaJe doesn't spell the death of Java ME either.
About Barbara Ballard Barbara Ballard is President and Founder of Little Springs Design. She's a wireless industry expert in product and user experience design and a developer of mobile user interface patterns. As an evangelist for improved mobile product development process, incorporating device proliferation and user experience, her experience includes phone user interfaces, Java ME, uiOne, mobile web, mobile payments, widgets, NFC, and location services. She is the author of 'Designing the Mobile User Experience' (Wiley 2007) and blogs actively at www.littlespringsdesign.com.
Reader Feedback: Page 1 of 1
#1
Ali Kianzadeh commented on 10 Mar 2008
The problem with j2me is diffrent implemntaion by vendors and restriction on accessing to the api.
For example if you want to make a phone call useing j2me. user have to answer to phone warning 4 to 5 times. And some phone don't allow you to access thier phone book if your application doesn't have certification, of cource you have to buy a 500$ per year licnece from Verisign to solve this problem.
This is too much, sorry!
Subscribe to the World's Most Powerful Newsletters
Subscribe to Our Rss Feeds & Get Your SYS-CON News Live!
Click to Add our RSS Feeds to the Service of Your Choice: