Book Image

Mastering iOS 12 Programming - Third Edition

By : Donny Wals
Book Image

Mastering iOS 12 Programming - Third Edition

By: Donny Wals

Overview of this book

The iOS development environment has significantly matured, and with Apple users spending more money in the App Store, there are plenty of development opportunities for professional iOS developers. However, the journey to mastering iOS development and the new features of iOS 12 is not straightforward. This book will help you make that transition smoothly and easily. With the help of Swift 4.2, you’ll not only learn how to program for iOS 12, but also how to write efficient, readable, and maintainable Swift code that maintains industry best practices. Mastering iOS 12 Programming will help you build real-world applications and reflect the real-world development flow. You will also find a mix of thorough background information and practical examples, teaching you how to start implementing your newly gained knowledge. By the end of this book, you will have got to grips with building iOS applications that harness advanced techniques and make best use of the latest and greatest features available in iOS 12.
Table of Contents (35 chapters)
Title Page
Copyright and Credits
Dedication
Packt Upsell
Contributors
Preface
Index

Questions


  1. What does a persistent store coordinator do?

a) It talks to the SQLite database. b) It talks to the persistent store. c) It manages the data model file.

  1. What is the function of the managed object context?

a) It shows instances of managed objects on the screen. b) It mediates between managed objects and the persistent store coordinator. c) It responds to changes in the persistent store.

  1. How many managed object contexts can you use in an app?

a) Three. b) It depends on the number of CPU cores in the device. c) An unlimited amount.

  1. What is the correct way to call save() on a managed object context?

a) try! save(). b) do save(). c) try save().

  1. When should you use a fetched-results controller?

a) Any time you want to show data on the screen and react to changes. b) Only when you need to fetch data from the database and want to react to changes. c) Any time you want to fetch data.

  1. Does a fetched-results controller always go to the database to fetch data?

a) No, Core Data implements clever caching...