• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • Devaka Cooray
Saloon Keepers:
  • Ganesh Patekar
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • salvin francis
Bartenders:
  • Ron McLeod
  • Frits Walraven
  • Pete Letkeman

How should I structure my iOS app?  RSS feed

 
Ranch Hand
Posts: 31
1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What is the best way to structure an iOS app? I've seen one structured like so:

A folder for:
- View Controllers
- Views
- View Models
- UI (aka storyboards)

A couple of bonus questions:
1) Can you explain what should be put into these folders? I know that view controllers should have you view controllers (obviously), and that UI should contain your storyboards. Would views be for custom views that you create, such as a custom datepicker or something? And would View Models be the model that contains all the data for a specific object that your view presents?
2) Would View Models be necessary if you use core data? Is what core data generates your "view models"?
3) When and for what purpose should you be writing part of your code as a framework?
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!