Django Apps Explained

In Django, a 'project' is the whole website configuration, while an 'app' is a self-contained Python package that implements one specific piece of functionality, such as a blog, a polls system, or a payments module. python manage.py startapp blog generates a directory with models.py, views.py, admin.py, apps.py, and a migrations/ folder, and the same app can, in principle, be dropped into a different Django project and reused, because it doesn't hardcode project-wide configuration itself.

Creating an app with startapp is not enough for Django to use it — the app must also be added to the INSTALLED_APPS list in settings.py, usually by referencing its AppConfig class from apps.py, such as 'blog.apps.BlogConfig'. Only once an app is registered does Django's migration system detect its models, does the template loader look inside its templates/ folder, and does the admin site discover any models registered via admin.py — an easy mistake for beginners is writing a model but forgetting this registration step, resulting in makemigrations silently finding no changes.

A useful rule of thumb is that a project can contain many apps, and each app should be focused enough that its name describes one clear responsibility — accounts for user profiles, blog for posts and comments, payments for billing — rather than one giant app holding every model in the system. This separation keeps models.py files small and focused, lets different apps be tested in isolation, and makes it realistic to eventually extract an app like payments into its own installable package if it needs to be shared across multiple projects.