Tuesday, September 27th, 2005>p>Dan Grossman, the VC that brought us Top 10 Ajax Apps, has now told us what is wrong with Ajax.
He has brought out the old chestnuts:
First Problem: User Interface Issues
- The back, stop, and refresh buttons don’t always work.
- Since Ajax applications generate pages dynamically, there generally aren’t static links available for bookmarking or sharing with others.
- Pages don’t always print well.
- Applications don’t run offline.
- Clicks and actions generally don’t get included into a browser’s history table.
We need to be aware of issues like this, but we have fixes for many of these already, and more are coming.
Sure, sure. Is that such a huge issue these days? And IE 7 will have native support for XHR at least.
Third Problem: perceived application performance
It is easy to make something slow, or seem slow. However, you only need to play with Yahoo! Mail beta to see how a fully functional app runs like a charm. So, we can do it, and it will only get better for us!
There are definitely issues, and there are MANY things that we all wish we had. But, none of these should scare us.
It is interesting to read Desktop Ajax as Desktop.com Returned where Paul says:
What I really want from Ajax apps is for them to do stuff that it’s too hard to do with binary apps. I want them to be sensibly integrated with online resources; I want them to support realtime collaboration. I want them to do different stuff from Word/Excel/Powerpoint, not just do the same thing with a different engine under the hood.
We need to find our way with Ajax applications. Let’s not just port over to the web way, with a poorer version due to the limitations. Rather we need to embrace the differences and do as Paul says. Do things that suit the web better.
Posted by Dion Almaer at 9:28 am