Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Be very clear about whether you are getting a 'managed' or 'bare' app #844

Open
brentvatne opened this issue Jul 31, 2020 · 5 comments
Open

Comments

@brentvatne
Copy link
Member

Describe the bug

It's currently confusing to users that most templates are managed apps but the default template is a bare app. We should be more clear about this and make it easy for a user to choose the option that works for them best.

Additional context

Some more discussion on this here: expo/expo#8563 (comment)

@mblarsen
Copy link

mblarsen commented Aug 4, 2020

So the 'blank' template is the managed version of the default template?

@brentvatne
Copy link
Member Author

npx create-react-native-app -> "Default new app" -> bare minimal template

@mblarsen
Copy link

mblarsen commented Aug 5, 2020

Thanks. What I'm trying to understand is if I want a managed app I have to select from expo and then choose 'Blank'. Is that correct?

The second part of my question is: is "Default new app" == "Blank" except that they are unmanaged and managed respectively?

@byCedric
Copy link
Member

Hi @mblarsen, I think you might be confusing two tools here. This tool installs a "bare" expo project when you pick the default template. This means it's installing a plain React Native project, just like $ npx @react-native-community/cli init (another tool), but with unimodules preinstalled. Eventually, you get a project that can use all React Native modules and Expo modules without additional config!

If you want to pick an Expo-specific template, you'd have to use $ npx expo-cli init (which is another tool). With that, you can decide if you want a "managed" expo project or a "bare" one. You can also pick one with some existing components, like the tabs/navigation one.

There are some differences between managed and bare expo projects, you can see that here. Keep in mind that whatever project type you pick, you are not locked into Expo. You can always eject from managed to bare projects, and even remove the expo modules from your bare project as well.

PS. I think this issue is more related to the examples part. Most examples are written with managed expo projects, but it doesn't have to be.

@leeeGreat
Copy link

I want to ask a question. If I change the rootviewcontroller on IOS, for example, if the rootviewcontroller is a homecontroller, will this action make OTA unable to work?

because there are many other native module like homeController MineController on tabbar,in this case, what i want to do is when i push a PannelController in HomeController,i want to trigger ota update,how can i do
PannelController:has rctrootview place the js code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants