title: Views VS App in Django?
body: <p>Sorry for this dumb question, but i was confused:</p>
  <p>I read <a href="http://www.jeffknupp.com/blog/2013/12/18/starting-a-django-16-project-the-right-way/" rel="nofollow noreferrer">This</a></p>
  <blockquote>
  <p><strong>Intermezzo: Projects vs. Apps</strong></p>
  <p>You may be wondering why, back in Django 1.4, the startproject command was added alongside the pre-existing startapp command. The answer lies in the difference between Django &quot;projects&quot; and Django &quot;apps&quot;. Briefly, a project is an entire web site or application. An &quot;app&quot; is a small, (hopefully) self-contained Django application that can be used in any Django project. If you're building a blogging application called &quot;Super Blogger&quot;, then &quot;Super Blogger&quot; is your Django project. If &quot;Super Blogger&quot; supports reader polls, &quot;polls&quot; would be an Django app used by &quot;Super Blogger&quot;. The idea is that your polls app should reusable in any Django project requiring polls, not just within &quot;Super Blogger&quot;. A project is a collection of apps, along with project specific logic. An app can be used in multiple projects.</p>
  <p>While your natural inclination might be to include a lot of &quot;Super Blogger&quot; specific code and information within your &quot;polls&quot; app, avoiding this has a number of benefits. Based on the principle of loose coupling, writing your apps as standalone entities prevents design decisions and bugs in your project directly affecting your app. It also means that, if you wanted to, you could pass of the development of any of your apps to another developer without them needing to access or make changes to your main project.</p>
  <p>Like many things in software development, it takes a bit of effort up-front but pays huge dividends later.</p>
  </blockquote>
  <p>Then, if the website contains: Upload, Login, Registration, Add post</p>
  <p>do i then split them to projects if i follow the app philosophy (instead of using on file for each Controller/View)? isent another complication for the code?</p>
  <p>Since Django created the <code>__init__</code> files to make it easier to import the <code>class</code> then what is the main idea to complicate it with other <code>startapp</code>? in tutorials i find in the web, all of them make the <code>startapp</code> once, even the most complete applications.</p>