Android applications should always be neatly organized with a clear folder structure that makes your code easy to read. In addition, proper naming conventions for code and classes are important to ensure your code is clean and maintainable.
Be sure to check out the Ribot Code and Style Guidelines for a more extensive breakdown of suggested style and naming guidelines.
The following naming and casing conventions are important for your Java code:
| Type | Example | Description | Link |
|---|---|---|---|
| Variable | incomeTaxRate |
All variables should be camel case | Read More |
| Constant | DAYS_IN_WEEK |
All constants should be all uppercase | Read More |
| Method | convertToEuroDollars |
All methods should be camel case | Read More |
| Parameter | depositAmount |
All parameter names should be camel case | Read More |
See this naming guide for more details.
Android classes should be named with a particular convention that makes their purpose clear in the name. For example all activities should end with Activity as in MoviesActivity. The following are the most important naming conventions:
| Name | Convention | Inherits |
|---|---|---|
| Activity | CreateTodoItemActivity |
AppCompatActivity, Activity
|
| List Adapter | TodoItemsAdapter |
BaseAdapter, ArrayAdapter
|
| Database Helper | TodoItemsDbHelper |
SQLiteOpenHelper |
| Network Client | TodoItemsClient |
N/A |
| Fragment | TodoItemDetailFragment |
Fragment |
| Service | FetchTodoItemService |
Service, IntentService
|
Use your best judgement for other types of files. The goal is for any Android-specific classes to be identifiable by the suffix.
There are several best practices for organizing your app's package structure.
The way to do this is to group things together by their category. Each component goes to the corresponding package:
com.example.myapp.activities - Contains all activitiescom.example.myapp.adapters - Contains all custom adapterscom.example.myapp.models - Contains all our data modelscom.example.myapp.network - Contains all networking codecom.example.myapp.fragments - Contains all fragmentscom.example.myapp.utils - Contains all helpers supporting code.com.example.myapp.interfaces - Contains all interfacesKeeping these folders in each app means that code is logically organized and scanning the code is a pleasant experience. You can see a slight variation on this structure as suggested by Futurice on their best-practices repo.
Alternatively, we can package-by-feature rather than layers. This approach uses packages to reflect the feature set. Consider the following package structure as outlined in this post:
com.example.myapp.service.* - Is a subpackage for all background related service packages/classescom.example.myapp.ui.* - Is a subpackage for all UI-related packages/classescom.example.myapp.ui.mainscreen - Contains classes related to some app's Main Screencom.example.myapp.ui.detailsscreen - Contains classes related to some app's Item Details ScreenThis feature allows you to place DetailsActivity, DetailsFragment, DetailsListAdapter, DetailsItemModel in one package, which provides comfortable navigation when you're working on "item details" feature.
DetailsListAdapter and DetailsItemModel classes and/or their properties can be made package-private, and thus not exposed outside of the package. Within the package you may access their properties directly without generating tons of boilerplate "setter" methods.
This can make object creation really simple and intuitive, while objects remain immutable outside the package.
Resources should be split up into the following key files and folders:
| Name | Path | Description |
|---|---|---|
| XML Layouts | res/layout/ |
This is where we put our XML layout files. |
| XML Menus | res/menu/ |
This is where we put our AppBar menu actions. |
| Drawables | res/drawable |
This is where we put images and XML drawables. |
| Colors | res/values/colors.xml |
This is where we put color definitions. |
| Dimensions | res/values/dimens.xml |
This is where we put dimension values. |
| Strings | res/values/strings.xml |
This is where we put strings. |
| Styles | res/values/styles.xml |
This is where we put style values. |
See the full list of resources here and note the following:
res/values/colors.xml and reference the colors in layouts with @color/royal_blue.res/values/dimens.xml and reference these in layouts with @dimen/item_padding_left.Be sure to start properly organizing your resources early on in the development of an application. Be sure to check out the Ribot Code and Style Guidelines for a more extensive breakdown of suggested style and naming guidelines.
Often there are questions about organizing not just the source files but also better organizing the application resources. In a modern app, there are often hundreds of different layout files, drawables, styles, etc and by default these are all grouped together in a flat list within a single subdirectory (i.e res/layout). For now, keep the layout resource files in the same directory.
Refer to stackoverflow post for a discussion of explored options. The main problem is that if you try to use the nested resource layout approach, the current logic for the Android Studio's Gradle plug-in will not update the resource files after they have changed for nested resource sets. The current implementation attempts to check the resource directories using startsWith(), so a directory structure that is nested (i.e. src/main/res/layout/layouts and src/main/res/layout/layouts_category2) will choose src/main/res/layout/layouts consistently and never actually update the changes. A result, you will you have to rebuild/clean the project each time whenever making layout file changes.
It is up to you to decide which of the aforementioned approaches suits your project best.
However, in general Java programming, packaging apps by feature is considered preferable and makes a lot of sense.
