apk-size for `api […]` vs `implementation […]` dependencies
up vote
0
down vote
favorite
i know that adding an Android dependency (for example OkHttp) as api 'com.squareup.okhttp3:okhttp:3.11.0'
in one of my app modules will make it available to other modules when included.
This removes the need to add implementation 'com.squareup.okhttp3:okhttp:3.11.0'
in the other modules.
Is there any difference in the resulting APK size to have each module include the dependency separately as implementation [...]
instead of just once as api [...]
in a module that other app-modules depend on.
These links describe the compilation-visibility differences but not whether or not there is any difference in the resulting APK.
android dependencies apk build.gradle
add a comment |
up vote
0
down vote
favorite
i know that adding an Android dependency (for example OkHttp) as api 'com.squareup.okhttp3:okhttp:3.11.0'
in one of my app modules will make it available to other modules when included.
This removes the need to add implementation 'com.squareup.okhttp3:okhttp:3.11.0'
in the other modules.
Is there any difference in the resulting APK size to have each module include the dependency separately as implementation [...]
instead of just once as api [...]
in a module that other app-modules depend on.
These links describe the compilation-visibility differences but not whether or not there is any difference in the resulting APK.
android dependencies apk build.gradle
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
i know that adding an Android dependency (for example OkHttp) as api 'com.squareup.okhttp3:okhttp:3.11.0'
in one of my app modules will make it available to other modules when included.
This removes the need to add implementation 'com.squareup.okhttp3:okhttp:3.11.0'
in the other modules.
Is there any difference in the resulting APK size to have each module include the dependency separately as implementation [...]
instead of just once as api [...]
in a module that other app-modules depend on.
These links describe the compilation-visibility differences but not whether or not there is any difference in the resulting APK.
android dependencies apk build.gradle
i know that adding an Android dependency (for example OkHttp) as api 'com.squareup.okhttp3:okhttp:3.11.0'
in one of my app modules will make it available to other modules when included.
This removes the need to add implementation 'com.squareup.okhttp3:okhttp:3.11.0'
in the other modules.
Is there any difference in the resulting APK size to have each module include the dependency separately as implementation [...]
instead of just once as api [...]
in a module that other app-modules depend on.
These links describe the compilation-visibility differences but not whether or not there is any difference in the resulting APK.
android dependencies apk build.gradle
android dependencies apk build.gradle
asked Nov 9 at 18:44
xst
5602930
5602930
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53231645%2fapk-size-for-api-vs-implementation-dependencies%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown