Bricks! The end of iOS Boilerplate.
Another day, another project, nothing new for an ios developer working on a company with lots of new projects. During this year I've worked on many different projects and far more than once I've found myself repeating the same old patterns, applying the same boilerplate from project to project. With every new project, knowledge and experience increases, but I've felt that even thought this first statement holds true for almost every project, something was missing. That something, inspired me to create a pod with my friend Jonas Tomaz, who is responsable for many of the design ideas behind bricks and held with me countless architectures|design discussions over the course of several different projects and years of working together.
This pod is called Bricks, It's quite simple actually but yet powerful. After this first release already used it on other projects and the productivity boost was huge.
Nuff Said. What it does?
It contains helper methods for many of everyday tasks such as:
TableViewCells | CollectionViewCells
If you follow a convention that every cellIdentifier or xib will have the name of the Cell class, you don't have to do much, just make sure your tableViewCell extend BKBaseTableViewCell and you're good to go. No need to worry anymore with cellIdentifier, registerOnTableView, cellHeight and others boilerplate stuff. Likewise we have another version that handles CollectionViewCells.
Json -> Obj with Mantle
We're big fans of mantle so we added a helper for it too, that turns out to be very useful . Using it, prevent to expose mantle for other parts of your code that are not models.
We will keep adding features, that we judge worth it, to the bricks library over the next weeks, but even now at 0.1.0 version still very useful, simple and powerful. As always Pull requests are welcome.
During this year i've created several pods and gems to help the ios developers and myself inside the company i work for Concrete Solutions . You guys can check them here:
