All language subtitles for 007 Ejecting To The Bare Workflow_en

In the last lecture,

we worked on a bare workflow project

which we created with Expo in it.

However, sometimes you might also work

on a managed workflow project and at some point you decide

that you wanna switch to the bare workflow

because you need more configurability,

you wanna add native code for such reasons.

And the great thing about Expo

is that you can eject from the managed workflow

to the bare workflow anytime you want.

And that's exactly what we'll do here.

Here, I have this Expense app

which we built as part of the course,

not the finished version with the https on

but the first version which had some basic screens

and where we could navigate around and so on.

Now let's say that for some reason,

we wanna switch to the bare workflow.

Doing so is super simple.

All we have to do here is open our terminal

and then in this project,

which again is a managed workflow project,

we can run expo eject.

And what this will do is it will ask us

if we really wanna continue.

If you're using Git, you can save, commit before you do that

so that you can go back

because otherwise there is no going back,

Git is your only option to go back

to the managed workflow thereafter.

But if you are sure, you can continue here

and you can then choose a name for your Android package.

This should be an identifier which has a shape like this,

basically a reverse URL.

And this should be a unique identifier

which is why you typically use

something like your company name, maybe your company domain

and then a project name at the end.

So here I will choose com.academind.rncourse

because my company is named Academind.

So this is an identifier which will later be important

once we publish apps to the app stores,

we will talk about this again

in the next course section therefore,

but here I'll confirm it.

And then we can do the same for iOS and it already suggests

that we take the Android identifier here,

so I will hit Enter to confirm this

and then it basically ejects this project

which means that it generates the Android and iOS folders

which we already know from before

and that it now does a couple of other adjustments as well.

Once it is done, we will indeed have a project

that is exactly the same as if we would've created it

with the bare workflow right from the start.

And therefore now we have a project

where we can run npm run iOS and Android

to build those apps locally on our machine

as we did it before in the previous lectures,

which we can then run on the emulators

or real devices by installing these apps on them,

so exactly as I showed it to you in the previous lectures.

And therefore here if I do that,

if I run npm run android here,

this will build this app for Android

and the first build will always take a bit longer

and then thereafter it will ship that built app

to the running emulator so that we can view it there.

And then it will still work as before

but it's now not running in the Expo Go app

but as a standalone app which is built on our machine

and we are then in that bare workflow

with all the advantages and disadvantages.

So let's wait for this Android build to finish here.

So here we go, the Android build finished

and now this app is starting up

on Android as an app installed on that device,

and it works just as before, it's the same app as before,

but now not running in Expo Go but as a standalone app

that was installed on this device.

And of course we can do the same for iOS.

Open a new terminal window, run npm run ios in there

and now again, this is built locally with help of Xcode

and then installed on the iOS simulator

so that we can then preview it there

and continue working on the app if we want to.

So here we go, the app is starting up

and now here's the app running on iOS, just like this.

So that is how we can eject from the managed workflow

to the bare workflow, and of course, if you wanna learn more

about that bare workflow, if you want to dive deeper,

the official docs are your friends.

You can learn more about the different workflows there,

about their differences and similarities.

You can find more help on which workflow to choose

and you can then also dive deeper

into the bare workflow here.

If you wanna use a third party package

provided by Expo, something like location which I showed you

but also something like the camera,

you always wanna have a look at those

API reference pages for that package

to learn which extra setup might be required.

You will basically always find little instructions like this

which lead you to extra pages with more setup instructions

that need to be followed when using the bare workflow.

So that's always something you have to do

and as you see here for this camera package for example,

sometimes you also don't just need to add

some permission settings,

but you also might need to tweak some native code

which is found in one of those Android

or iOS specific files.

So, that is the bare workflow and what you can do with that.

But sometimes of course, you don't wanna use Expo at all

and therefore in the next lectures, we will explore

how we can build react native apps without expo.