Same repo, multiple apps proof-of-concept

Goals

Minimize separate repo tasks
Minimize need to “sync”
Visual design patterns are changed in one place, shared.

Open questions

How do we keep GPS and BTE separate enough that one will not accidentally turn on via a release?
How would i18n work?

Options

Split into packages with yarn workspaces or lerna

# existing app
gps/
  app/
    services/
      GpsService.js
    views/
      # fetch state from service, but pass to shared view
      MainContainer.js
      ExposureHistoryContainer.js
    App.js
    ...
  android/
  ios/
  .env
  .env.release

# BT app
bte/
  app/
    services/
      GaeService.js
    App.js
    ...
  android/
  ios/
  .env
  .env.release
  
# shared packages via yarn workspaces
packages/
  ux/
    Button.js
    IconButton.js
    NavWrapper.js
  # shared views, could work. We could have containers around them in app land ^
  views/
    main/
      NoExposure.js
      UnknownExposure.js
  services/
    # would there even be shared services?
    # language.js?