iOS Development - The (not so) Weekly Fitz

Solve most of your Xcode problems through Cargo Cult

If you are an iOS or macOS developper, you probably work with Xcode. And if you work with Xcode, you've most probably had some weird times where, suddenly, things just stopped working. Here's how to solve that

SwiftUI

Add a bottom divider to your SwiftUI view!

Where we learn to look around thoroughly before blindly trusting strangers.

Swift Programming

Give your UIViews and UIButtons some rounded edges and a shadow!

Somehow, making a button rounded, and then adding a shadow to it, seems to be more difficult than it should. Here's how to do it in Swift!

Swift Programming

Memoize your API calls in Swift using functions' scopes!

Improve your iOS app's performance and battery usage by not repeating expensive computation and network calls, using memoization, in Swift!

Swift Programming

Stop hard coding your cells identifiers

Tired of having your app crash on runtime because of a misspelled a tableView's or collectionView's cell identifier? Learn here how to stop that from happening, today!

Swift Programming

Swiftly deal with pagination in Swift

Not satisfied with how you're handling pagination in your Swift iOS app? Pretty sure there has to be a better way to paginate your UICollectionView or UITableView? So did I, and here's how I did it!

iOS Development

Always handle your table & collection view cell selection properly, using functions

When writing iOS, you will always end up using UITableView or UICollectionView. With them come cells, delegates, datasources, cellForRow(at indexPath:), didSelect,... I've often seen it become (and inherited) an ugly mess. Not anymore.

iOS Development

How to debug your JSON in Xcode when JSONDecoder fails

Sometimes, JSONDecoder fails. And when that happens, it can be difficult to figure out what went wrong. Not if you can print Data instances!

iOS Development

How to elegantly make sure you only setup your ViewController's UI on viewDidLoad

When handling navigation, we often end up having to pass some sort of state to our view controllers, wether directly or indirectly. Setting endless optional publicly exposed properties feels dirty and is a pain, while setting @IBOutlets before viewDidLoad is crash prone. Let's solve that together.

iOS Development

Thrice blessed, Oh Core Data !

I was told to stay as far away as I could from Core Data. Some hate the poor thing, and others... don't really dislike him? Let's add my own story to this.