Book Image

SwiftUI Essentials – iOS 14 Edition

By : Neil Smyth
Book Image

SwiftUI Essentials – iOS 14 Edition

By: Neil Smyth

Overview of this book

Do you want to create iOS apps with SwiftUI, Xcode 12, and Swift 5.3, and want to publish it on the app store? This book helps you achieve these skills with a step-by-step approach. This course first walks you through the steps necessary to set up an iOS development environment together and introduces Swift Playgrounds to learn and experiment with Swift—specifically, the Swift 5.3 programming language. After establishing key concepts of SwiftUI and project architecture, this course provides a guided tour of Xcode in SwiftUI development mode. The book also covers the creation of custom SwiftUI views and explains how these views are combined to create user interface layouts, including the use of stacks, frames, and forms. One of the more important skills you’ll learn is how to integrate SwiftUI views into existing UIKit-based projects and explain the integration of UIKit code into SwiftUI. Finally, the book explains how to package up a completed app and upload it to the app store for publication. Along the way, the topics covered in the book are put into practice through detailed tutorials, the source code for which is also available for download. By the end of this course, you will be able to build your own apps for iOS 14 using SwiftUI and publish it on the app store. The code files for the book can be found here: https://www.ebookfrenzy.com/retail/swiftui-ios14/
Table of Contents (56 chapters)
56
Index

42.8 Reviewing the Intent Handler

The Intent Handler is declared in the IntentHandler.swift file in the SiriDemoIntent folder. Load the file into the editor and note that the class declares that it supports a range of intent handling protocols for the messaging domain:

class IntentHandler: INExtension, INSendMessageIntentHandling,

  INSearchForMessagesIntentHandling, INSetMessageAttributeIntentHandling {

.

.

}

The above declaration declares the class as supporting all three of the intents available in the messaging domain. As an alternative to listing all of the protocol names individually, the above code could have achieved the same result by referencing the INMessagesDomainHandling protocol which encapsulates all three protocols.

If this template were to be re-purposed for a different domain, these protocol declarations would need to be replaced. For a payment extension, for example, the declaration might read as follows:

class IntentHandler: INExtension...