Created
June 23, 2013 15:54
-
-
Save iggym/5845490 to your computer and use it in GitHub Desktop.
Useful iOS Project structure
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Useful iOS Project structure | |
A simple folder structure: | |
AppDelegate | |
Controllers | |
Models | |
Helpers | |
Folder Structure for a complex app | |
A couple of months ago, after finishing the Podio iPad app, I took a stab at improving the structure of the Xcode project. This is the what I came up with: | |
/<ProjectName> | |
/Shared | |
/Application # App delegate and related files | |
/Controllers # Base view controllers | |
/Models # Models, Core Data schema etc | |
/Views # Shared views | |
/Library # Anything that falls outside of the MVC pattern | |
/Support # Categories and helpers | |
/iPhone | |
... # Same structure as 'Shared' but with interface specific classes | |
/iPad | |
... | |
/Other sources # Prefix headers, main.m | |
/Supporting files # Info.plist | |
/Resources # Images, videos, .strings files | |
/Vendor # 3rd party dependencies not managed by CocoaPods | |
The structure on disk is the same, with some additional directories: | |
Scripts: All project-related scripts, typically executed as rake tasks using a Rakefile in the project root directory. | |
Translations: Holds all the base strings and localized gettext files used by our translation tool. | |
Pods: Folder containing all dependency CocoaPods. Auto-generated when running pod install. | |
via http://www.sebastianrehnby.com/blog/2013/01/15/structuring-an-ios-project/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment