/explore
|
You are here 
|
swiftwithmajid.com | ||
| | | | |
noahgilmore.com
It's been a year since SwiftUI was released, and many iOS developers who are lucky to only support the two most current iOS versions will soon be able to start writing SwiftUI in their production apps. There are clear benefits to using SwiftUI (I could probably devote a whole post to them), so the question I've been thinking about is: where to start? |
|
| | | | | ||
| | | | |
osinski.dev
[AI summary] The author details a custom implementation of snapshot testing for self-sizing iOS table view cells to ensure UI consistency and generate documentation screenshots. |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
apontious.com
I had to handle a fun little challenge with Codable and unorthodox JSON recently (as you do). Apple's Codable API have been around for a while, and it's an example of the best kind of API: it makes the easy things easy, and the hard things possible. [ { "type": "Great White Shark", "movie": "Jaws",... |
|
| | | |||
