We are ready to make our very first app, so go ahead, open up Xcode, and there are two ways we can
make our first app.
One is to click create new Xcode project, or you can go to file new.
Project, when you click that, you are presented with a little Wizzit to run through.
We can have an app, a document app, a game, etc, etc, frameworks, libraries, we got Mako's at
the top, we got watch post-box, etc..
You can also click multiplatform game or swift package.
For now we're just going to use iOS and a basic app click.
Next, it will ask you for your product name.
What are we going to call this green space torch.
Let's get that right.
It will ask you for your team.
Well, that's my company name registered under Apple.
I'm not sure what this is going to look like if you don't have a developer account, but I do know that
you can still run through this.
The interface, you have two choices, Swiftie and Storyboard.
Now, Swiftie is the latest greatest thing from Apple to create user interfaces, but because it's new,
everyone still uses storyboards.
It's only the pioneers going to Swiftie.
You don't need swift UI at this point, and probably not for the next five to 10 years.
Storyboard will continue to be the dominant way to be the interface of your app.
Life-cycle, you like Kit App delegate, I'll explain what life cycles are as we go through everything,
because I don't want to fill your head with too much stuff right now and then we have language swift
or objective.
C Well obviously swift.
It's a much nicer, cleaner language than objective C and we have an option to use core data.
That's basically the database that's built in to iOS.
But we don't need it for this app.
And I would say in almost 100 percent of apps don't use Chordata.
It's really complicated.
It's better to use something like SQL Lite, but we'll get into that.
We can include tests if we want, but I'm going to check that.
Let's hit next.
It'll ask you where you want to save it.
So we have this little desktop area here.
I'm going to create that and it should save it under his own folder called Screen Torch.
I can see it's happened at the corner.
Right, and it says, no, all the information was supplied, don't care about that, just click cancel.
You can change all of that.
Now, let's get you a little bit familiar just with the interface.
Over on this side of my mouth is where we have screen torture, a bunch of folders and files, we have
a bunch of files that basically will contain all the code of our app.
What you see there is the bare template required to get an application to work on an iOS simulator or
device.
When we're editing stuff, we'll just be clicking these.
If you double click them, you're going to open up that particular item and you'll see we have code
and things there.
So that brings us to the center of the screen where you do all of your code editing.
So important UI kit, class view controller, you've done the first parts of this course or my basic
drift course is you'll know what this means already.
Right.
What else have we got?
We've got things like a main storyboard, storyboards are the graphical element of your app.
Whenever you're coding, it's a good idea to keep the storyboard separate from the code is just good
coding practice.
If you click something in the storyboard on the right, we get a whole bunch of options to change that
particular item.
So that's where we change the properties of the item in the storyboard.
I'm going to close storyboard because we're not going to use that for now, right?
Once everything is up and running and sorted and you want to actually test your app and all you have
to do is hit play in the top left corner and that's going to load the app onto whichever device you've
selected in this top menu.
So if you just click the device name, you can select literally anything you like.
If you click the first item, we start to get a little more complex, so we're not going to touch that,
we're just going to go for the device.
Now, where's the device?
Here it is.
It's loading an iPod Touch and the app is actually loaded.
I know that because I can see the code at the bottom says it's loaded, but there is nothing to display
because we have a basic white screen.
So that's your first app.
That's your familiarisation around Xcode and that's how to load the app onto a simulator.