Make detach less scary by providing a maintainable native module layer | Voters

Make detach less scary by providing a maintainable native module layer

complete

Quincy Mitchell

There are scenarios where you want to write some native code to get at a simple feature.

If expo can make an API layer so that native code can implement an interface and a config file to point to implementations then this would provide an easy to maintain native codebase.

May 9, 2017

Evan Bacon

marked this post as

complete

In Expo SDK 41, the JS bundle in managed and bare workflow apps are the same, the only difference is where you run them (i.e. Expo Go vs. custom app). This makes switching between runtimes and customizing your app extremely easy https://blog.expo.io/expo-sdk-41-12cc5232f2ef

Sébastien Lorber

Hi, this is not totally related but you might find that if you can still use Expo client after detaching, the detaching experience would be less scary and you would more easily want to write custom native code with less fear of ejecting. See also https://expo.canny.io/feature-requests/p/ability-to-work-in-expo-client-after-detaching