WhoBuilt

Scaling Mobile Development with React Native

Sep 14, 2018· 32 min· 413 views·Watch on YouTube

Speaker

Aaron Greenwald of Wix explains how a team of more than 40 developers builds one React Native app from independently developed features at a conference hosted by Callstack.

Scale the development process

Greenwald clarifies that scaling means growing the development process, not handling more users or data. Wix wanted one mobile app for its roughly 90 million registered users, while reusing its web expertise and shipping features quickly.

Balance team autonomy with shared standards

Greenwald frames the approach as a balance between independent teams and central oversight. Wix organizes cross-functional product groups as “companies” and professional communities as “guilds,” which share practices and maintain quality across specialties.

Fund shared infrastructure and expertise

Wix developers contribute 20% of their time to guild work, through quarterly guild weeks and regular collaboration. That time supports shared tools, open-source projects such as Navigation and Detox, and infrastructure; a core team and short-term staff loans provide additional expertise.

Build modular features with clear boundaries

React Native helps small groups build for both iOS and Android, while publishing modules as open source from the start encourages separation from company-specific code. Each product team owns one or more mini-app modules, which the core app imports and hosts.

Connect modules through small contracts

A module registry lets teams share components, publish events, and invoke methods without depending on one another’s internal state. Modules can choose different state tools, while the core app handles sessions and a shared UI library keeps the experience consistent.

Takeaways

  • Define whether scale means more users or a larger team; the operating model differs.
  • Give product teams autonomy while centralizing the standards users experience.
  • Reserve explicit capacity for shared infrastructure and cross-team learning.
  • Use module boundaries and narrow APIs so teams can change internal state independently.
  • Adopt this model only when the coordination cost is justified by the organization’s size.

Mentioned in this talk

Search inside this talk

What was claimed 10

Show all 10 facts

Related talks