| > It's not only EVER done, it's regularly done. Perhaps you should interrogate some of the reasons why. Content in the app is reloaded, sure, but the actual layout and business logic? Code that generally changes almost never, regenerated on every page load? I know of technologies that are basically web wrappers that allow for doing that to bypass app store review processes, but I'd be pissed if an alarm clock app decided to reload its layout from a server every time I loaded it up! The SPA model of "here is an HTML skeleton, fill in the content spaces with stuff fetched from an API" makes a ton more sense. The application model, that has been in use for even longer, of "here is an application, fetch whatever data you need from whatever sources you need" is, well, a fair bit simpler. Everyone is stuck with this web mindset for dealing with applications and I get the feeling that a lot of developers now days have never written an actual phone or desktop application. > But more to the point, if it's bad, SPAs seem to frequently manage to bring the worst of both worlds, a giant payload of application shell and THEN also screen-specific info, all for reasons like developer's unfortunately common inability to understand that both JSON and HTML are perfectly serviceable data exchange formats (let alone that the latter sometimes has advantages). I've seen plenty of MPAs that consist of multiple large giant mini-apps duct taped together. Shitty code is shitty code! |
Parentheticals added.