Earlier quoted context omitted.
Native will always give the richest user experience, and deliver the most up-to-date tech. That said, most applications are really windows onto server-based algorithms, so the need for a “pure native” UX is a lot less, these days, than it used to be. The one big skunk at the hybrid picnic is that we are “dancing with a gorilla.” That means that we don’t get to change the step, or stop, until the gorilla says so. If w…
> Native will always give the richest user experience, and deliver the most up-to-date tech. Oh yeah, not arguing with that at all. But I think the commercial reality is a lot of companies will think the trade off of using a cross platform framework like Electron is worthwhile, the UX is “good enough” for most users and the development process is much more efficient. Of course, users might vote with their feet and go…
Cross-platform app frameworks have been around for decades.
One of the nice things about writing native on Apple, is plugging into the latest tech. Not always a big deal, but there are some apps that use that as their biggest selling point.
Also, if we are doing low-level stuff (like Bluetooth connectivity), the app framework can be a very stubborn gorilla.