Okay. You still need a client side database with syncing. Which is what this is about.
The pure native approach only solves (kind of) the limited storage issues, nothing else.
If you nuke your site and only develop about native apps then you'll lose users to competitors because people can try their service without downloading an app.
Yeah maybe we shouldn't have shoved an app run-time into a document viewer, but here we are and things run decently well (thanks to v8 and other tech) if you do things right.
I think you underestimate the number of issues a (purely) native app solves. The fact that many developers don't care about some of them it does not mean they don't exist. One of them is shorter delay, very important in interactive applications.
Syncing can be implemented in billion ways, from dedicated solutions to custom ones.
Paradoxically, I think Microsoft got it (somewhat) right with Office. You can use a native C++ app, and this is what most people use because of speed and control. However, if you like working online, don't mind saving your documents unencrypted on Microsoft's systems, don't worry about being offline, you need collaborate with others online, or just like the convenience of having your documents always online, you can use the 365 version with inferior but probably acceptable performance - in this way everybody is happy.
The pure native approach only solves (kind of) the limited storage issues, nothing else.
If you nuke your site and only develop about native apps then you'll lose users to competitors because people can try their service without downloading an app.
Yeah maybe we shouldn't have shoved an app run-time into a document viewer, but here we are and things run decently well (thanks to v8 and other tech) if you do things right.