React Native at scale

Suñol describes recurring enterprise challenges: growing teams, communication silos, security and licensing concerns, and bringing in outside expertise. He says React Native’s component structure and quick feedback can help teams work in smaller scopes and iterate without lengthy build cycles. Teams of eight to ten can give people more room to contribute than groups of 40 or more.

Suñol connects collaboration to trust, shared language, and clear code structure. React Native can give iOS, Android, and JavaScript developers common ground while letting teams split work by function. He recommends evaluating open source libraries and their licenses, and says teams can take over maintenance if a library’s original maintainer steps away.

Suñol says agility is a team’s ability to adapt and improve in small steps, rather than simply adopting Scrum or planning many sprints. He favors third parties who work alongside internal teams and share knowledge, so the organization can maintain and extend what it builds. When choosing partners, he looks at their code, communication, and whether their goals match the team’s.

For healthcare software, Suñol says teams must assess how failures could affect patients and test across devices, operating systems, and edge cases. Abbott’s apps connect glucose readings to patients’ homes, and its work also involves physical devices communicating over Bluetooth Low Energy and NFC. He says React Native can suit many patient facing apps, while highly time critical or specialized device work may call for another technology.

Suñol recommends judging a technology by its fit for the problem, the products built with it, and the strength of its community, rather than its age alone. Before a long project, he advises building a prototype, consulting developers and the community, and checking performance. React Native is a good option for many healthcare apps with user interfaces, but the use case should guide the choice.