But more importantly, I don’t think they meet the users needs nearly as often as we think they do. I’ve been in more than one client meeting where the developers try to sell benefits that clients/users don’t care about. Things like:
Developer: Look! Notice how the page didn’t reload?
Client: Uh, yea. That’s cool.
Most likely, the client only cares about the task at hand. The truth is it’s the developers that care about the tooling or of pages reload.
Jim Newery has done a superb job describing patterns that single page apps follow that lead to being dysfunctional.
So many quotes I could pull from the article. But my favorite is this.
Mistake 4: Use naïve dev practices Under-investing in front end skills has knock-on effects.
Poor development practices reinforce each other:
- Poor or no test coverage, results in…
- Highly-coupled code, that encourages…
- Over-engineered solutions, that leads to…
- Big monolithic balls of mud, that forces us to deliver…
- Giant monolithic asset bundles
Each of those is spot on and directly leads to the next. Almost all single page apps I have worked on lack tests and lead to hard to maintain code because of how interconnected it is. I’m at fault too. I never take the time to think about the front end architecture like I do the backend.
If you enjoyed reading this and would like to know when the next article is posted, please enter your name and email address below. Nothing spammy. Ever. And you can unsubscribe at any time. Thank you in advance!