Becoming a Better iOS Developer Through Tooling

@swanros Becoming a Better iOS Developer Through Tooling AltConf 2017

@swanros Oscar Swanros @Swanros Colima, México

@swanros CloudApp

@swanros Promo code at the end of the presentation

@swanros Colima

@swanros Sergio Tapiro Velasco https://www.flickr.com/photos/tapiro/

@swanros

@swanros I got some for you!

@swanros What?

@swanros tooling architecture

@swanros Tools can be modular

@swanros Swift is modular by nature

@swanros open public fileprivate private internal

@swanros class ContactView: UIView { private lazy var avatarImageView =
AvatarImageView() }

@swanros open class P3NetworkOperation: P3Operation { // MARK: - Private
Support Types private enum OperationType { case GetData case Download } }

@swanros public class BaseNetworkOperation<T: Codable>: P3NetworkOperation { override public var
headerParams: [String : String]? { var headers: [String:String] = [:] if let session = SessionManager.sharedManager.currentSession { headers["Authorization"] = "Token token=\"\(session.token)\"" } if [.put, .patch, .post].contains(method) { headers["Content-Type"] = "application/json" } return headers } }

@swanros Tools can be dependencies too

@swanros

@swanros “have you used the Facebook SDK with Swift 3?”

@swanros

@swanros every single part of your app that you don't
have _control_ of in your app, is a dependency

@swanros data services

@swanros data persistence

@swanros if it’s not essential…

@swanros Tools can prevent us from making mistakes

@swanros

@swanros public enum APIError: String, ErrorConvertible { case malformedServerResponse =
"malformed_error_response" case emailTaken = "email_taken" case unverifiedUser = "unverified_user" // ... public var errorDescription: String { return self.description } public var domain: String { return "net.Pacific3.CallicoAPIKit.Error" } } extension APIError: CustomStringConvertible { public var description: String { switch self { case .phoneNumberTaken: return "Phone number already taken." case .emailTaken: return "Email already taken.” } } }

@swanros public struct UserCollection: JSONParselable, Collection, IteratorProtocol, CustomDebugStringConvertible, ExpressibleByArrayLiteral {
} let users: UserCollection = [firstUser, secondUser]

@swanros public class GetContactsOperation: BaseOperation<UserCollection> { public override var simpleEndpoint:
EndpointConvertible { return Endpoint.contacts } public var contacts: UserCollection? public init?() { super.init() } override func generated(result: UserCollection) { contacts = result finish() } } guard let op = GetContactsOperation() else { return } P3OperationQueue().addOperation(op)

@swanros Your architecture and toolset should work for you, not
against you

@swanros don’t trip yourself up

@swanros new features requests may arrive at any time

@swanros no iOS app is feature-complete for more than 360
days

@swanros /users/:user_id/favorites

@swanros Demo

@swanros This is not an universal solution

@swanros Your toolset should be much more than just pieces
of code

@swanros Soft tools Personal/professional relationships Ability to speak to people
Asking for help is actually okay

@swanros Meta tools How are you going to know why
you did something? Document every single decision you make Time machines do exist!

@swanros Questions?

@swanros getcloudapp.com cloudlovesaltconf 50% off

@swanros GRACIAS @swanros swanros.com [email protected]

Becoming a Better iOS Developer Through Tooling

Becoming a Better iOS Developer Through Tooling

More Decks by Oscar Swanros

Other Decks in Programming

Featured

Transcript