When it comes to building mobile apps, the debate between native and hybrid approaches is an enduring one. With new and evolving tools and frameworks we’re constantly experimenting with new approaches and challenging our assumptions about how to build the best mobile apps.
To frame this discussion, lets clarify what we mean by native vs hybrid.
We’ve often said that native development delivers the best user experience. This remains true. With native, you get the tightest integration with platform capabilities, the most optimised performance, and full access to the design language and conventions that users expect.
But the bigger factor in delivering a great mobile app isn’t the technology—it’s the people who build it.
Teams that specialise in crafting mobile app experiences, who deeply understand iOS and Android, will consistently deliver better outcomes. This is true regardless of whether they’re using native tools or a hybrid framework.
Take any reasonably sized sample and there’s no denying that native apps tend to deliver better user experiences than hybrid apps, but the disparity in app quality often reflects the teams that built them rather than the tools being used. Many hybrid apps struggle because:
On the other hand, teams that care deeply about mobile app experiences and understand the platforms can build great apps, even with hybrid technologies. Mobile app expertise matters more than the tech stack.
That said, technology choice is still important. If you have a strong mobile team, the right technology will amplify their impact. If you’re aiming for the very best user experience, native development remains unmatched.
A big reason cross-platform app development is popular is the single codebase myth. Playing on the reasonable assumption that building native iOS and android apps means building the same thing twice and building with React native or Flutter means building it only once. Not only is this wrong because hybrid codebases always end up with iOS and Android specific code in addition to the multiplatform code, but it’s wrong because cross-platform shared code can and should play an important role in native mobile app development too.
When sharing code between iOS and Android, the how matters. Kotlin Multiplatform stands out as a modern, elegant solution for shared code. We use it to write shared business logic that runs natively on both platforms without any intermediary layer and integrates with native UI components developed for each platform. This strikes a balance between efficiency and delivering the best app user experience, and only depends on frameworks with official support from Android and iOS, using a programming language native app developers are already expert in.
Ultimately, the best mobile apps come from teams that combine the right expertise with the right tools. When you get that combination right, you can deliver outstanding mobile experiences.
Web technologies also have their place in mobile apps. For example, HTML and other web technologies are excellent for static content, and many apps can benefit from seamlessly integrating web views where appropriate. The key is to build mobile apps that are great at leveraging cross platform and web technologies, rather than trying to force them to be something they’re not.
Choosing native vs hybrid is still a critical decision, but it shouldn’t dominate the conversation. Focus first on assembling a team that prioritises mobile app experiences and understands the platforms deeply. Then, make thoughtful technology choices that align with your goals:
Ultimately, the best mobile apps come from teams that combine the right expertise with the right tools. When you get that combination right, you can deliver outstanding mobile experiences.
We’re ready to start the conversation however best suits you - on the phone at
+353 (0)1 833 7392 or by email
