Project structure management for larger and more complex applications

This is a little basic question / s and pertains to the structure of the project. This is just a basic concept that I missed in android. (as a result of self-learning).

In an application that has many classes, actions and fragments, it becomes busy in both the java and res folders.

I'm not sure what is the best way to continue managing large projects.

For example, if I have different sections: bluetooth, wifi, gps, etc. And for many of them, they are "packages" or "modules" for reuse (I'm not sure of the right word).

How do I start formatting my project? Using packages?
Is there an equivalent to the dll concept?

There is this question here:
Is there any DLL or DLL concept in Android? but it doesn't really help clarify this issue for me.

Any feedback is appreciated.

+3


source to share


1 answer


How do I start formatting my project?

It depends on your needs. If you want to move some of your logic into a library, you can do so by creating an Android library project. See the Library Module section : https://developer.android.com/tools/projects/index.html

Is there a dll equivalent?



If you want to have a compiled version of this library project (like a DLL), you can generate a .jar

. Referencing this link: How to create a jar for an Android library project

So, you can link the Android library project directly, or first compile it and then include it as a file .jar

.

+2


source







All Articles