2 ms·

Sorry, I'm a bit confused about the difference between an Ajax powered page vs an SPA

• matt_s 11y ago
  AJAX and the ability to manipulate the DOM has been around for about a decade or so, AJAX came out of Microsoft I believe. Putting bits of AJAX into a web app doesn't make it SPA. Lets say you have a CRUD web application that is tax forms which end up being 5-10 "pages" printed. Then as a SPA you would have to load all the code to generate the 5-10 pages of forms, validation, logic, etc. onto a Single Page. This single page would be where everything is done, the URL would not change and the end user would have a seamless experience. If the goal is interactivity and seamless operation to the end user, attempting to mimic a desktop app, there are multiple paths to achieving that goal. Limiting the design to a single page seems sort of contrived and a "do it because I can" type of approach, absent of user requirements - in my opinion.
  • vilmosi 11y ago
    >>> This single page would be where everything is done, the URL would not change There's HTML5 history API, lazy loading... Seriously, you describe SPAs in very simplistic terms that are just not true. Do you have any experience building them? Google Maps is technically an "Ajax powered web app", but it's technically an SPA too as you never encounter a full page refresh.