Repo-structure design towards using Expo + Expokit staged development

Curious about what techniques projects have found that work well to achieve a sequenced/staged development where one stage of the development uses Expo (and the beautiful range of rapid dev + convenience tools) which is later merged into an Expokit stage that handles all the ejected-only required facets, such as native social auth and everything expo-firebase-app related.

I’m currently using patterns such as

// appOwnership destructured from Expo.Constants
const isProd = appOwnership === 'standalone';

to determine whether to use Expo-based methods (ie: AuthSession) or Expokit ejected methods.

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.