10 Pods to Use in a New iOS Project
Working with Cocoapods

This is a brief overview of the Cocoapods system. If you’re familiar with it, skip this section.

If you still don’t have Cocoapods in your system, open the Terminal app and type:

sudo gem install cocoapods

Create a new project, open the containing folder in Terminal and type:

pod init

pod install

You’ll get a workspace file. From this moment, you should only open workspace, not a project, otherwise, Xcode won’t see your dependencies and you’ll get references to a non-existent code. To add dependencies use Podfile . It’s a Ruby script, but you don’t need to know Ruby to edit it. There are several simple rules.

First of all, let Cocoapods know your target system. For example, iOS. And don’t forget to specify your minimum iOS version:

platform :ios, '10.0'

As all warnings in external libraries are not my business, I usually add this line:

inhibit_all_warnings!

It will silence all the warnings in external libraries.

If you use Swift, you probably want to use frameworks. Some pods require this:

use_frameworks!

Each target can have separate dependencies. For example:

target 'MyApp' do

pod 'Alamofire'

pod 'Kingfisher'

# ...

end

As you can see, you can add comments with the symbol # .

Any target can have an unlimited amount of libraries. Sometimes you need to specify a version or a version range. In such cases, web pages of libraries give you instructions, but the general syntax looks like this:

pod 'Kingfisher', '~> 5.4'

And that’s it! Let’s move on to the ten libraries I use the most.
['Alex Nekrasov']
['Cocoapods', 'Mobile', 'Xcode', 'Swift', 'Programming']