CODEWITHSUNDEEP
androidfirebasefacebookgoogle-playgalaxy
threedollarbill
threedollarbill

Reputation: 165

Issues when using unique package name for Google Play and Samsung Galaxy store

We have an existing Android app in the Google Play Store, and we are looking at publishing the same app to the Samsung Galaxy Store. We are unsure whether it would be better to use the same package name or a different package name for the Samsung Galaxy Store.

The Samsung docs say it is "recommended" to use a unique / different package name. Doing so also prevents cross-store issues with in-app purchases.

The thing is, we are using Firebase in our app. Firebase relies on the package name, and changing it will cause Firebase to stop working. Is it possible to have 2 android apps (with different package names) use the same Firebase project? If so, will everything still work as normal for both apps (Remote Config, Messaging / Push Notifications, etc)?

We also have other integrations that rely on the package name (such as the Facebook SDK). Unless it's possible to have 2 Android package names for a Facebook app, it seems there is no easy way for us to use two different package names for the Play Store and the Galaxy Store.

Upvotes: 0

Views: 207

Answers (1)

user16930239
user16930239

Reputation: 9798

Is it possible to have 2 android apps (with different package names) use the same Firebase project? If so, will everything still work as normal for both apps (Remote Config, Messaging / Push Notifications, etc)?

YES

Is it possible to have 2 Android package names for a Facebook app

NO

My Recommendation is to use the same package name with two different versions or variants (let the user know that this is a Samsung version or Google Play and in the market description and privacy policy mention that these are different versions)

Upvotes: 0

Related Questions