Scaling Mobile Development

        
export function initModules() {
  require('wix-one-app-bi').default.init();
  require('native-app-wix-login');
  require('wix-one-app-feed');
  require('wix-inbox-mobile');
  require('wix-hotels-mobile-app');
  require('wix-store-merchant-app');
  require('wix-one-app-pos');
  require('wix-one-app-module-blog');
  require('wix-one-bookings-manager');
  require('wix-visitors-mobile-app');
  require('wix-invoices-mobile');
  require('wix-contact-card-mobile');
  require('wix-mobile-media-manager');
  require('wix-one-app-more');
  require('wix-promote-app-module');
  //clubs
  require('wix-one-clubs-chat').default();
  require('wix-one-bookings-member').default();
  require('wix-one-invites').default();
  require('wix-one-clubs-manager').default();
  require('wix-one-clubs-feed').default();
  require('wix-one-activities').default();
  require('wix-one-app-notifications');
}

        
      

          
// expose
ModuleRegistry.notifyListeners('core.SessionUpdate', session);

// consume
const subscription = ModuleRegistry.addListener('core.SessionUpdate', function (session) {
  // consumer handles updated session here
});
subscription.remove();
          
        

          
// expose (react-native-navigation screen), see note below
ModuleRegistry.registerComponentAsScreen('hotels.Dashboard', () => ComponentClass, store, Provider);

// expose (regular component / view)
ModuleRegistry.registerComponent('hotels.ReservationView', () => ComponentClass);

// consume
const ComponentClass = ModuleRegisry.component('hotels.Dashboard');
          
        

          
// expose
ModuleRegistry.registerMethod('inbox.getContactDetails', () => contactService.getContactDetails);

// consume
const contactDetails = await ModuleRegistry.invoke('inbox.getContactDetails', 'johnsmith@example.com');
      
      

Scaling Mobile Development (with React Native, of course) Aaron Greenwald aaron@aarongreenwald.com | @aaronjgreenwald | github.com/aarongreenwald Icons created by Dave Gandy from www.flaticon.com and licensed under CC 3.0 BY Abstract _React Native is great for developing large applications across multiple teams, but only if you architect your app well. See the code and architecture that allows us to have disconnected teams working on separate modules but delivering a cohesive product that users feel is just one unified app. How many developers do you have working on your React Native app? One? Less than five? 15? What if you had over 40? React Native is a good fit for developing large applications across multiple teams in a company, but only if you architect your app correctly. Less than two years ago, I could count all of the developers working on our app on one hand. Now, I don’t even know everyone’s names. Learn how we architected the Wix app in a way that allows us to have multiple teams on multiple continents working on separate modules but delivering a cohesive product that users feel is just one unified app. When we first started building the Wix mobile app with React Native, the team was very small. But we knew we’d expand it very quickly, and we knew we’d need a way to allow an increasing number of developers to start adding functionality very quickly. Making it even more complicated, many of these developers would not be part of the “core team” - they’d come from other parts of the company, with their own development schedule, roadmap, and management structures. So it was important to create an architecture that would be friendly to distributed development, both in code and in process. At the same time, it was important to make sure the app would not feel like a frankestein-like mashup of disconnected modules. What we came up with is still in production today (although we’ve certainly iterated upon it). I’d like to present it to the community so that others can learn from our experience, particularly companies that are large and are considering using React Native to build apps by reusing existing web developers that are already distributed in separate departments and business functions._