Refactor package names

[luongvo]

Why

As presented via this presentation, we need to refactor package names to support the KMM Templates in a consistent way across templates.

As we're mixing between singular and plural in our codebase. I see the benefit and purpose of using plurals to explicit that the package contains multiple classes of the same type. Checking out some sample projects around, we can see this point of plural naming usage:

• https://github.com/android/nowinandroid/tree/main/feature 👉 some in plural
• https://github.com/android/nowinandroid/tree/main/app/src/main/java/com/google/samples/apps/nowinandroid 👉 singular
• https://github.com/android/sunflower/tree/main/app/src/main/java/com/google/samples/apps/sunflower 👉 some in plural
• https://github.com/android/architecture-samples/tree/main/app/src/main/java/com/example/android/architecture/blueprints/todoapp 👉 some in plural
• https://github.com/android/compose-samples/tree/main/Jetchat/app/src/main/java/com/example/compose/jetchat 👉 some in plural
• https://github.com/android/compose-samples/tree/main/JetNews/app/src/main/java/com/example/jetnews/ui 👉 some in plural

After researching, I found this best practice that could be applied to our template:

• Use the plural for packages with homogeneous contents.
• Use the singular for packages with heterogeneous contents.

https://softwareengineering.stackexchange.com/questions/75919/should-package-names-be-singular-or-plural

Who Benefits?

Developers