It's dangerous to go alone! Take this important bit of orientation info:
So you've decided to make iOS apps. Congratulations!
AKA system requirements, assets, and beyond!
With Swift, playgrounds aren't just for kids.
What's a var? What sorts of vars do we see in Swift?
Bring some stability to your life with Lets.
Failure to learn about optionals is not an option.
More ado about nil.
Take loops for a whirl and form some functions.
Create your own virtual Alfie with classes.
Because doors are now deprecated.
I need somebody! Not just anybody! Here's a few great resources.
We've got to prepare for the journey ahead — don't forget your towel!
Let's start a shiny new Xcode project!
Let's get rid of some of Apple's unnecessary default code. Gross.
I launch! I die! I launch again! Learn about the various states of an application.
The app receives a window and a new view. It's probably time it got some sunlight.
Those things were getting out of hand. Such problems are best solved with a view controller.
It's such a pain to keep it inside the lines. Interface Builder makes it easier.
The compass points UICompassNavigationManager.Directions.North! A Navigation Controller will bring everything in line.
Time to put the "Add" in "Add an Add Button."
The stars of this lesson are Ed, Edd, n Edit Button. However, only one will be added to the project.
Resolving layout issues by exercising constraints.
Prepare to experience a magical moment: where the visuals meet the variables.
Or: How I Learned to Stop Worrying and Love the Table View.
Because Table View can't do anything on its own! In this step, it receives some required construction handicaps.
Don't worry, it's only a placeholder to see how the items array object works. But it probably isn't any worse than a real to do list.
Moderately successful sequel to the Electric Slide, in which the Add Item window is actually presented on command!
And for our next trick... the window is dismissed!
It's always important to be open to feedback. That's why we build a Text Field.
Today on CSi:OS we look for clues. Or maybe just make a quick fix to the layout properties.
That thing is just waiting to pounce. The safe idea is to let it open immediately, so that's what happens here.
Please. Nobody needs to see that. Let's hide the keyboard after it's been used.
This one makes sure that new items will actually be added. No prank protocols, please.
It's alive! But more importantly, it can now receive new items.
As if coding in Swift wasn't already a sensual experience.
It's time somebody edited tehse typos. In the meantime, let the Edit button enable the Editing state.
Deletion is now complete by modifying the data source, which, of course, means that [REMOVED]
It's a Cache-22! But first, it's important to set up the save and load functions.
iOS development mainly consists of defining load and save protocols and running from Tom Hanks.
Don't spend it all in one place. Also, there's no money, just protocol implementations.
Sometimes the user can be a real cachehole. Which is great for setting up a new protocol implementation class.
A functional iOS app is born!
Are you the Gatekeeper? Because I'm the KeyedArchiverCache. This class demonstrates another way of saving user data.
A functional iOS app is born... again!
The app succeeds!
Already have an account?