zlacker

>>gnitin+(OP)
I still, will never understand the need for native "Apps". To this day, I have never seen an "App" that couldn't simply have been a website/webapp. Most of them would likely be improved by being a webapp.

The only benefits I can see of "Apps", are the developer get's access to private information they really don't need.

Yeah, they get to be on the "App Store". But the "App Store" is a totally unnecessary concept introduced by Apple/Google so they could scrape a huge percentage in sales.

Web browsers have good (not perfect) sandboxing, costs no fees to "submit" and are accessible to everyone on every phone.

>>turble+KJ
How would you make a video app in a browser? ie taking videos and then editing them afterwards

>>baxtr+WM
The commenter says about most apps. The use case you mentioned requires computing resources. You can do the whole thing on browser too but it is not efficient way . But in the case of delivery apps, finance apps, you don't need much compute as can work exclusively with APIs .

>>scbzzz+uO
Performance is likely not a reason anymore - and if it is, then it is the platform that imposes it (rust was runs fairly fast in a browser).