single project or many projects for many apps

[MMLLEVVY]

Hi Firebasers,

I need an advice in terms of how to structure my project. I have a platform, that is used by many customers and each customer has at least one mobile app (android, ios and pwa). Right now, all customers uses single firebase project, so project's functions, firestore database, storage etc are shared by all customers. Because I want to implement cloud messaging (and I need to register each app within firebase), I'm wondering whether I should add customers' apps within main/shared firebase project or it would be better to create separate firebase project for each customer and add apps in customer's project. For now I have 10 apps, but hopefully it will be much more (100, 200 or... 1000 :-)). What is your advice?

[Samuel Stern]

Hi there,

If you're going to have hundreds or thousands of apps you almost certainly want them to be in separate Firebase projects.  Generally a project represents a single "application" across multiple platforms where a user would reasonably expect shared data, authentication, etc.

- Sam

On Thu, Dec 21, 2017 at 3:34 PM MMLLEVVY <ma...@lewczuk.com> wrote:

Hi Firebasers,

I need an advice in terms of how to structure my project. I have a platform, that is used by many customers and each customer has at least one mobile app (android, ios and pwa). Right now, all customers uses single firebase project, so project's functions, firestore database, storage etc are shared by all customers. Because I want to implement cloud messaging (and I need to register each app within firebase), I'm wondering whether I should add customers' apps within main/shared firebase project or it would be better to create separate firebase project for each customer and add apps in customer's project. For now I have 10 apps, but hopefully it will be much more (100, 200 or... 1000 :-)). What is your advice?

--
You received this message because you are subscribed to the Google Groups "Firebase Google Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebase-tal...@googlegroups.com.
To post to this group, send email to fireba...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/firebase-talk/791231e7-29ad-4d51-b285-1e079a32d255%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Nick Okunew]

It’s not entirely clear what you’re trying to achieve.
If you’re talking about a whitelabelled platform (ie same codebase) for operational purposes you probably want one project. You may need to spin up a project per customer (or group) for FCM - but you probably don’t wanna be deploying sites/functions across 100s or 1000s of projects.

If the data structures/code base is independent you may want to pursue multiple projects.

I would primarily consider the release process and operational support (ie bug fixes, alerts and revising logs) when making this decision.

[MMLLEVVY]

Nick, this is exactly what I did - there is one main project, which contains datastore, storage and functions, that are accessed by all customers. My question was primarily related to FCM, cause in order to use it I had to register each app within firebase project. I will have a project per customer, but only to use FCM and analytics within customers' apps.

Thanks.