App Separation

Updated

Countly apps are the main grouping tool we have and they are used for data separation between your different projects. If you have multiple projects for different user bases, like two different mobile games, you would create two apps in your Countly server to send data to. This way you can check data of each project separately.

However not every situation is as clear cut as this. What if both of your projects share the same user base? Or what if you have mobile and web versions of the same project? Or maybe you want to separate data from the same project, what should you do?

In an example scenario where you have one web application, one iOS application, and one Android application, the questions you should ask to decide the structure on the Countly side are:

  1. Are the apps logically similar? Do they provide access to similar services (such as web banking vs. mobile banking) or belong to the same project?
    • If the answer is yes, you should continue with step 2 and 3.
    • If the answer is no, we recommend having separate apps on the Countly side for logically different applications. (You can consider Consolidation later.)
  2. Do you have a single user identifier across these 3 apps, such as an email address or account number?
    • If the answer is yes, you should have a single app on the Countly side.
    • If the answer is no, it is better to keep these three projects as separate apps on the Countly side, too, since they don’t share a common user identifier.
  3. Do you need to have different teams accessing these applications?
    • If the answer is yes, regardless of your answer to question 2, you should go with three separate applications on the Countly side since you will want to control access to these apps on a granular level.

There is always an option to duplicate your data from multiple Countly apps to a single one with Consolidation plugin, in case you want to check some general trends over your multiple separate projects.

Apart from the above questions and consideration points, we recommend having:

  • Testing

  • Production

  • QA 

versions of your applications represented as separate apps on the Countly side to avoid cluttering the production app(s).

If you are interested in how to create and manage Countly apps and also about the Consolidation plugin you can check this documentation:

Management Overview
Was this page helpful?
Reach out to us for any other questions.
Discord Community Contact Support
Helpful?

Looking for more Help?