Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

When I saw this, I thought "wow, this is pretty much exactly the same stuff I include every time I start a new iOS project."

I feel like it would make more sense as a project template though. It seems like if I use this to start a new project, I need to clone the repo and then change a lot of classes to get started. Or am I missing something?



Having to copy in 4-5 frameworks every time you start a project is not a bad thing.

Alternatives are always emerging to even the most used frameworks. Every time I start a project it is a time to look and see if there are better ways to do things.

Also including frameworks that you will never use is bad practice. Most apps are not going to make use of MapKit. If you're not going to use it why bother bloating your project?


i agree with you, especially on not including MapKit


From the site:

"At this moment iOS Boilerplate is just an XCode project. Is planned to be released as a true XCode template in a near future."


You are. There are much better choices out there. Check AFNetworking for example.


i had never heard of AFNetworking until today. definitely going to try it out.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: