This project is part of a
about how to build Android applications using
Dagger 2 (2.11-2.17) with the
Dagger Android extension,
Dagger Android support extension,
Butterknife (8.7-8.8), and Model-View-Presenter (MVP) pattern
with support for
A Larger Project
This project is a smaller, derivative of a larger project. One of the main purpose of this project is to showcase / walkthrough a specific portion of the larger project's architecture. Take a look at the following larger project for a more real-world example on how to apply Dagger Android (2.11-2.17), Butterknife (8.7-8.8), Clean Architecture, MVP, MVVM, Kotlin, Java Swing, RxJava, RxAndroid, Retrofit 2, Jackson, AutoValue, Yelp Fusion (v3) REST API, Google Maps API, monolithic repo project management with Gradle, JUNit 4, AssertJ, Mockito 2, Robolectric 3, Espresso 2, and Java best practices and design patterns.
This project now uses Android Studio 3.2.0-rc02. Previous versions of Android Studio (2.4/2.3.3 and below) will no longer be able to build this project.
The following major Dagger 2 and Butterknife versions works with this project;
- Dagger 2: 2.11, 2.12, 2.13, 2.14, 2.15, 2.16, 2.17
- Butterknife: 8.7, 8.8
There are 4 main branches:
- Uses regular
Fragmentclasses with a
- Uses regular
Fragmentclasses with a
- This branch is an extension of the master branch, containing all changes from master.
- Take a look at PR #49 for the main diff from the master branch.
- Same as master except written in Kotlin.
- This branch is an extension of the master branch, containing all changes from master, which is then translated to Kotlin.
- Take a look at PR #67 for the main Java -> Kotlin translation of the master branch.
- Same as master-support except written in Kotlin.
- This branch is an extension of the master-support branch, containing all changes from master-support, which is then translated to Kotlin.
- Take a look at PR #68 for the main Java -> Kotlin translation of the master-support branch.
Why is the
minSdkVersion of the non-support setup in master 17? Can it be lower?
There are 2 main reasons why the
minSdkVersion of the non-support setup can only be as low as 17.
Thus, the lowest
minSdkVersion supported for the non-support setup in master is 17. It cannot be lower.
What about the
minSdkVersion of the support setup in master-support? Can it be lower than 14?
No. The dagger.android.support API only supports
as low as 14.
- As of API 28, fragments and all related fragment code have been deprecated in favor of the support fragments in the support lib. Therefore, it is recommended that the master-support and master-support-kotlin be used as reference instead of the master and master-kotlin branches. See issue #86.
This demonstrates dagger.android, Butterknife, and MVP setup using 5 examples:
- Activity with 1 Fragment.
- Activity with 2 Fragments.
- Activity with 1 Fragment with 1 child Fragment.
- The Fragment in example 1 as a floating dialog.
- The Fragments in example 3 as a floating dialog.
A Quick Gist
For a quick overview of dagger-android 2.11 usage with support for
@PerChildFragment scopes, take a look at
Read the walkthrough for the complete guide with proper step-by-step setup and explanations.
Read the blogs for a complete walkthrough of this app:
- Creating a project, from scratch, using the new Dagger.Android (2.11-2.17) dependency injection
framework with support for
- Using Butterknife (8.7-8.8) to replace a lot of handwritten boilerplate view binding code. ARTICLE
- Restructuring the code to Model-View-Presenter (MVP) to increase testability, maintainability, and scalability. ARTICLE
If you don't like reading blogs or are just too "pro" and would like to just explore the repository, you may want to look at the issues instead;
Copyright 2018 Vandolf Estrellado Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.