Is there any best practices or conventions for ios project structure

I was wondering if there is any best practices or conventions to structure your iOS projects?

Thanks.

Upvotes: 21

Answers (5)

Randika Vishman

Reputation: 8134

I've been using a similar one to the following for my projects.

But after going through this thread and some other articles online, I decided to categorize few types under a new folder code UI.

Application (Config file with constants, AppDelegate)
Models
UI
- Views
- Controllers
- If I use Nib files (.Xib) they should come under this or else the storyboard(s)
Resources (All resources like Images, Custom fonts, Audio files with each in different subfolders)
Services
Helpers/Utilities
Libraries

But if you are using MVVM architecture, please customize this to your best fit.

Cheers!

Upvotes: 1

Alvin George

Reputation: 14292

We follow a standard project structure so as the team can understand in a better way.

Upvotes: 0

daneejela

Reputation: 14243

Although I agree that most common practice is to have files grouped by types (i.e. ViewControllers, Models etc.), I would add that there are some business cases where it is more useful to organize code by provided functionality. For example if you work for company that offers multiple combination of services, usually packed into different apps that share some of elements, for example - AddressBook, Messages, Document Management, etc...

In my projects I usually have a folder called Common where I put things that I reuse often, like datetime helpers, IO writers etc... Other things I separate by functionality.

Upvotes: 0