Reputation: 25673
Should I publish the Android and iOS versions of my app under the same package name, or is there some benefit in using different package names?
i.e. should I use com.mycompany.myapp
for the Android and iOS versions of my app, or should I separate them as com.mycompany.myapp.ios
and com.mycompany.myapp.android
?
I can't think of any technical reason right now to use separate packages, but as this would be horrendous to change later I'm tempted to use different packages.
Upvotes: 18
Views: 6913
Reputation: 34255
There is no technical requirements to use same bundle/package name. A good practice is stick to iOS/Android recommendations
Upvotes: 1
Reputation: 22592
I agree with the other answers that it's entirely your own choice, but I will also go against the other answers and state that, personally, I feel it's unnecessary to use specific ios and android packages/namespaces.
Both platforms have their own ideologies and structures and I generally play to them when it comes to naming classes and packages/namespaces.
Take these examples:
Android:
iOS
It's simple, neat and easy to follow. Obviously there are crossovers and there can always be a bit of confusion ... but the languages and IDEs themselves are different enough to keep your head in the game.
So, as stated; personal choice.
Upvotes: 11
Reputation: 8641
Agreed. In Android itself, you should use the same package name for the app and for its classes (wherever possible), but don't use the same package across iOS and Android. It's not a technical limitation, it's just that it will help you avoid dumb mistakes.
Upvotes: 1
Reputation: 19539
It's arbitrary. But personally I would use different packages:
com.mycompany.android.myapp
com.mycompany.ios.myapp
Upvotes: 5