Simplify your Swift networking with Alamofire

Announcing Our New Alamofire Pro Course!

Are you building an app that uses complex API calls, uploads or downloads files, or implements certificate pinning? Then you should consider Alamofire, a Swift networking library that makes networking tasks easy.

In our new Alamofire Pro course, learn how to make GET requests, send and receive JSON and handle errors, handle authentication to make routing type-safe and much more!

Keep reading to hear more about the course from course instructor Tim Condon:

Why should I take your Alamofire course?

"Networking in modern apps can get really complicated. URLSession has evolved to cater to a large number of use cases, but there are still times when you need a framework to handle networking.

Complex use cases like downloading and uploading files, authenticating requests, retrying requests, or certificate pinning requests require a significant amount of boilerplate code.

In my Alamofire course, you'll learn how to implement all these advanced features and how to write maintainable clean networking code. You'll also look at how to add type safety to routes to make calling routes Swifty!"

How can your course help with a common pain point in iOS development?

"A really common pain point when adding networking into iOS apps is when you need to make changes later. Maybe you have a requirement to add certificate pinning, or you move to a new authentication method with the API that requires you to add functionality to refresh expired tokens.

With Alamofire, you'll centralize your code so making changes is easy and only done in one place."

What's something that surprised you when making this course?

"How simple it was to add certificate pinning to network requests!

I've done this in the past and when using URLSession directly there is a lot of code to write so it gets complicated, really quickly.

Alamofire makes this better with only a few lines of code!"

Can you please share a cool Alamofire tip with us?

"If you certificate pin your requests to your API it can complicate development.

For instance, you might want to connect to a different API endpoint for testing, use Charles to inspect network traffic or, run the API locally.

One cool way of doing this is to alter this list of evaluators at build time depending on different flags.

All you need to do is add compiler flags to ignore different hostnames:"

Tim's Alamofire course is available for Professional subscribers now!

— Ray