The hard truth about Managed v. Bare

hey @kodmunki! hopefully we’ll be able to address your specific use case at some point so that you and people like you won’t need to eject. I just wanted to clarify one thing: currently when you eject, you get an “ExpoKit” project. this is a bit different than what the “bare” workflow available to you when you initialize your project. basically, ExpoKit is like including the Expo client in your app but rather than having the Expo client app where you can sign in and open your apps in development, it just points directly to your app. this has some nice benefits - everything works roughly the same as when you were in the Expo client. but it also has some downsides (discussed in the ExpoKit 2019 blogpost). bare apps, on the other hand, are just regular react-native apps with as few or as many of the expo sdk packages installed as you like.

we’re in a bit of an in-between phase where we are working on getting parity in the “bare” react-native workflow with ExpoKit so that we can switch everyone over to the bare workflow. this should make it easier for people to work with ejected apps, but of course not quite as easy as the managed workflow :slight_smile:

2 Likes