Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Analyse APK size #3381

Open
anandwana001 opened this issue Jun 28, 2021 · 4 comments
Open

Analyse APK size #3381

anandwana001 opened this issue Jun 28, 2021 · 4 comments
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Work: High It's not clear what the solution is. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@anandwana001
Copy link
Contributor

anandwana001 commented Jun 28, 2021 •
edited
Loading

General Investigation of databinding, view binding, and Jetpack Compose. One option we were considering was to migrate to Compose once it's ready, so it'd be good to get an idea on:

  1. Code maintenance reduction/simplification for each option
  2. APK sizes
  3. Compile times
  4. An analysis of features that are available in each & how they compare
  5. A basic idea on adoption difficulty (for view binding & Compose since we're already using databinding)

This is a big issue and required documentation approved by core team members before working on it. Suggestions are welcome in the comments below.
@anandwana001 anandwana001 added this to the Backlog milestone Jun 28, 2021
@BenHenning
Copy link
Member

@anandwana001 I think some context might be missing here--why is this work needed?

@anandwana001
Copy link
Contributor Author

@BenHenning This is more of a research-based issue that do we have any places where we are using DataBinding instead of ViewBinding and that might help in APK size reduction. So, I had created this issue.

@BenHenning
Copy link
Member

Got it. Maybe we should repurpose this issue to be a general investigation of databinding, view binding, and Jetpack Compose? One option we were considering was to migrate to Compose once it's ready, so it'd be good to get an idea on:

  • Code maintenance reduction/simplification for each option
  • APK sizes
  • Compile times
  • An analysis of features that are available in each & how they compare
  • A basic idea on adoption difficulty (for view binding & Compose since we're already using databinding)

WDYT?

@anandwana001
Copy link
Contributor Author

Sounds good, updating the issue.

@BenHenning BenHenning mentioned this issue Sep 1, 2021
Merged
6 tasks
@Broppia Broppia added the Impact: Low Low perceived user impact (e.g. edge cases). label Jul 14, 2022
@BenHenning BenHenning added Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Z-ibt Temporary label for Ben to keep track of issues he's triaged. issue_user_developer and removed mini-project labels Sep 14, 2022
@BenHenning BenHenning removed this from the Backlog milestone Sep 16, 2022
@seanlip seanlip added enhancement End user-perceivable enhancements. and removed issue_type_infrastructure labels Mar 28, 2023
@MohitGupta121 MohitGupta121 added the Work: High It's not clear what the solution is. label Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement End user-perceivable enhancements. Impact: Low Low perceived user impact (e.g. edge cases). Issue: Needs Break-down Indicates that an issue is too large and should be broken into smaller chunks. Work: High It's not clear what the solution is. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Projects
[Team] Developer Workflow & Infrastructure - Android
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
5 participants
@seanlip @BenHenning @anandwana001 @MohitGupta121 @Broppia