Comments on: Mobile Ajax and Predictions of J2ME's Demise http://pathfindersoftware.com/2006/08/mobile_ajax_and/ The Fastest Way to Launch Successful Software Thu, 19 Jan 2012 16:36:03 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: mobile marketing software http://pathfindersoftware.com/2006/08/mobile_ajax_and/#comment-5667 mobile marketing software Tue, 12 Feb 2008 21:57:07 +0000 http://www.pathf.com/blogs/?p=485#comment-5667 <p>Ajax is still far from mobiles, thats because mobile http connection is still slow and limited. Beside browsers on mobile phones are very different, so it's very hard to prepare something smooth for ajax mobile.</p> Ajax is still far from mobiles, thats because mobile http connection is still slow and limited. Beside browsers on mobile phones are very different, so it’s very hard to prepare something smooth for ajax mobile.

]]> By: Louenas Hamdi http://pathfindersoftware.com/2006/08/mobile_ajax_and/#comment-5666 Louenas Hamdi Sun, 01 Oct 2006 04:57:15 +0000 http://www.pathf.com/blogs/?p=485#comment-5666 <p>Ajax will replace for sure the way mobile online apps are architecture for eliminating the unnecessary round trips to the server by providing some caching, queuing of requests, asynchronicity, client side binding etc. Ajax is already good in mitigating the uncertainties of the cellular network and providing a good user experience. But right now and certainly not in the next three years at least, we can not talk about replacing J2ME or .NET on the mobile devices. First because it's not doing that in the desktop world and second lots of the applications run lot off business logic on the client side and need offline data for long disconnected periods. Flash Lite is an other technology that could take a big part of the pie in the near future because it (should) provide a neat user experience, push mode, same look and feel, offline capabilities, caching, etc.</p> Ajax will replace for sure the way mobile online apps are architecture for eliminating the unnecessary round trips to the server by providing some caching, queuing of requests, asynchronicity, client side binding etc. Ajax is already good in mitigating the uncertainties of the cellular network and providing a good user experience. But right now and certainly not in the next three years at least, we can not talk about replacing J2ME or .NET on the mobile devices. First because it’s not doing that in the desktop world and second lots of the applications run lot off business logic on the client side and need offline data for long disconnected periods. Flash Lite is an other technology that could take a big part of the pie in the near future because it (should) provide a neat user experience, push mode, same look and feel, offline capabilities, caching, etc.

]]> By: Thomas Landspurg http://pathfindersoftware.com/2006/08/mobile_ajax_and/#comment-5665 Thomas Landspurg Fri, 18 Aug 2006 17:27:21 +0000 http://www.pathf.com/blogs/?p=485#comment-5665 <p>Ajax is a good think to solve current HTML flaw, but it's probably not the only solution for mobile (and could be even create worst result if badly used)</p> <p>I think mobile might be the opportunity to solve the current flaws and difficulties of creating web based rich UI, and to create a better framework by using existing pieces together: html, j2me, vector graphics, JS/Ajax etc...<br /> ( <a href="http://blog.landspurg.net/web20back-to-the-roots" rel="nofollow">http://blog.landspurg.net/web20back-to-the-roots</a> )</p> Ajax is a good think to solve current HTML flaw, but it’s probably not the only solution for mobile (and could be even create worst result if badly used)

I think mobile might be the opportunity to solve the current flaws and difficulties of creating web based rich UI, and to create a better framework by using existing pieces together: html, j2me, vector graphics, JS/Ajax etc…
( http://blog.landspurg.net/web20back-to-the-roots )

]]> By: Martin Paulo http://pathfindersoftware.com/2006/08/mobile_ajax_and/#comment-5664 Martin Paulo Thu, 10 Aug 2006 21:44:11 +0000 http://www.pathf.com/blogs/?p=485#comment-5664 <p>Surely the two are orthogonal? As the earlier comment makes clear, J2ME apps work without the network needed, and Ajax is dependent on it.</p> <p>And the flaws in the J2ME business model are even more apparent in the AJAX model. IE: you have closed garden vendors who try to control what goes into their network, and demand your first born as payment for data traffic. Neither are going to fly until the business models are truly fixed. I'm not holding my breath... </p> <p>Further, are all phone vendors going to render AJAX identically? At least with J2ME there is a high degree of cross platform support. It isn't ideal, but it is better than having to create different scripts for different browsers.</p> Surely the two are orthogonal? As the earlier comment makes clear, J2ME apps work without the network needed, and Ajax is dependent on it.

And the flaws in the J2ME business model are even more apparent in the AJAX model. IE: you have closed garden vendors who try to control what goes into their network, and demand your first born as payment for data traffic. Neither are going to fly until the business models are truly fixed. I’m not holding my breath…

Further, are all phone vendors going to render AJAX identically? At least with J2ME there is a high degree of cross platform support. It isn’t ideal, but it is better than having to create different scripts for different browsers.

]]> By: Pavel http://pathfindersoftware.com/2006/08/mobile_ajax_and/#comment-5663 Pavel Thu, 10 Aug 2006 21:01:45 +0000 http://www.pathf.com/blogs/?p=485#comment-5663 <p>Well, mobile ajax can be relevant perhaps even significant technology one day, but it has long way to go to replace J2ME. Mobile devices can't rely on availability of relieable network connection and this is vital for Ajax to work. There are (quite common) use cases where reliabilty of the network connection won't be solved even with improvements in GPRS/UMTS/whatever technologies. What about users abroad, with all those interconnection problems and ridiculously high roaming rates for data ? J2ME don't rely on permanent connection and thus will work even in scenarios such as flight mode etc. IMO 90% of the mobile applications usage now is without any network connection an in such conditions J2ME thrive and will further improve with forthcoming MIDP3 release.</p> Well, mobile ajax can be relevant perhaps even significant technology one day, but it has long way to go to replace J2ME. Mobile devices can’t rely on availability of relieable network connection and this is vital for Ajax to work. There are (quite common) use cases where reliabilty of the network connection won’t be solved even with improvements in GPRS/UMTS/whatever technologies. What about users abroad, with all those interconnection problems and ridiculously high roaming rates for data ? J2ME don’t rely on permanent connection and thus will work even in scenarios such as flight mode etc. IMO 90% of the mobile applications usage now is without any network connection an in such conditions J2ME thrive and will further improve with forthcoming MIDP3 release.

]]>