I received some very nice feedback from my last post yesterday that included a very legitimate point about local apps that harness the web versus extending the web model as one does in the case of AJAX. Honestly, if my goal was to develop Windows Mobile-specific solution then the local app harnessing the web would probably make the most sense.
Here’s just a few random thoughts about my interest in getting ASP.NET AJAX to work with Windows Mobile…
My main interest in getting the ASP.NET AJAX stuff to work is that I'd like to find a solution that is reasonably easy to write that works across both Windows Mobile devices and the desktop. My hope is that once I figure out how to get the ASP.NET UpdatePanel to work on Windows Mobile that I can publish the scripts so that people can start building ASP.NET AJAX sites that'll automatically support both mobile and desktop clients. Hopefully, others may be interested enough to take the scripts even further.
What's funny is that IE Mobile (especially 6.12) provides excellent support for building AJAX-enable sites as long as you're building them manually - which can be painfully time-consuming. On the other hand, ASP.NET AJAX makes building simple AJAX pages trivial. IMHO, it'll be some time before IE Mobile supports ASP.NET AJAX out-of-the-box. The IE Mobile DOM is currently just missing too many things. A near-term solution, even if limited in power, is needed.
I don't want to see the ASP.NET AJAX story evolve too far without considering where mobile devices fit in. I'm hoping that by publishing mobile-enabled version of the ASP.NET AJAX script files that at least a few people will start including Widows Mobile as a target of some of their sites. This'll hopefully lead to Microsoft getting some feedback on the ASP.NET AJAX mobile experience.
As we all know, some solutions are best solved on the web (and many are best solved locally), I'd like to see more of those apps that are best suited for the web provide mobile users with the speed and convenience of the AJAX experience without requiring devs to manually wire everything up. For now ASP.NET AJAX seems to be one of the best choices for that.
All that said, this may be a fool’s errand J
Posted
Sep 21 2007, 10:58 AM
by
jim-wilson