"I'm aware. You can build two native apps, you know." The problem is that you now have two separate apps. Not only does at least some of the code have to writt

"I'm aware. You can build two native apps, you know." The problem is that you now have two separate apps. Not only does at least some of the code have to written twice, but every other activity from hiring developers, designing the app to releasing new versions have to be done twice. In co-ordination. Over and over again. Like a lot of technologies, hybrid is really solving people problems. If your core business relies on one product or service that you sell direct to consumers, then it's probably worth accepting the extra complexity and doing two native apps. There are plenty of scenarios where it probably isn't worth it. Hybrid actually comes with hidden costs, and can actually be harder for debugging, as well as toolchain maintenance and build engineering. The pay-off, though is having a single process. Frequently, cost savings are one benefit from that, but not the only one.