5 ms·

Agree 100%. I think this sort of thing would work better as a list of common problems that you encounter when doing iOS dev and the possible frameworks with ex

Agree 100%. I think this sort of thing would work better as a list of common problems that you encounter when doing iOS dev and the possible frameworks with example projects. Having one massive Xcode project with all of these things already integrated is just begging for abuse. Novice devs who make this their goto Xcode project template and not really understand what these frameworks do are going to hurt themselves in the long run.

gimenete 15y ago
Please, count the lines of code. This is not a "massive" project. The documentation is very simple. These frameworks won't hurt you in the long run. They are very simple.
- reidmain 15y ago
  Lines of codes are a horrible metric. Having 10+ "frameworks" that you don't understand automatically included in a boilerplate project is just bad practice. Explaining why these frameworks are useful in certain scenarios and how they work are more important in my opinion. Also including frameworks like MapKit in a boilerplate project is just wrong. Why not add every Apple framework to the build phase so that novice devs will never by accident and an #import and get a compile error because the framework wasn't added to the project?
iloire 15y ago
Hi reidmain, I'm a novice dev that is now becoming an iOS dev thanks to this project. I found it quite illustrative in facing the basic stuff when you start an iOS project... hope won't hurt me in the long run though! ;)
- reidmain 15y ago
  My recommendation to you would be to not use any of these frameworks to start. If you come to a point in your project where you think you would need one then write it yourself and use these frameworks and their alternatives as references. I have written my own version of basically all of these frameworks (except for JSONKit because JSON parsing is incredibly complex and efficiency is very important) and I am a better iOS dev now because of it. If every time I needed to do a HTTP requeste I just included ASI I would not have learned as much as I did about network connections and iOS.

gimenete 15y ago

Please, count the lines of code. This is not a "massive" project. The documentation is very simple. These frameworks won't hurt you in the long run. They are very simple.

reidmain 15y ago
Lines of codes are a horrible metric. Having 10+ "frameworks" that you don't understand automatically included in a boilerplate project is just bad practice. Explaining why these frameworks are useful in certain scenarios and how they work are more important in my opinion. Also including frameworks like MapKit in a boilerplate project is just wrong. Why not add every Apple framework to the build phase so that novice devs will never by accident and an #import and get a compile error because the framework wasn't added to the project?

iloire 15y ago

Hi reidmain, I'm a novice dev that is now becoming an iOS dev thanks to this project. I found it quite illustrative in facing the basic stuff when you start an iOS project... hope won't hurt me in the long run though! ;)

reidmain 15y ago
My recommendation to you would be to not use any of these frameworks to start. If you come to a point in your project where you think you would need one then write it yourself and use these frameworks and their alternatives as references. I have written my own version of basically all of these frameworks (except for JSONKit because JSON parsing is incredibly complex and efficiency is very important) and I am a better iOS dev now because of it. If every time I needed to do a HTTP requeste I just included ASI I would not have learned as much as I did about network connections and iOS.