Now, we have two view controllers, and we need to get from one to another.

You'll be surprised at how easy this is actually.

First, go to the playlist master view controller implementation file.

That's right here, and let's get rid of the button pressed action.

Now, we need to go back to main.storyboard.

And let's not forget to get rid of the reference to that action

by right clicking on the button and pressing the x over here to get rid of it.

And I'll explain why I did that in a second.

To connect from the master view controller, that's the first scene,

to the second scene, the playlist detail view controller.

Select the button, and then Ctrl+drag over to the Playlist Detail View Controller.

Now a little dialog should pop up, asking you to select a type of action segue.

Let's select Modal for now.

Right now, both views are just plain views with white backgrounds.

So let's change the color so that we can distinguish between them.

First, select the master view and then to select the view it's actually easier if

you bring up the document outline, and select the view from the list over here.

Now in the attributes inspector, we need to change the color and

let's set that to blue.

Any blue works here, so I'm just going to use something that I've recently used.

And we need to change the button text color as well so that we can see it.

Click on the button and then, again,

in the attributes inspector under text color, let's set it to white color.

Let's repeat the same thing for the second view, the detail view controller.

Let's select the view from the list, and

change the background color to something we've used before.

Okay, let's run this app.

And first thing, you'll notice that we don't have an issue anymore.

Now, once we hit Press Me, look at that.

The second view control is up.

What we just did was create a segue.

Spelled S-E-G-U-E, but pronounced S-E-G-W-A-Y, segue,

these objects manage transitioning from one view controller to another.

Now back in our storyboard,

each segue is represented by an arrow from the first view controller to the second.

This icon inside of the arrow represents what type of segue we're using.

When we clicked on the button, we initiated the segue,

which transitioned us to our second view controller.

Now, remember when I asked you to delete the action associated with our button?

That's because a segue overrides an action, and

having this action over here associated with our

button could have potentially caused bugs in our code, and bugs are the worst.

Okay, so when we created that segue, this one over here, we selected a modal option.

Now, we can click it and change it to Push, Pop Over, or

some of the others, and this will change the icon as well.

Now, as you can see, there are some different types of segues, so

which one do we use?

Well, each segue has a specific purpose.

Now there are two basic kinds that are available in every app that you will use.

The first is a modal segue, the one that we just added.

A modal segue presents a view modally.

Great explanation, right?

Well, a modal view provides self contained functionality in the context of

the current task or flow.

It is very similar to an alert view.

That is, it disables access to the rest of the app and

forces you to interact with the current view.

In designing and

building apps, we use a modal view when we need to offer the ability to

accomplish a self-contained task related to our apps primary functionality.

This is best understood through examples.

Let's look at some popular apps.

The Pinterest app enables you to search, find, and pin visual bookmarks.

When you download the app, before you can do any of that,

you need to either create an account by signing up, or logging in.

Both these actions are self contained actions.

You can do either one of those and then go back to using the app and

its main functionality.

Now, since this action is a one time action, we present this sign up or

log in view temporarily on top of the current view as a modal.

This is what is known as presenting a view modaly.

It is presented on top of the existing view, and when we're done with it,

it is dismissed and

we go back to the screen we were on to indicate that we completed that action.

In iOS the default modal animation is for the view to slide up

from the bottom of the screen on top of the existing view, to reinforce the idea

that this is a temporary view on top of what you are currently doing.

Let's look at another app to understand what self contained functionality means.

This next example is of the popular task management app called Things.

In such an app, creating a task is a self contained action.

It isn't part of some workflow, and when we're done creating a task,

we want to go back to where we were, that is, reviewing other tasks.

Because of this type of workflow, creating a new task presents a view modally,

with all the self contained functionality needed to create that task.

Okay, so that's a modal segue, and it's what we just used in our app.

The next main type of segue is a push segue.

Let's jump to the next video to learn more about it