Now, what did change between version four and version five with reality navigation in the past were
with these older versions, so with REACT navigation, which are free and for which we use in this course,
we had this way of setting up routes that were of setting up screens we could go to.
We set up such a registry like configuration in a file where we basically mapped our different screens
to identifiers and then we could work with these identifiers from anywhere in the application to go
to a specific screen.
Now, when it came to configuring these different screens, we could do that directly in the screen
component or also globally on the Stack Navigator, for example, with the default navigation options.
Now, this approach of navigating around works just fine, as you see in this course.
And there isn't necessarily something wrong with it, though.
We also had some occasions where we definitely saw that it could be tricky at times.
Right.
If you wanted to update Hattar buttons in the header of a component dynamically, you had to abuse Purim's
to do that.
And that was not ideal and definitely a bit tricky to wrap your head around.
Nonetheless, you can definitely use Riak navigation versions free and fair and you can keep using those
versions.
But with the release of React Navigation Version five, things changed a bit.
And we now set up Rawat's and we navigate around a bit differently.
Now there basically is one super big change between version four and five, which I'll cover in this
module.
We now don't set up our different Rawat's or our different screenname mappings in this registry like
way we see on the left.
But now instead we set everything up as a component tree, you could say.
So now we have a component based configuration of our different Rawat's.
We can go to all of our different parts of the application, go to and what looks a bit messy here on
the slide will look way cleaner later in this module when we put our project to that set up.
Now, whilst this certainly is a big change and a big mental model switch we have to make because we
set up our navigation configuration in a totally different way.
Now, it offers some nice advantages.
As you will see, it's actually closer to the react way of building apps where you basically want to
use components everywhere to express what the result should look like.
And you then let react figure out the way to get there.
And if we set up our screen configuration in such a component based way, then we actually just define
our end result and we let react and react navigation, figure out the way to get there.
So that's actually a good mental model to have.
But of course, that's one we have to get used to.
And therefore, without further ado, let's dive in and let's put our application.
However, there is one thing I want to say.
React navigation.
This package with the words three and four is still super important.
Of course, react navigation, version five and so on is the future of react navigation.
But the vast majority of project you will find out there of react native projects will use react navigation
in versions three and four.
So you have to know those versions as well, which is why the overall course still uses D versions with
this module.
I also show you version five.
So did you have the full toolkit and you were able to work on any react native project, no matter which
version of navigation it uses?