Explore >> Select a destination
|
You are here 
|
codeworkshop.net | ||
| | | | |
benscheirman.com
|
|
| | | | | Almost every app you build with Xcode will need some sort of configuration. Whether it is API Keys for 3rd party SDKs, the URL of your API, feature toggles, or a logging level of verbosity, it's a good idea to keep this configuration separate from your code. | |
| | | | |
brunoscheufler.com
|
|
| | | | | When developing a software product, you'll end up with multiple environments, for your local development environment, one or many development/staging environments, and a production environment (or multiple depending on your architecture). The same applies to mobile applications.... | |
| | | | |
www.blog.montgomerie.net
|
|
| | | | | In which a semi-automated system for the versioning of iPhone applications is detailed. Said system ensures that the reader's apps are always correctly versioned, and his users' iTunes applications are never confused by an update of his beta builds. Versioning your iPhone applications properly ensures that your app updates go smoothly, and also that when you make a beta build testers never get into the frustrating state where iTunes refuses to accept it because of versioning conflicts, leaving them to have to delete the older version, and its settings and documents along with it. | |
| | | | |
www.iamsim.me
|
|
| | | In the first installment of this blog series on UIKit and The Composable Architecture we talked about how we can reduce the boiler plate required to setup a view controller powered by a Store. This post will build on that and see what it takes to implement a collection view. The first thing you need to know about rendering items from a TCA Store in a table or collection view is that we won't be referring to the items by IndexPath. | ||
