How many methods will the support library add to apps? |
|||
Issue descriptionOnce we have a support library prototype we should ensure the number of methods it contributes, when compiled into an app, is reasonable. If not, we should communicate this to developers (and point them to proguard / multi-dex).
,
Sep 14 2017
,
Oct 9 2017
See crbug.com/758615#c11 and crbug.com/758615#c15 there are cirka 1100 methods in android.webkit that would make it into the support library, and ca 80 of those methods were added since L.
,
Oct 9 2017
when I write "since L" I mean between L and O-MR1
,
Oct 24 2017
Right, so we have the numbers. IMO 80 methods doesn't sound too bad, though the support library itself will multiply that number by some small constant (<5) because of corresponding interfaces/plumbing. I guess we might add 20-30 methods per year, which in 5 years would mean 100-150 methods, multiply that by 3 (for support library plumbing), and we have 300-500 methods added to the app. Though I would assume proguard can remove any methods not used by the app itself. Does that sound reasonable?
,
Oct 24 2017
Yeah, that's unlikely to be a problem for anyone.
,
Oct 24 2017
Cool, I'm marking this as fixed. We might wanna revisit again after we have a finished version of the support library. |
|||
►
Sign in to add a comment |
|||
Comment 1 by gsennton@chromium.org
, Aug 24 2017