Find online courses made by experts from around the world.
Take your courses with you and learn anywhere, anytime.
Learn and practice real-world skills and achieve your goals.
A course for developers who want to create their iOS applications using good practices, while avoiding some traditional code smells.
For first time iOS developers, this course will guide you through several parts of the the language and the API, how and why to use them properly. Avoid common iOS and developers mistakes while building a real world application. The number of applications is not the goal here: a good, well written app is what we are looking for.
In this course you will learn the basics that will allow you to understand what you are building: how and why. You don't really know something until you learn why.
If you already develop for iOS, but are tired of developing applications that are costly to mantain, tired of writing code noone else understands, or even the simplest change requires too much energy, this course will fit your needs: learn how to avoid those mistakes using features both from the language and the API.
You will learn Swift, the iOS API, good practices, design patterns and code smells. You will not just learn how to use, but understand what and why you are using it. As a newcomer, learn how to use the long press gesture, show modal alert controllers, use encapsulation, when and how to use optional chaining, if let, the DRY and SRP principles, default parameters, the extract class and method refactorings, use closures, understand the serialization process, the NSCoding type, and the DAO pattern.
Understanding what is going on is the difference between a language and API user and a professional programmer. This is our goal, let's understand Swift and iOS development.
Not for you? No problem.
30 day money back guarantee.
Learn on the go.
Desktop, iOS and Android.
Certificate of completion.
|Section 1: Gesture: long press and the observer pattern|
Detecting gestures and the UILongPressGestureRecognizerPreview
Detecting which View was long pressedPreview
Summing up: Long press and the Observer PatternPreview
|Section 2: Alerts|
Creating an UIAlertController
Summing up: alerts and caring about encapsulation
|Section 3: Optional: good or bad?|
Smelly :( or good practice :) Optionals usage
Code smell: "Optional!" is as dangerous as it gets
Bug: infinitely losing money
Code smell: "Optional?Chaining" is as dangerous as it gets
I don't wan't to be the bad guy, do you?
The optionals rule: avoid defining, use if let as much as possible
Good practice: optionals, if let and alerts messages
Summing up: avoiding optionals, showing meaningful error messages
|Section 4: Even more good practices and questioning|
Dont repeat yourself (DRY)
Good practice: refactor extract method/class
Invoking the refactored method
Code smell: if/else/elses and switch are nasty boys
Refactor: isolating nasty code
Good practice: thinking after coding, should we refactor further?
Summing up: avoiding copy and paste mess and simple refactor power
|Section 5: Functions, methods or closures?|
ActionStyles: Cancel or Destructive?
Functional programming intro: passing functions as arguments
Code smell: Using properties as global variables
Vanilla functions: it is just a function
Updating the data source and redrawing the table
Defining a closure and passing it as an argument
Receiving closures as a parameter
Summing up: Spaguetti Code, and Closures
|Section 6: Serialization: saving data to the file system|
Serializing with NSCoding and writing to the file system
Locating the file in our simulator file system
Saving the files, copy and pasting code :(
Summing up: saving to disk and serialization
|Section 7: Single Responsibility Principle and Data Access Object (DAO)|
Single Responsibility Principle (SRP) and Data Access Object (DAO)
Thinking out loud: method naming (aka items items item, meals meals meal)
As a software developer I was tired of "language tutorials" and "bad practices courses". What about you? I want my students to finish a course and become capable of judging what is good and bad for their software, both on the short and long run. They should understand what they are doing, not just make use, but own their language and tools.
I have worked as a software development educator for the past 12 years, with experience in several countries, programming languages and environments. Learning how to program should be done as we learn things in real life: with real examples and a parental guide on what is good and what is bad for us.
My mobile experience started with Java ME in the early 2000's, went through Android and I have finally reached iOS development when Swift was first announced. I was given the task to write our company's main product iOS version using Swift and that experience together with many other language and API experiences can be seen in my courses.
I have closely worked with several user groups and communities in Brazil, where I was lucky to be invited to give talks at many conferences, including QCon, AgileBrazil etc. I am also the co-organizer of a well-known brazilian mobile development conference, MobileConf.
I am the cofounder of the biggest Brazilian web site on software development questions and answers, GUJ, creator of VRaptor, a java community expert on some JSRs and cofounder of Brazilian's tech book publishing company Casa do Código.
You can find more information about my career at my linkedin page.
Finally, as a personal note, I am a language lover, feel free to find me at twitter and chat in portuguese, korean, english, french or german, or follow my korean weekly blog.