Historically we've had two projects for iOS:
The primary intention of Console was to demonstrate how to use MatrixSDK to write a Matrix client app. However, this split isn't helpful for developers who want higher level modules that provides UIViewControllers ready to use in an existing app, with no need to manage low level communications with the Matrix homeserver.
It is where the MatrixKit project started. MatrixKit sits between MatrixSDK and your existing iOS app.
It provides customisable UIViewControllers a developer can integrate in their app. If you want to add to your app a screen to chat in a room, you just need to use the MXKRoomViewController.
We made MatrixKit so that the components it provides are easy to integrate but also easy to customise. We do not have yet full samples of customisation as we've been focused on the library core, but here are a few examples:
MatrixKit is also highly extensible. If you want to create new table cells to render messages, new views, new view controllers, etc, you will find a place to hook them into the MatrixKit code.
MatrixKit repository is here: https://github.com/matrix-org/matrix-ios-kit and it is available via CocoaPods (the MatrixKit pod).
In parallel of MatrixKit, we did some spring-cleaning - the official Matrix.org iOS offerings are now split into three github repos. One for each deliverable:
Today, we released MatrixSDK 0.4.0 (changes). Update your pods :)
Console 0.4.0 (changes) is in the Apple submission process. This will be the first version of the app using MatrixKit. Aesthetically, there is no change since the previous version. The app is more stable due to all the data abstractions and management improvements provided by MatrixKit.
If you're an iOS developer, please have a go with MatrixKit and let us know on #ios:matrix.org how you get on!