Using the same package name on both Google Play and Samsung Galaxy Store

Unity Engine
1

We have an existing Android app in the Google Play Store, and now we are looking at publishing it to the Samsung Galaxy Store as well. The issue we have is whether or not to use the same package name for the 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.

However, using a different package name also means that other integrations in our app that rely on the package name (such as Firebase, Facebook, Applovin, Adjust, etc) will be affected and may no longer work for the Galaxy Store version. (unless we configure a separate Firebase project, a separate Facebook app, etc… which seems impractical).

Has anyone faced a similar issue before? What did you end up doing?

2

The larger surface area of third parties you have that care about the bundle, the more fiddling you have to do.

We make custom firebase dashboards and builds for all SKUs of all of our titles, separate from Android, iOS, Samsung, Amazon, local, test, develop, release production, etc.

It’s a metric buttload of work but our company decided it was worth it. We also have multiple staff members dedicated to tracking and setting this stuff up as well as maintaining a build system capable of building all flavors of an app with a single button press.

If I were you I’d just ship the same SKU to both stores, see how it goes, adjust from there.