I've read that an "app" in Django is a piece of reusable functionality.
As this is not crystal clear in my mind maybe Django pro dev may judge my real life example and put me on the right track if necessary before I start coding.
My goal is to create a really lightweight financial dashboard for our studio.
I am using Django Boilerplate as project starter.
So my root looks like :
apps/
config/
db/
libs/
public/
static/
templates/
.gitignore
.manage.py
In "apps/" I have the following tree (each one is an app)
apps/invoice (manage all invoices)
apps/estimate (manage all estimates)
apps/customer (manage all customers for both invoice and estimates)
apps/idstore (manage a central repository of unique custom ID for each estimate and invoice)
apps/main (manage all global business logic such as routing etc..)
Am i doing it right ? Wrong ? Am I over-complexifying the stuff ? Will I face major trouble during development lifecycle with this organisation ?
Thanks for your thoughts on this.