> don't need an app in the first place You need a native app if you need native features not offered by the browser but you can still use chromium webview for

> don't need an app in the first place You need a native app if you need native features not offered by the browser but you can still use chromium webview for the UI. That's my use case at www.waiterio.com. A webview with React is fast enough for the UI but my app needs to speak with hardware using USB, TCP sockets and Bluetooth sockets. I'm fully aware of WebUSB but it doesn't work well with the hardware I use. WebUSB seems like a prototype built to work for a demo with Arduino and that's it. > But Android is slowly limiting the power of apps further and further I believe Android is adding more fine grained control of apps power permissions but I'm not sure about the reduction in power. > The whole point of apps is to interact with hardware browsers don't support I agree on this, I don't criticize apps interacting with native API/SDK. I criticize the UI systems of native apps. On paper swift/kotlin should be fast but in practice Google put so much work in optimizing Chrome and Facebook put so much work on React that Chromium+React is faster than the native UI kits.