At this years WWDC Apple announced that Xcode 11 will contain support for using Swift packages through the Swift Package Manager. This is great news for developers of Apple platforms as it will allow us to create, publish, add, remove and manage dependencies straight from Xcode. Let us have a look at how to work with this exciting new feature.

Last week at WWDC Apple announced a lot of exciting new features and frameworks. One of my favorites was the introduction of diffable data sources for UITableView and UICollectionView. Let us dive right in and see how it can be used in combination with UICollectionView.

Unit testing is a great tool to ensure the quality and reliability of your code. A good test suite gives you confidence that your code does what it intends to do and that you will not introduce any bugs in your app when introducing a new feature or refactoring. Let us have a look at some tips and best practices to keep in mind when creating such a test suite.

The main advantage that UICollectionView has over UITableView is that you have full control over its layout. If you are used to working with UITableView you can get up to speed with UICollectionView fast as a big part of the API looks quite familiar to that of UITableView and the build in layout is great for most use cases. However the exiting part of creating custom layouts will be new and can sometimes get quite complex.

A QR code, short for Quick Response code, is a two dimensional barcode. Because it stores information in both the horizontal and vertical direction it can contain more information than a traditional barcode. It can for example store a url which deep links to a certain page in your app.