Cwa-app-android: App size too big, minimization required

Created on 16 Jun 2020  路  9Comments  路  Source: corona-warn-app/cwa-app-android

Current Implementation

App download on the playstore is ~15MB (38 after install)

Suggested Enhancement

Minimize the app, remove unnecessary large libraries with minimal (native) implementations. Under one megabyte should be easily possible and the goal!

Expected Benefits

An app that just needs to generate, exchange and check random IDs should not need to be that big and will stop a lot of people from installing the app as space constraint is a common occurrence on Android, especially budget phones with small internal space so please find a way to minimize the size.

Edited to match enhancement template, did not show up on mobile github client used my apologies

enhancement in progress

Most helpful comment

Thanks for mentioning budget phones. You're right 38 MB is large for what little the app does. Size should be optimised in future releases.

Similar issue #482 got tagged "wontfix" unjustifiedly. SAP should stop closing important issues that should be fixed in the near term with future releases.

All 9 comments

Does it use the Android App Bundle?

see #482

Thanks for mentioning budget phones. You're right 38 MB is large for what little the app does. Size should be optimised in future releases.

Similar issue #482 got tagged "wontfix" unjustifiedly. SAP should stop closing important issues that should be fixed in the near term with future releases.

@tkowark Could you also take a look at the more extensive #482? This issue is a duplicate of #482 which was marked as wontfix despite listing potential steps to improve the app size.

Thanks for the pointer @ironjan . We're looking into both issues. But please note that main priorities right now are bug fixes and implementing planned features for the next releases. If we can reduce size along that path, we'll, of course, do that, but it is currently not a top priority.

@tkowark I fail to understand how your comment connects to my comment. According to the state of #482 (closed, wontfix), SAP/Telekom are not looking into the problem. According to this one #527 (duplicate, less detailed, open, enhancement), SAP/Telekom are looking into the problem. Your comment does not address the duplication nor the more detailed nature of #482.

So my question to you is: should all comments and steps that describe how the big app size can be solved copied from #482 into #527? No to mention the fact that there was no comment about the intentional closure of #482 in neither issue.

Sorry for the confusion @ironjan . I'll clarify with the team and get back to you about how we'll proceed with the two issues and the respective comments.

Ok, we clarified that issue with the team. Following proposal:

  • we'll reopen #482 as it provides more details on how size could be reduced
  • This issue will be closed accordingly to only have one central discussion point

But again, while the team will of course have possible improvements in size in mind, it is not a main priority. We appreciate any suggestions for that endeavour as comments in #482 !

Sorry for the confusion and best regards,
TK
Corona-Warn-App Open Source Team

Thanks @tkowark for a thoroughly explained response. This is the interaction style that would be great moving forward.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sdschulze picture sdschulze  路  3Comments

Diapolo picture Diapolo  路  3Comments

ironjan picture ironjan  路  3Comments

marceljay picture marceljay  路  3Comments

wmertens picture wmertens  路  3Comments