4 ms·
Browser-based apps get you a lot more flexibility and it's much easier to find developers for it. I mean ideally you'd create a native application for all oper
by Cthulhu_ 6y ago
Browser-based apps get you a lot more flexibility and it's much easier to find developers for it.
I mean ideally you'd create a native application for all operating systems and use their native frameworks, but you need to hire at least two developers (for redundancy / knowledge sharing) per platform and it'll be a constant struggle to keep features aligned. It can be done, but you need a clear vision, alignment, some independence for the native app developers, etc.
But it's pretty much unfeasible for solo developers.
- pjmlp 6y agoI wonder how do all those freelancers doing native mobile apps manage, or how we did back in the heterogeneous days of home computing.
- hombre_fatal 6y agoThey manage because they're paid to work on one platform, not a solo developer trying to launch their product on all platforms.
- pjmlp 6y agoThey are paid to work on whatever platforms the customer is hiring their guns for. And again we managed as solo developers, or with very tiny teams to do that in the context of 8 and 16 bit home micros, which meant writing lots of Assembly and hardware specific code in the process. So I guess strangely younger generations cannot manage to go to school bare foots uphill in snow both ways.
- eivarv 6y agoThere are frameworks, such as Qt and wxWidgets (desktop), that offer native or near-native widgets for all major platform. Given that most of these have bindings to many languages, I don't understand why one would involve a browser-runtime and whole other set of technologies.
- hombre_fatal 6y agoCan you give some examples of a Qt app that looks native or actually looks good? Two Qt apps that I use are Calibre and Ripcord, the two ugliest apps on my computer. Not that I'm complaining, but never lines up with HN's why-would-you-use-a-browser Qt praise.
- eivarv 6y agoWireshark, TeamViewer, Parallels Desktop for Mac, etc. For more, see [0]. The fact that it's possible to not build an "app that looks native or actually looks good" doesn't imply that it's impossible to build one that does, though. And I actually tend to prefer wxWidgets, as this wraps the platform's native widgets proper, whereas Qt reimplements many (all?) widgets, but attempts to offer a native look-and-feel. Regardless: Actual GUI-frameworks have huge advantages to using a browser, like: - Better performance - Visual and UX consistency (HCI, people!) on a shared platform - Smaller sized apps - Drastically reduced resource and energy usage [0]: https://en.wikipedia.org/wiki/Category:Software_that_uses_Qt https://en.wikipedia.org/wiki/Category:Software_that_uses_Qt