What is Gradle ? Gradle History & Why need Gradle ? What is Gradle Files and project structure ? Android Build System & the build graphe . Build diff build types Product flavors. Merging Resources. Adding dependencies. Automate Sign Configuration for apk. APK split. Writing Your Own Custom Tasks. Performance Recommendations. What is new in Gradle?

1. Gradle Build Capabilities

2. Goals
- What is Gradle ?
- Gradle History & Why need Gradle ?
- Android Build System & the build graphe .
- Build diff build types
- Product flavors.
- Merging Resources.
- Adding dependencies.
- Automate Sign Configuration for apk.
- APK split.
- Writing Your Own Custom Tasks.
- Performance Recommendations.
- What is new in Gradle?

3. Gradle
- Gradle is a general-purpose build tool
Gradle is an open-source build automation tool that is designed to be
flexible enough to build almost any type of software based in Groovy.

4. Gradle History.
Idea come from :
For years, builds had the simple requirements of compiling and packaging
software.
But the modern software development has changed, and so have the needs
for build automation.
Today, projects involve large and diverse software stacks,
apply abroad of testing strategies. With the rise of agile practices, builds
must support early integration of code as well as frequent and easy delivery
to both test and production environments.

5. Gradle
- The core model is based on tasks
Any build process modeled as a graph of tasks , which is
one of the reasons why Gradle is so flexible. And that
task graph can be defined by both plugins and your
own build scripts, with tasks linked together via the
task dependency mechanism.

6. Gradle Files and the build process ?

7. Android Build
System using
Gradle

9. Gradle Capabilities >> Build types & Flavours
You need to automate changes of different build variants As ( debug - staging – release - ....)

10. Gradle Capabilities >> Product Flavours
Product Flavors and Variants : You want to build essentially the same
application, but with different resources and/or classes.
EX: You want to add Android activities or other Java classes to individual
product flavors.

11. Gradle Capabilities >> Product Flavours

12. Gradle Capabilities >> Product Flavours
Each product flavor can have its own values of the following properties,
among others, which are based defaultConfig:
- applicationId
- minSdkVersion
- targetSdkVersion
- versionCode
- versionName
- signingConfig

13. Gradle Capabilities >> Product Flavours
Also Each flavor defines its own source set and resources :
main/java, you can also add source files in:
- app/src/falvour1/java
- app/src/falvour2/java
You can also add additional resource files in:
- app/src/falvour1/res
- app/src/falvour2/res/layout

14. Gradle Capabilities >> Merging resources
- Merging resources from different
flavors and build types.
- If we want to change resources
according to certain flavor.
- You want to add Android activities
or other Java classes to individual
product flavors.

15. Gradle Capabilities >> Adding dependencies
One of the biggest features in gradle build adding libraries.
main/java, you can also add source files in:

16. Gradle Capabilities >> Adding dependencies
will download library and it’s transitive libraries by default
We could disable transitive libraries for certain library :

17. Gradle Capabilities >> Adding dependencies
You can also exclude a transitive dependency in the
dependencies block.

18. Gradle Capabilities >> Automate APK Signing
You need to digitally sign an APK so it can be released to the Google Play store.

19. Gradle Capabilities >> APK Split
Although you should build a single APK to support all your target devices whenever possible, that might result in a very
large APK , one of the ways to reduce apk size is split based in certain conditions .
We can split vs :
Abi , density , language
We can also group some of tragests together
.

20. Gradle Capabilities >> APK Split
Also we can order to generate beside “universalAPk” with all combinations together

21. Gradle Capabilities >> Write Custom Task
Copy Apks to another folder to automate this process
Copy APKs to another folder
task copyApks(type: Copy) { from("$buildDir/outputs/apk") {
exclude '**/*unsigned.apk', '**/*unaligned.apk' }
into '../apks'
}
NOTE : If you would like the copyApks task to run every time you do
a build, make it a dependency of the build task,
build.dependsOn copyApks

22. References
-
https://docs.gradle.org/current/userguide/what_is_gradle.html#3_gradle_has_several_fixed_build
_phases
-https://docs.gradle.org/current/userguide/tutorial_using_tasks.html#sec:using_methods
-https://docs.gradle.org/current/userguide/kotlin_dsl.html
-
https://docs.gradle.org/current/userguide/dependency_management_for_java_projects.html#sec:co
nfigurations_java_tutorial
- https://gradle.org/whats-new/gradle-5/#new-gradle-invocation-options
- https://developer.android.com/studio/build/configure-apk-splits#configure-split
- https://developer.android.com/studio/build/dependencies#dependency_configurations
-http://google.github.io/android-gradle-
dsl/current/com.android.build.gradle.BaseExtension.html#com.android.build.gradle.BaseExtension:
buildTypes(org.gradle.api.Action)