End to End iOS Development
End to End iOS Development
About the Bundle
We've all seen it. That amazing app that solved all your problems.. and turned your phone into a coffee warmer.
The developer had a great idea but is doing too much work on the device. It's downloading too much data, trying to process it locally, keeping connections open, and killing your battery cutting you off from everything and everyone.
The only solution is to move that work off the phone and back to the server via APIs. To do that well, your API has to be well planned, thoughtfully designed, and easy to use.
With this bundle, you'll be equipped to design and build API-driven Swift apps from the frontend to the backend.
In A Practical Approach to API Design, we work to help you understand who will be using your API and why, what problems you need to prepare for, and how to solve many of those problems. Nouns, verbs, routing, and versioning are all discussed to make sure you build the right thing.
In iOS Apps with REST APIs, we'll dig into the patterns and practices that you need to interact with APIs successfully including authentication processes like OAuth 2.0. We'll transition from a simple main table view into analyzing the JSON responses and turning them into models that you can use and extend.
The target audience for this bundle is developers who are adding native iOS development and APIs to their skillsets. A solid grasp of backend development is recommended.
iOS Apps with REST APIs
Building Web-Driven Apps in Swift
Skip the hundreds of pages that barely get into how to make a network call in iOS. No esoteric details about Core Anything or mathematical proofs of flatmap. Only the nitty gritty that you need to get real work done now: interfacing with your web services and displaying the results in your UI.
This book was written using Swift 3.0, Alamofire 4.0, Xcode 8.1, and iOS 10 (with support for iOS 9). Free update to Swift 4 in fall 2017.
All code samples included.
After reading this book you’ll be able to:
- Analyze a JSON response from a web service call and write Swift code to parse it into model objects.
- Display those model objects in a table view so that when the user launches the app they have a nice list to scroll through.
- Add authentication to use web service calls that require OAuth 2.0, a username/password, or a token.
- Transition from the main table view to a detail view for each object, possibly making another web service call to get more info about the object.
- Let users of your app add, modify and delete objects (as long as your web service supports it).
- Hook in to more web service calls to extend you app, like adding user profiles or letting users submit comments or attach photos to objects.
This book is for:
- Software developers getting started with iOS but experienced in other languages
- Front-end devs looking to implement native UIs for iOS apps (no CSS, oh noes!)
- Back-end devs tasked with getting the data into the user's hands on iOS
- Android, Windows Phone, Blackberry, Tizen, Symbian & Palm OS devs looking to expand their web service backed apps to iOS
- Anyone whose boss is standing over their shoulder asking why the data isn't showing up in the tableview yet
This book isn't for:
- People completely new to programming, you should have a decent grasp of at least one object-oriented programming language or have completed several intro to iOS tutorials
- Designers, managers, UX pros, ... It's a programming book. All the monospace font inserts will probably drive you crazy.
- Cross-platform developers dedicated to their tools (including HTML5 & Xamarin), this is all Swift & native UI, all the time
- Programmers building apps with no webservice interaction
- Game devs
3 reader testimonials
A Practical Approach to API Design
From Principles to Practice
If you read the tech press, everyone knows they need an API but most aren't really sure what it is. They treat it as another checkbox like "Web 2.0" was a few years ago or a mobile app was most recently. In fact, there’s an entire “API-first” movement in development circles that most people don’t understand or even realize why. In this book, we'll start by discussing the what an API is, why you might need one, and follow up with the how to build one.
This book is incomplete, lacking one last appendix. As a result, we hope this book becomes a conversation as we continue writing. When you find something interesting, let us know. If you think we’re wrong, say so. If you think we’re right, tell your friends. If you want us to teach your team more and deeper concepts, please let us know.
Towards that goal, we have one remaining chapter on our drawing board:
- API Design Patterns
- SOLID Design Principles
- Naming - Resources & Parameters
- Authorization - Tokens vs Credentials
- Link Relations
- Error Handling
- Caching - Strategies & ETags
- Hard vs Soft Deletes
The Leanpub Unconditional, No Risk, 100% Happiness Guarantee
Within 45 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
See full terms