4 ms·
I’m about to finish my first web application—created to show off as a portfolio piece—and it ended up being an SPA. Granted, it’s not very complex, but I’m thin
by DATACOMMANDER 8y ago
I’m about to finish my first web application—created to show off as a portfolio piece—and it ended up being an SPA. Granted, it’s not very complex, but I’m thinking about adding additional functionality to it, and if I do I’m pretty sure I’ll stick with the SPA architecture. I like the responsiveness and sense of intimacy, but more than that, I like having all of the functionality easily accessible to the user at all times. The one thing I find most annoying about using web applications is the sense of uncertainty that lurks behind every click of a link/button. I find myself wondering:
- Am I going to be taken to a new page with a different interface?
- Will I have to open multiple tabs and/or navigate back and forth?
- Is this going to take several seconds to load?
It’s not the end of the world, but I find it annoying.
- tucaz 8y agoAll of the points you mentioned to be true for web pages can also be true for an SPA. Can't they?
- DATACOMMANDER 8y agoThey can, but it seems easier to avoid those pitfalls if you go with SPA.
- romanovcode 8y agoIn classic websites you also have layouts and controller-views so I don't see how it's different from SPA in this regard.
- DATACOMMANDER 8y agoGiven the down votes and critical replies I’ve received, it would appear that my understanding of the trade-offs between single page applications and traditional web applications is sorely lacking. I will do some research on the issue; if anyone has any particular resources they’d like to recommend, I’ll check them out.