4 ms·

How would something like this work as a non-single-page-app: https://www.productchart.com/laptops/ https://www.productchart.com/laptops/ Would the user have t

by 3dfan 8y ago

How would something like this work as a non-single-page-app: https://www.productchart.com/laptops/ https://www.productchart.com/laptops/ Would the user have to chose "32 GB Ram", hit a submit button and wait for the page to reload with the matching laptops?

rocky1138 8y ago
I can't decide whether you're joking or not. That's how the web has worked since its inception until just a few years ago when SPAs appeared on the scene. I don't think SPAs are always a bad idea, but they sometimes are. For instance, I've gone back to HTML Gmail and I love how fast it is compared to the JavaScript mess the main product has become.
- 3dfan 8y ago
  Not joking. It was a rhetorical question. What I mean: This is an example where a single-page approach is better. I agree that there are many single-page sites that would be better if they were multipage. But I'm not sure the "almost always" is justified. The title of the article is even stronger "The Architecture No One Needs". But you and I clearly can bring up examples where it's an architecture that does make sense.
  - cpeterso 8y ago
    Why is this product chart SPA better than a simple MPA? The zoom animations do not add any value to the user experience. Also, with this SPA, you can't bookmark or a share a URL to a particular hardware search, so information and usability is lost. The URLs could be fixed, but the SPA has to explicitly manage the page history. An MFA gets that for free.
    - systematical 8y ago
      As a developer I appreciate it more, perhaps users might find it slicker. However, I go back to something another user posted "The vast majority of users don't even perceive things like page reloading, etc. Build something useful, whatever the means are." And that is the correct answer here. As the other poster stated, there are tons of applications that don't need to be an SPA. Think of damn near every admin section of a companies intranet or whatever. That thing just needs do the job, run fast enough, be easy to scale and develop on and hopefully not look like an eye sore.
LaGrange 8y ago
I was going to point out the mention of Turbolinks and other JS stuff (author isn't a fundamentalist if you read more than the headline), which would help, but in this case, to be honest, my opinion is "hopefully it wouldn't happen." It hurts my eyes.
richardwhiuk 8y ago
If it stopped the developer doing some ridiculous animation and providing me with a list of products like every ecommerce website on the net, then, sure. Also, why do you need the submit button? Just let me click on a link which filters by 32 GB and be done with it.
marcosdumay 8y ago
That's basically how every other product comparison site works. And, honestly, this is one of the worst ones I've seen.
mekoka 8y ago
In a traditional MPA yes. The user would have to choose and hit submit and wait. Regardless, I think this is a superior experience. It does require some getting use to because of the screen/price chart, but just because it's different than anything everybody has done in the past, doesn't mean it's worse. I think someone getting used to this reactive approach might find it a bit hard to go back to a more traditional click/wait cycle.

by 3dfan 8y ago

rocky1138 8y ago

I can't decide whether you're joking or not. That's how the web has worked since its inception until just a few years ago when SPAs appeared on the scene. I don't think SPAs are always a bad idea, but they sometimes are. For instance, I've gone back to HTML Gmail and I love how fast it is compared to the JavaScript mess the main product has become.

3dfan 8y ago
Not joking. It was a rhetorical question. What I mean: This is an example where a single-page approach is better. I agree that there are many single-page sites that would be better if they were multipage. But I'm not sure the "almost always" is justified. The title of the article is even stronger "The Architecture No One Needs". But you and I clearly can bring up examples where it's an architecture that does make sense.
- cpeterso 8y ago
  Why is this product chart SPA better than a simple MPA? The zoom animations do not add any value to the user experience. Also, with this SPA, you can't bookmark or a share a URL to a particular hardware search, so information and usability is lost. The URLs could be fixed, but the SPA has to explicitly manage the page history. An MFA gets that for free.
  - systematical 8y ago
    As a developer I appreciate it more, perhaps users might find it slicker. However, I go back to something another user posted "The vast majority of users don't even perceive things like page reloading, etc. Build something useful, whatever the means are." And that is the correct answer here. As the other poster stated, there are tons of applications that don't need to be an SPA. Think of damn near every admin section of a companies intranet or whatever. That thing just needs do the job, run fast enough, be easy to scale and develop on and hopefully not look like an eye sore.

LaGrange 8y ago

I was going to point out the mention of Turbolinks and other JS stuff (author isn't a fundamentalist if you read more than the headline), which would help, but in this case, to be honest, my opinion is "hopefully it wouldn't happen." It hurts my eyes.

richardwhiuk 8y ago

If it stopped the developer doing some ridiculous animation and providing me with a list of products like every ecommerce website on the net, then, sure. Also, why do you need the submit button? Just let me click on a link which filters by 32 GB and be done with it.

marcosdumay 8y ago

That's basically how every other product comparison site works. And, honestly, this is one of the worst ones I've seen.

mekoka 8y ago

In a traditional MPA yes. The user would have to choose and hit submit and wait. Regardless, I think this is a superior experience. It does require some getting use to because of the screen/price chart, but just because it's different than anything everybody has done in the past, doesn't mean it's worse. I think someone getting used to this reactive approach might find it a bit hard to go back to a more traditional click/wait cycle.