Android Large Scale Project - Is it ok to divide in to several library projects? -


I am going to develop an extensive Android project, which has thousands of classes and resources. I am planning to separate the application in the module and are planning to develop them separately as library projects. Combine them together later (the application can contain 5-6 modules, so 5-6 libraries plan to create projects and combine them)

Is this approach okay? Or Android experts, please suggest a way to maintain and develop such a big project?


Edit:

Libraries share code for many applications - & gt; Yes 100% agreed on the truth

But this project is like a combination of several projects. Like this:

The Home screen dashboard has 8 buttons which click the 8 modules on a button - & gt; It opens an activity and has its own thousands of pieces, layouts, devices, etc. which is independent of other modules

Similarly, cases of interdependent use can be easily separated from me, and 4-5 developers are going to join this project, so if I can separate several library projects, then I can easily develop the module based on the module (library projects)

So one approach is to create and build a project package structure module com.name.something.Module1

I have this package under

  com.name.something.Module1.activity com.name.something.Module1. Use com.name.something.Module1.widget com.name.something.Module1.data com.name.something.Module1.dao   

and module2

 < Code> com.name.something.Module2 com.name.something.Module2.activity com.name.something.Module2.util com.name.something.Module2.widget   

etc.

So this is the first approach, but there are thousands of classes in every module: Es and Resources, Layout xml file etc.

The other way is to separate the module as library projects. I do not know how large scale projects keep their codebase, such as Facebook, Twitter etc.

Please advise.

Libraries have been kept in shared code for many applications ... if you are completely using the same application If you are focused on, then there is no point in separating your code into 5-6 library projects.

One Common Way Android Developers Separate Their Project by Creating a Sub-Package for Different Components. For example, com.package.name.ui to go inside custom view s and adapter, utility package com.package.name.util , etc. Apart from this, you have to be smart ... starting an app from scratch that will have "thousands of classes" which are very ambitious and there is really no advice that will make your life easier. / P>

Comments

Popular posts from this blog

Python SQLAlchemy:AttributeError: Neither 'Column' object nor 'Comparator' object has an attribute 'schema' -

java - How not to audit a join table and related entities using Hibernate Envers? -

mongodb - CakePHP paginator ignoring order, but only for certain values -