3 ms·
I propose one of the accurate terms that were already in common use, like "AJAX app" or "single-page app". But terms like these are constantly being replaced, t
by extension 15y ago
I propose one of the accurate terms that were already in common use, like "AJAX app" or "single-page app". But terms like these are constantly being replaced, to the great bewilderment of the client/lay person, in order to give the illusion of innovation. By using consistent terminology, we could avoid the translation step, along with the frequent conflicts caused by mistranslation.
- bradleyland 15y agoI also prefer the single-page-application description. I use the acronym form (SPA) once I've introduced customers to the idea. I scope projects like this: * You want a web app * The web app will be composed of components * Some components will be standard CRUD applications * Some components will be SPAs The "page refresh" is the cognitive anchor I use for clients. I tell them that standard CRUD applications are applications where the page disappears and refreshes when they click the save or submit buttons. SPAs are pages where things happen seamlessly on the page when they click buttons. I usually contrast their existing site to a site like Gmail. The thing is, I don't get in to this detail until we're past the opening conversation. During the opening conversation, my approach is to avoid correcting them at all. Rather, I ask for clarification of what they mean, then let them continue using their own terminology; abusive of our craft or not. I find that people are far better at explaining things in their own terms than they are trying to wrap them in our terms. Asking for functional examples (micro workflows) is a great way to understand what they really mean.