3 ms·

If most of the business logic is on a server then caching doesn't help; there's too many misses. Besides, major draws for building web apps includes control of

• brundolf 5y ago
  There's nothing technical that stops you from putting business logic in the web client any more than on native (except I guess working with local files, but not many mobile apps do that these days anyway). I'm just saying, if the key benefit is not having to download the app every time you open it, and instead only downloading the actual data as needed (to save on bandwidth), PWAs can serve that usecase (if they're designed to).
  • adrianmonk 5y ago
    I think this is technically viable, but I wonder if a lot of projects fail (from a performance perspective) because teams don't realize the limitations of mobile networks early enough. So they develop everything on wifi, and it seems OK, and they make certain design choices. Then after they launch, performance is terrible when people try to use it on cell networks. By then it's too late to fix performance because they'd have to re-architect the whole thing. The lesson they could take away from it -- the one that would be most accurate -- is, "We should have designed our mobile web client differently." But the subtlety is lost and the message everyone learns is more like, "Last time, when we did a mobile web client approach, it was a disaster. Let's never do that again. From now on, it's native apps."