Build Your Swift App Using Protocols
Course
Online
Description
-
Type
Course
-
Methodology
Online
-
Start date
Different dates available
Use protocols effectively in your code and explore protocols under the hood.This course shows you how to get the most out of Protocol Oriented Programming. Taking you beyond the basics, it teaches you advanced techniques and ways-of-thinking that will improve the way you use protocols, and shows you how to solve common problems you'll face when working with protocols. You will soon be building your first app with protocols. By the end of this course you'll be a protocol programming expert.About the AuthorHamish Knight is a Computer Science undergraduate at the University of Bath in the UK with a passion for Swift. Hamish is always interested in exploring how Swift operates at a lower level, and enjoy posting answers to Swift questions on Stack Overflow. Furthermore, he has over three years of experience developing mobile apps for iOS, with four apps currently on the App Store.
Facilities
Location
Start date
Start date
About this course
Explain the implementation of common patterns using protocols
Implement some of the standard library's more advanced protocols, such as Sequence and the Collection family of protocols
Use protocols effectively in real-world applications
Explore some under-the-hood details of protocols that can help you use them efficiently in your code
Solve common problems encountered when working with protocols
Master some of the great new protocol features in Swift 4
Reviews
This centre's achievements
All courses are up to date
The average rating is higher than 3.7
More than 50 reviews in the last 12 months
This centre has featured on Emagister for 4 years
Subjects
- Architect
- Programming
- Graphics
- Composition
- Semantics
- Protocol
- Testing
- Inheritance
Course programme
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- The requirements and semantics of collection
- The added requirements and semantics of MutableCollection, BidirectionalCollection, RandomAccessCollection, and RangeReplacableCollection
- How to conform to all of these protocols
- Examples of protocols that represent key abstractions
- Using protocols with core Graphics, UI views, and CALayers
- Why we use protocols where we use them
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- The requirements and semantics of collection
- The added requirements and semantics of MutableCollection, BidirectionalCollection, RandomAccessCollection, and RangeReplacableCollection
- How to conform to all of these protocols
- Examples of protocols that represent key abstractions
- Using protocols with core Graphics, UI views, and CALayers
- Why we use protocols where we use them
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Using protocols over “pure abstract” classes
- Using composition over inheritance
- The flexibility that protocols bring to composition
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Why protocols without semantics aren’t useful for generic code
- Taking protocol semantics into consideration when defining your own protocols
- The semantics of the protocols in the standard library
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- Allowing two objects to communicate with each other
- The flexibility that protocols bring to delegation
- Considerations you need to make when performing delegation
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- How protocols can be used to perform dependency injection
- How to architect your types to allow them to be easily tested
- Mock and spy types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- What these protocols describe in terms of both requirements and semantics
- How to conform to these protocols
- The power that these protocols bring to your types
- The requirements and semantics of collection
- The added requirements and semantics of MutableCollection, BidirectionalCollection, RandomAccessCollection, and RangeReplacableCollection
- How to conform to all of these protocols
- Examples of protocols that represent key abstractions
- Using protocols with core Graphics, UI views, and CALayers
- Why we use protocols where we use...
Additional information
Build Your Swift App Using Protocols