What do you think?
Rate this book
iOS Apps with REST APIs
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.
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.
214 pages, Paperback
First published September 15, 2015
2 people are currently reading
5 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 4 of 4 reviews
August 16, 2020
Short book that shows the basic workflow of designing, and implementing an iOS App that requires working with a REST API. The examples are simple and easy to understand.
March 26, 2016
This book would benefit greatly from an editor. It is confusing at times whether the author wants you to type a certain code into your program or just analyze it. Furthermore it isn't always clear which file it should be in. I managed to work through the book while constantly having to take long pauses from reading to diagnose the problems I was facing.
It is rare to encounter problems with compiling when you work with Xcode thanks to its autocomplete capabilities, but the errors I was encountering were more due to the inaccuracies in the book. There is not a nice "flow" to this book. The wording is awkward at times and the pictures don't always match the instructions.
This is not a very professional book by any means. She begins the book by linking the source code at every chapter and then entirely stops halfway through the book, resuming once again at the end. A lot of basic things are explained for some odd reason, while much more intricate concepts are glanced over. The book is really all over the place. I gave up about halfway through the book because I was tired of wasting time trying to make sense of what the book was saying.
HOWEVER, now that I've got the bad stuff out of the way, onto the good. The book introduced me to a lot of dependencies I wasn't aware of and taught me how to use them. It also gives you a nice format of how to set up your program to handle JSON in a structured manner. Otherwise, the book feels less like a tutorial and more like someone giving you code to get a program up and running. Very little is explained and it is up to you to make heads or tails of the code.
Could be an amazing book if the author hired an editor to clean it up or the author, herself, read the book from start to finish, following her own directions, which I understand is one of the last things an author wants to do after finishing a book.
It is rare to encounter problems with compiling when you work with Xcode thanks to its autocomplete capabilities, but the errors I was encountering were more due to the inaccuracies in the book. There is not a nice "flow" to this book. The wording is awkward at times and the pictures don't always match the instructions.
This is not a very professional book by any means. She begins the book by linking the source code at every chapter and then entirely stops halfway through the book, resuming once again at the end. A lot of basic things are explained for some odd reason, while much more intricate concepts are glanced over. The book is really all over the place. I gave up about halfway through the book because I was tired of wasting time trying to make sense of what the book was saying.
HOWEVER, now that I've got the bad stuff out of the way, onto the good. The book introduced me to a lot of dependencies I wasn't aware of and taught me how to use them. It also gives you a nice format of how to set up your program to handle JSON in a structured manner. Otherwise, the book feels less like a tutorial and more like someone giving you code to get a program up and running. Very little is explained and it is up to you to make heads or tails of the code.
Could be an amazing book if the author hired an editor to clean it up or the author, herself, read the book from start to finish, following her own directions, which I understand is one of the last things an author wants to do after finishing a book.
February 6, 2016
Basically just bunch of code snippets put together. Minimal explanation and hard to follow what changes in each snippet.
Read
January 20, 2019I've found this book at Pragmatic Bookshelf.
I vote it's very pragmatic.
Author gives >= 95% of practice. Many {not-so}modern iOS frameworks are described.
The main motivation for reading this book: to write a stuff described in the book for an iOS dev with no prior knowledge of {client-server, REST, UITable} can take e.g. 40 hours. It can take about 10 hours with this book.
The main new points for me:
Estimate the wins of using SwiftyJSON.
Look at Alamofire.
Use ResponseJSONObjectSerializable.
Use UITableView’s insertRowsAtIndexPaths
Use “To update one cell” instead of reloading all table.
Write simplest regexp in Swift.
Sometimes look at UIRefreshControl, UIProgressIndicator in UIAlertViewController
Mashape analogues: can REST APIs really have some difficulties?
Handle a lack of internet connection (level of caching: none, partial, all).
Estimate usefullness of XLForm/analogues ( wrapper + DSL over UITableView ).
Add persistence: NSKeyedArchiver/CoreData.
I vote it's very pragmatic.
Author gives >= 95% of practice. Many {not-so}modern iOS frameworks are described.
The main motivation for reading this book: to write a stuff described in the book for an iOS dev with no prior knowledge of {client-server, REST, UITable} can take e.g. 40 hours. It can take about 10 hours with this book.
The main new points for me:
Estimate the wins of using SwiftyJSON.
Look at Alamofire.
Use ResponseJSONObjectSerializable.
Use UITableView’s insertRowsAtIndexPaths
Use “To update one cell” instead of reloading all table.
Write simplest regexp in Swift.
Sometimes look at UIRefreshControl, UIProgressIndicator in UIAlertViewController
Mashape analogues: can REST APIs really have some difficulties?
Handle a lack of internet connection (level of caching: none, partial, all).
Estimate usefullness of XLForm/analogues ( wrapper + DSL over UITableView ).
Add persistence: NSKeyedArchiver/CoreData.
Displaying 1 - 4 of 4 reviews