Advantages and disadvantages of an ajax based client application

Advantages and disadvantages of an ajax based client application

1. Advantages and disadvantages
of an Ajax-based client
application
Plăcintă alaru Mihai-Alin
Ș
group 1A

2. What is Ajax?
Not a programming language.
Not a new technology. (a programming
technique)
Client-side (Web browsers. i.e FireFox,
Internet Explorer, Opera, Chrome, Safari)
Ajax = (Asynchronous Javascript + XML)

3. Who uses Ajax?
Facebook. (Mostly, ajax utilized)
Google. (GoogleDoc, GoogleSuggest,
Gmail, etcs.)
Yahoo. (YMail)
Meebo. (Multi account of web messenger)
And many more modern web application
utilize ajax…

4. Ajax
Classical website.
Need to reload the whole page to return results.
Eg: search results.
Time consuming. Old fashion.
Web application using Ajax.
Only update the related section without
reloading the entire page.

5. Why use Ajax
To cut the response time.
Reduce network latency.
Asynchronous interaction.
Make web application feels like desktop
application.
Invisible data retrieval
Updating data behind the scene.
Constant updating
Notification

6. When to use Ajax?
Mostly use in:
AutoSave
Save the textbox contents without need to wait for user
prompt. (Eg: Gmail compose, blogspot topic post.)
AutoComplete
Automatically display the results match. (Eg: Facebook
search.)
Paginating
Able to search, sort and organize return data from server.
User to user communication
Can you imagine using web chat application that need to
reload ENTIRE page for each reply? Insane! (Facebook
chat, Gmail chat, YahooMail chat.)
Checking user validity, etc.

7. Advantages
comes with all modern browsers
better user interface,responds to user
interaction.
low bandwidth, even lower then regular
html/http server applications
separation of data, format, style and
function (ajax coding doesn't require this,
but makes it a whole )
lot easier to do when it is separated)

8. Disadvantages
harder/imposible to bookmark Ajax
updated page content
network latency delays impact the app's
responsiveness
search engine won't crawl AJAX
generated content
relies upon javascript, which some users
turn off.
browser compatiblity issues.

10. And...

12. Well..some browsers are smarter..

13. Ajax in Web 2.0

14. Ajax in Web 2.0

15. Ajax in Web 2.0

16. Ajax in Web 2.0

17. Ajax in Web 2.0

18. Ajax in Web 2.0

19. Ajax in Web 2.0

20. Don’t use Ajax for the sake of using Ajax
Remember careful design principles and
include ajax only where it makes sense for
your application

21. Ajax in Web 2.0

22. Ajax in Web 2.0
Failing to visually indicate ajax activity
such as busy on status bar, "working"
graphic , mouse change,etc
Solution: use graphics, status bar,etc. to
indicate "busy"

23. Ajax in Web 2.0
Leaving people behind
Offline
Mobile users
non-js enabled browsers
web accessibility (blind,hearing impaired,etc)
Solution: Provide alternative, traditional
implementation when possible to utilize ajax for
performance improvements, general ease of use
improvements, but not for core functional
aspects of a site

24. Ajax in Web 2.0
Slowness
ajax by definition means improved performance,
but poor design can counteract the benefits
to much/complex client side logic
hitting the server too often
sending too much data back and forth
Solution:
careful design
sensible use of bandwidth

25. Ajax in Web 2.0
overlooking security
sending data in clear texxt
sending form data without preprocessing
Solution:
encryption and https when needed
be mindful of security when designing

26. Sources:
http://www.slideshare.net/MolecularInc/making-web-20-usable-ajax-case-study

http://
en.wikipedia.org/wiki/Ajax_(programming)
http://www.youtube.com/watch?v
=p5CTh8aDpsI

27. Questions?

28. Thank you!