Say for example that I’m making a social media platform called “EveryoneTube” or something, what should and shouldn’t be an application? Should I make separate apps for the home page, trending page, subscriptions page, and user page? Or should I gather them in one single app?
This topic has been discussed a couple times here. See the full threads at:
What is the use case? Why differentiate between a project and an app?
A common explanation is to structure code within a project or to be able to ship an app as a standalone package. However, I’m still not sure what benefits the first use case provides. Finally, why would we need a Python package to be an app in order to be able to work with Django? I guess my main question is why can’t we just use regular Python modules to structure code? The only API that apps provide is the ability to dynami…
Hello, Django community! I’ve just been through the awesome “polls” tutorial series, and now I’m starting my first real project- a family tree website (that I’ve written years ago in another language, now rewriting in Django)
One thing I’m not sure about is the project structure, and how/whether I should break up the code into different apps. Reading around online, it sounds like people use separate apps that may be reusable in the future by another project. Do people also break up code into ap…
Hi
I have started to learn Django and i have a little question about apps
Let’s say my project talks about cars. Each car has a brand (and more complex stuff may arrive later)
Is it better to have a single application that manages everything about cars OR split each item in its own application (an app for cars, an app for brands, and so on…) ?
Thank you very much
After you’ve read these, if you still have questions, please let us know.
1 Like