Welcome @xl3ehindTim !
I’m not sure I’m following what you’re talking about in terms of “integrations” here.
Are you saying that your Django project is going to be callng these external services, and that you want to add the data retrieved by them to your system?
If so, my decision would be based upon the degree of interrelationships of that data with the rest of my data.
<opinion>
I’m primarily in the camp of “One app until otherwise proven necessary.”
There are two cases that would most likely cause me to look toward a multi-app environment.
-
The identification of a module that I could see using in different projects. In other words, if I knew that I was going to use the “Fitbit API Integration” in projects other than what I was currently working on, then I’d consider making it an app. (But if I didn’t have an identified need - even if I thought that I might use it elsewhere, I probably wouldn’t bother.)
-
My model and view files were getting too large to be manageable. (We don’t start thinking about reorganizing until the files get to be about 2000 lines, and don’t start considering it urgent until we get to about 2500. But those are guidelines and not hard rules.)
In pretty much all other cases, we would create this all as one app.
</opinion>