Book Image

Swift 2 By Example

By : Giordano Scalzo
Book Image

Swift 2 By Example

By: Giordano Scalzo

Overview of this book

Swift is no longer the unripe language it was when launched by Apple at WWDC14, now it’s a powerful and ready-for-production programming language that has empowered most new released apps. Swift is a user-friendly language with a smooth learning curve; it is safe, robust, and really flexible. Swift 2 is more powerful than ever; it introduces new ways to solve old problems, more robust error handling, and a new programming paradigm that favours composition over inheritance. Swift 2 by Example is a fast-paced, practical guide to help you learn how to develop iOS apps using Swift. Through the development of seven different iOS apps and one server app, you’ll find out how to use either the right feature of the language or the right tool to solve a given problem. We begin by introducing you to the latest features of Swift 2, further kick-starting your app development journey by building a guessing game app, followed by a memory game. It doesn’t end there, with a few more apps in store for you: a to-do list, a beautiful weather app, two games: Flappy Swift and Cube Runner, and finally an ecommerce app to top everything off. By the end of the book, you’ll be able to build well-designed apps, effectively use AutoLayout, develop videogames, and build server apps.
Table of Contents (18 chapters)
Swift 2 By Example
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Free Chapter
1
Welcome to the World of Swift
2
Building a Guess the Number App
Index

Building a skeleton app


Let's start implementing the base structure on top of which we'll implement the entire app.

Implementing an empty app

Let's start creating a new app called Todolist using the Single View Application template in Xcode. The app will be in portrait mode only, so you must uncheck Landscape from the allowed device orientations:

Although Apple has improved Interface Builder in Xcode 7, most developers still favor writing the layout in code instead of using Interface Builder. The common reasons are that with Interface Builder, it is more difficult to create reusable views, which makes working in a team difficult because of merging of the storyboard files; in general, it is more difficult to debug a complex layout.

However, Apple strongly encourages that you use Interface Builder to build User Interface and we will use it to build our first complex app. To show the difference, the app in the next chapter will be built using Auto Layout by code, helped by a third-party library...