⁉️Doubt: Common Package Name⁉️

[JeelDobariya38]

Overview

I have Doubt about package name related to this project.. As the com.passwordmanager could potentially be a very general package name.. I fear what will happen if other app also have a same package name... What will be the consequences?

Scenarios & Questions

• If some other app has a same package name like ours, will android create a same sandbox environment for both the app..
• What if other app is virus or something.. That steals user data..
• It also danger, even if other app is just a normal innocent app, and more probably a password manager app, I guess because of com.passwordmanager
• Will the other app be able to modify data.. And in worst case, what happen if other app also have same com.passwordmanager.SameClass will it override the our app SameClass.

Potential Solutions

One & Only Solution to this is to change our package name. But is not so simple... Because we have already publish a release

What we can do:-

• we can change the package name to something more rare & unique, com.passwords.manager or com.jeeldobariya38.passwordmanager or com.passcodes.passwordmanager.. and we can just yanked the release..
• Or we can unpublished the release and then change the package name...

What you think would be the best and how to approach it?

; Edited ;
Already decided: #12 (reply in thread)

[JeelDobariya38]

@kudanilll I am planning to change, is it worth it or.. and what should i change it to... it will not change instantly but with proper planning

[kudanilll]

We should use package names that comply with existing standards.

com.company.appname

This way, we can reduce package name conflicts.

[JeelDobariya38]

Which one can suggest one.. i can't think of one..

• com.passwords.manager
• com.jeeldobariya38.passwordmanager
• com.passcodes.passwordmanager

I have come up with three but which one.. or something else.. because we are not an organisation afterall...

[JeelDobariya38]

Suggest one!! And is it okay to have number in package names @kudanilll!!

[kudanilll]

first one!!

[hexCode63]

Package names, In my experience should be

com.DEVELOPERNAME.PROJECTNAME.

The reason for this is because:

1. when you publish on play store, all published apps by you in the future carry the same package repository and can be verified to be published by the same trusted author

2. having the developer in the package name shows the publisher is proud of their work, whereas if you had something like com.password.manager, in my experience, it looks a little untrustworthy because there is no developer attached to it

3. it is, and has been common practice to do it in this format for as long as I can remember. There is no need to alter this or try to make this part of the process look pleasing.

4. it becomes increasingly difficult to monitor and maintain apps created using this package name format (com.password.manager) as you expand and start developing more apps in the future.

My recommendation would be, as you are now wanting to create a team, to decide upon an organisation or team name and use that, then have the project name as the last input. For example; com.teamessentials.passwordmanager. if you decide to make another app, you could add that into the "team essentials" team name: com.teamessentials.keynotes. That way everyone will know it's by the same, trusted group of developers.

[JeelDobariya38]

we are currently using com.jeeldobariya.passcodes and I think it, comply with what you said.....

but if need, later on we can change to com.passcodesapp.passcodess coming from organisationid.appname from GitHub Organisation..

[JeelDobariya38]

@kudanilll

And how handle the migration mean from com.passwordmanager -> com.....

I am thinking of yanking the release rather then unpublished it.... Because that way we can still have the v0.1.0-alpha apk file.. because many may have installed it... (Let pretend that 😂)

[JeelDobariya38]

We are currently continue with com.jeeldobariya.passcodes.

Refer #17