I am a newbie android developer, my latest app has package name of com.myWebsite.appName, is that ok since it will be uploaded to the client google play account, or should I change it to com.clientWebsite.appName
I will create my own developer account very soon, and I want to make sure that won't cause me problems in future when I use com.myWebsite in my package in future and upload them to my own personal account
Thank you
MORE CLARIFICATION
So can I have com.myWebiste.appName1 under a developer account and com.myWebsite.appName2 under another developer account ?
Spend some time and go through this link on Android package names. The store requires each app to have a unique package name hence the need to use com.clientWebsite.appName in the event that in future you may need to publish your own app with com.myWebsite.appName as its package. We've all been there
Related
We currently use a app creator that creates the app package for us. They use an app name convention that have their domain name in the url, ex: com.theirname.ourapp
We are working on a new native app, and will stop using the app creator that we must pay monthly and also did not cover all our needs.
My question is: Do they own the "com.theirname.ourapp" package name? or could we deploy the new app using the same name? We have almost 100K installs, and will not like to star fresh with a new package name. Could they ask or force us to stop using "their" package name?
Thanks,
Luis
The package name is the smaller. The problem i can see is the key. When you create an app you need to generate de APK. APK is the package to install the app id all devices, but the updates need a new one APK signed with the same key. The package you can change and sometimees give you problems, you nd to be carefull with that, but the key always has to be the same. The key has a passwords and then you need to know too.
In the wide world of Android, no-one owns the package name, ignoring legal questions like trademark or copyright. If you are interested in these then you should consult a lawyer, not stackoverflow.
However, in the world of Google Play, the most popular app store on Android, then each package name belongs to a developer account.
If you generated the app with the App creator, and the app creator uploaded it to Google Play, then it will be associated with their developer account. You will also have other propblems, like it being signed with a signing key that they own, not you.
if you generated the APK file with the App creator, and then downloaded it. Then you uploaded it to Google Play later, then the package name is associated with your developer account. You might still have problems with the signing key, unless you signed it yourself.
Any responsible App creator should let you transfer ownership, and also be prepared to let export the signing key. If they don't this is a problem. If this turns out to be the case, you might want to contact Google Play developer support to see if they can help you. I don't know what would be done in this scenario. If this is the case then I'd also share the name of the App creator in your question as a warning to other App developers.
first time building and publishing an app.
I used PhoneGap to create an app.
I got this message when i tried to publish the app on Google play.
App violates the impersonation policy
Not sure if the problem is the package name.
My package name: com.phonegap.organisationnameappname
Should it be like this instead: com.organisationname.appname
I am using phonegap in the package name, could this be the cause of the violation.
I am using content form the organisations/company's website to create this app.
The app is for them. I am using my personal developers account to publish the app. Could this be the issue. Using my account to publish the app for them?
Concerning the package name.
Example: com.organisationname.appname
What happens if you don't have an organisation name or organisation website? Can you use any name as an organisation name?
Can you have a package name like this: com.appname with no organisation name?
Is it possible to have more than one app on the app store with the same package name?
Thanks in advance
Yes you cannot use any brand or company name in package or in name without permission.
Please read Impersonation and Intellectual Property guidelines:
https://play.google.com/about/ip-impersonation/
If your app includes any image, logo, name etc. belonging to some brand, that would be counted as policy violation. Detailed explanation is presented in Developer Policy Center linked below. Note that, there will be violation even if the brand is not on Google Play which means if you are using something e.g company logo that you are developing app for, that could be the counted as policy violation by Google Play.
https://play.google.com/about/ip-impersonation/
I am creating an application which need google play game sign in. I created app in developer console and application is running properly. now I have to change the package name of the game but I can't delete since I already publish that game.
How to handle this situation. Help me.
I want to add my application as a new game and delete the old game since I don't need THE old one I am new to android and google developer console is very confusing. please Help
com.wordpress.applica.quizz my old application package
com.wordpress.applica.qui my new application package
but they both are same application
Based from this thread, you can't delete app from account. Just make them unpublish. However, be noted that it will be still visible in account ie main server but in playstore, it will not be available.
You can delete an app anytime before it is published.
After it has been published, it "owns" its unique packagename forever in the Google PlayStore app naming hierarchy:
com.yourdomain.yourapp
There is no "deleting" this packagename after publication. That would cause mayhem.
If you want to add your application as new game, you may upload it but just make sure the package name is different with the first app uploaded. GooglePlay will treat it as a totally different application. So you can upload it without any problem.
I have an app in Play Market with package name, for example com.mycompany.appone. And I want to publish another app with package com.mycompany.apptwo from another account. Is it allowed? Or same company should publish all apps from the same account?
It is allowed, although probably not recommended, simply because it might be confusing for users and developers.
You can use, its allowed.
But creating second account will charge same as it did for creating first account.
I was recently hired to rewrite an existing Android project. The old project was published to Google Play, but I do not have access to the source files or the certificate that was used to sign it.
I finished my project, but I'm unable to publish it as a replacement for the old version because I signed mine with a different certificate. Google Play is also complaining because I used a different package name than the original project.
Is there any way around these roadblocks?
It is a new application from GooglePlay perspective. So you can only publish it as new application
As you changed its package name....the only option you have to publish it as a new app on google play
It's a different app if it has a different package name; this is fundamental to Android. Package names are how you refer to a specific app in code and how you search for a specific app, among other things. If you want it to be the same app, keep the same package name!
If it is signed with a different certificate, it can't be installed as an upgrade. This is presumably so you can't install an app with the same package name as another app and read its private data — you have to delete the app (and its data) first (the benefit is limited, of course: you can uninstall the real app and install a lookalike malicious app and steal the user's data that way). This is a bit of a limitation in Android (it doesn't handle certificate expiry, for one) and might be fixed at some point, but I don't expect it to happen any time soon.
I've been in the same situation before — the original developer lost the signing key for one app but not the other. We changed the package name and released it as a new app.