Migration from `com.passwordmanager` to `com.jeeldobariya.passcodes`

[JeelDobariya38]

Discussed in #12

Overview

As decided In Migration Discussion, We are going to migrate to com.jeeldobariya.passcodes package name. because, com.passwordmanager is pretty general name.. and there could be potential problems.. (already discussed in discussion #12).

We are also from hereby, shift to KOTLIN + XML. (and may be in later stage of development to Kotlin + Jetpack Compose)

Migration Steps

• Migrate package from com.passwordmanager to com.jeeldobariya.passcodes.
• Migrate code from java to kotlin.
• Migrate to room library.
• Add test for room database using kotlin + android.
• Update the docs & other repository to have kotlin and up-to-date information.
• Handle previous releases & stuff.
• Change project name to PassCodes

Passcodes Name Credit

Name passcodes come from the parent project. Which is not on github. But I have created this project previously.

There are three parent project to this project. which are failed due to design issue in them... and i guess because i didn't get proper guidance. like i did with this project. (all thanks to @kudanilll)

• PassCodes (not on github)
• PassCodes-Java (https://github.com/JeelDobariya38/passcodes-java)
• Smart Manager (https://github.com/JeelDobariya38/Smart-Manager)

[kudanilll]

the best solution is to withdraw the release and then change the package name. i prefer the package name com.jeeldobariya.passcodes

Why?

• jeeldobariya is taken from your name as the owner/founder of this application
• passcodes i suggest changing the app name to something non-generic and keeping it simple (just one word), and i think passcodes is a suitable name.

imagine if we used Password Manager as the app name; there are many apps with the same name, differing only in the package name.

if we take examples of popular password manager apps, perhaps Bit Warden, Nord Pass etc., come to mind. they do not use the universal name Password Manager.

[JeelDobariya38]

Important

all the other pr will be put to sleep. meaning, will not be allowed to merge in main, until this migration takes place.. to avoid conflicts

[JeelDobariya38]

the best solution is to withdraw the release and then change the package name. i prefer the package name com.jeeldobariya.passcodes

Handle the migration by yanking the release that way release will still be documented but not used...

[JeelDobariya38]

We are migrate to Room Database because SQLiteDatabase is hard to implement.