> You're starting out with browser as your base. There are many things that come with that decision. [...] why not just learn react native instead of boasting

> You're starting out with browser as your base. There are many things that come with that decision. [...] why not just learn react native instead of boasting about how still using web browser is good enough? Because for instance I can use native HTML APIs like WebRTC without 3rd party libraries and I can reuse many great JS libs, which I'm familiar with. > Also that Bitcoin app is a bad example because it's a very simple app. It's the perfect example because it reflects that it all depends on the use case, and that are use cases that will better fit your company stack. In bitpay's case, they're heavily invested in JS/Node. So it just makes sense (like in many other cases/companies). A good lead (tech, manager, etc) will always pick the proper tool for the task, taking into account many aspects of the project: business decisions, UX, costs, current work force, current stack, available libs, etc... What I'm trying to say is that Hybrid has it's place. It's not all hybrid or all native. It depends.