Entry 4: How to choose iOS libraries

header5

Four posts in, almost 20 hours spent on the project and all I did so far was to pull a bunch of pre-made components and stitch them together. It might seem like it was a puzzle that didn't involve that much coding. That's not really the case. My research involves a bit more than looking at some screenshot and deciding if I like it or not. While I'm picking iOS libraries for my projects, I need to make sure that I'm able to follow the code and understand what's going on. Sooner or later I will have to modify it. I don't want to dive into something that's poorly documented or uses lots of deprecated code that will make my app obsolete in a year or two. Each time I pick a module I think might work, I try it with my code. After all I already have a working project with my own setup, so the new code has to fit.

A good example of one of the things I check is how the interface of that module has been designed. I'm trying use the Interface Builder and autolayout as much as I can so each module I import has to work with it too, or it has to be so good that I don't care.

Stitching everything together to the point where I see that every element works was a part of my initial setup and over the next few days I will be working on some logic that's happening behind the scene.

I like starting the process of building the app with building out the interface. I can visualize everything and already have a few candidates for functionalities that might be unlocked by in-app purchases.

What I did: The user interface is clunky but everything is in place and working.

Time spend: 3 hours.

Total time spend on the project: 19 hours.