Reputation: 3111
This is my first attempt at publishing an Android app, and I'm hoping I haven't totally &*$#'d the pooch. I've designed an app that is intended to run as one app. However, the purchaser can buy different pieces of data (from a SQLite database) depending on their interests. Specifically, a knitter can buy information on different sets of stitches depending on their ability level. However, no matter what pieces of data they buy, the app, as I said, is intended to run as one app because a knitter may want to purchase more than one set of stitches. I've got my beta-testers lined up, and now I discover that I can't publish multiple apps with the same package name. Does package name = apk name? I don't want to publish apps with different apk names, because then they'll run as different apps. I've seen on Android's site something called In-App Billing, but it requires me to write additional code, and as I said, I've got my beta-testers lined up, so I don't want to delay this any further. Is In-App the only way to go with this? I saw something on stackoverflow about setting up a library with multiple packages. Would that solve my problem? I also found an answer that references the Advanced Mode in the Developer Console. Is this the solution to my problem? Any clarification would be more than welcome!
Upvotes: 0
Views: 206
Reputation: 48612
Does package name = apk name?
No, application packname is different that uniquely identify your app. There is no linking between them.
You can publish multiple APK of your single app with same package name under same app but you should go through the InAppPurchase for purchase stuff etc.
Upvotes: 1