Welcome!

Machine Learning Authors: Liz McMillan, Janakiram MSV, Roger Strukhoff, Yeshim Deniz, Pat Romanski

Related Topics: Machine Learning

Machine Learning : Article

Prescribing AJAX: Panacea, Placebo, or Poison? Peeling the AJAX Onion

Mike Padilla will be speaking at AJAXWorld Conference & Expo 2008 East, March 18-20, 2008, in New York City

When to Get Rich
When evaluating whether or not to use AJAX, we need start upstream during the early design process when the user experience is conceptually designed. For example, imagine we have four sections of related content. We can choose to simply display the four sections in a four cell table or we could use an expanding/collapsing accordion control.  While an accordion control may seem cool, is its interactivity warranted? Is there fundamental value in hiding some content while viewing other content? Perhaps screen real estate is at a premium so the space saving behavior of the accordion is warranted. But would it be more beneficial to see all panels always open so that users can view information in context of other information?
 
Such design issues should be initially addressed solely in respect to conceptual usability, independent of any specific technical considerations. Once conceptual usability issues have been considered, it is time to investigate the technical implementation implications to the user experience.
 
Let’s assume the accordion control is well prescribed from a pure conceptual design perspective – the benefits that it affords outweigh its drawbacks. If the accordion will be implemented purely with DHTML, the designer should consider potential page state and accessibility issues. If the accordion panel has to retrieve information from the server based on the user’s interactions, we’ll need to use AJAX and consider its additional drawbacks.
 
Once we head down the AJAX path, we must consider the somewhat veiled, full set of usability drawbacks related to page state, caching, accessibility, and findability that accompany it. These are not merely technical drawbacks. These are drawbacks that directly affect the user as a result of the technical implementation. Do the benefits of the conceptual design still outweigh the drawbacks of the conceptual design coupled with the drawbacks that AJAX brings? If they don’t, you’ll likely want to go with the static four cell table.
 
Conceptually, the entire Web could be rendered as one giant AJAX application. It’s obvious that that would make no sense, but when does it make sense to use AJAX? It’s all about page context. AJAX is most sensibly used when the user most benefits from a persistent context. Put another way, when the user can cause a small amount of information to change relative to a large amount of information that should remain unchanged.

More Stories By Mike Padilla

Mike Padilla is a user experience manager at Vanguard. He has led front-end development efforts for such companies as Fleet Credit Cards, Mellon Private Asset Management, The Bank of New York, Radian Guaranty, and Bessemer Trust. Macromedia has featured his usability designs. He received a B.S. in mechanical engineering, focusing on ergonomics, from Cornell University.
Padilla is an ardent advocate of high-fidelity prototyping during requirements development. In his spare time, he designed and developed Protonotes, a free AJAX web service that allows project team members to discuss system functionality, design, and requirements directly on prototypes with "sticky notes".

Comments (1)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


CloudEXPO Stories
Cloud-Native thinking and Serverless Computing are now the norm in financial services, manufacturing, telco, healthcare, transportation, energy, media, entertainment, retail and other consumer industries, as well as the public sector. The widespread success of cloud computing is driving the DevOps revolution in enterprise IT. Now as never before, development teams must communicate and collaborate in a dynamic, 24/7/365 environment. There is no time to wait for long development cycles that produce software that is obsolete at launch. DevOps may be disruptive, but it is essential. DevOpsSUMMIT at CloudEXPO expands the DevOps community, enable a wide sharing of knowledge, and educate delegates and technology providers alike.
In a recent survey, Sumo Logic surveyed 1,500 customers who employ cloud services such as Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform (GCP). According to the survey, a quarter of the respondents have already deployed Docker containers and nearly as many (23 percent) are employing the AWS Lambda serverless computing framework. It's clear: serverless is here to stay. The adoption does come with some needed changes, within both application development and operations. That means serverless is also changing the way we leverage public clouds. Truth-be-told, many enterprise IT shops were so happy to get out of the management of physical servers within a data center that many limitations of the existing public IaaS clouds were forgiven. However, now that we've lived a few years with public IaaS clouds, developers and CloudOps pros are giving a huge thumbs down to the...
Kubernetes is an open source system for automating deployment, scaling, and management of containerized applications. Kubernetes was originally built by Google, leveraging years of experience with managing container workloads, and is now a Cloud Native Compute Foundation (CNCF) project. Kubernetes has been widely adopted by the community, supported on all major public and private cloud providers, and is gaining rapid adoption in enterprises. However, Kubernetes may seem intimidating and complex to learn. This is because Kubernetes is more of a toolset than a ready solution. Hence it’s essential to know when and how to apply the appropriate Kubernetes constructs.
To enable their developers, ensure SLAs and increase IT efficiency, Enterprise IT is moving towards a unified, centralized approach for managing their hybrid infrastructure. As if the journey to the cloud - private and public - was not difficult enough, the need to support modern technologies such as Containers and Serverless applications further complicates matters. This talk covers key patterns and lessons learned from large organizations for architecting your hybrid cloud in a way that: Supports self-service, "public cloud" experience for your developers that's consistent across any infrastructure. Gives Ops peace of mind with automated management of DR, scaling, provisioning, deployments, etc.
xMatters helps enterprises prevent, manage and resolve IT incidents. xMatters industry-leading Service Availability platform prevents IT issues from becoming big business problems. Large enterprises, small workgroups, and innovative DevOps teams rely on its proactive issue resolution service to maintain operational visibility and control in today's highly-fragmented IT environment. xMatters provides toolchain integrations to hundreds of IT management, security and DevOps tools. xMatters is the primary Service Availability platform trusted by leading global companies and innovative challengers including BMC Software, Credit Suisse, Danske Bank, DXC technology, Experian, Intuit, NVIDIA, Sony Network Interactive, ViaSat and Vodafone. xMatters is headquartered in San Ramon, California and has offices worldwide.