SPA’s are wildly popular right now, with the fans of such site and application building starting to sound more like cultists than rational adults. This figures as there’s significant overlap between the cheesy framework fanboys and those making wild unfounded claims about how much “better” SPA are for user experience.

Sadly much like artists under the delusion that they are designers, those making these UX claims know just as little about user experience or accessibility.

As I’ve said many the time, front-end framework fans are devoid of the most basic knowledge of what HTML and CSS are even for; thus it’s no shock they have the same cult-like attitude when it comes to throwing “JavaScript for nothing” at websites.

Though MOST of the problems are not the concept of SPA’s fault. No, the blame lies at the implementation’s doorstep.

Implementation Woes

How an SPA is created and coded is where most of it goes wrong. Let’s go through some of the most common problems.

#javascript #css #html #single-page-applications #web-development #single page apps