First steps toward GCM support #2182
Conversation
|
How does this change affect the final size of the APK? |
|
Before: -rw-r----- 1 mpcomplete eng 8952459 Dec 14 16:17 Fitness.apk After: -rw-r----- 1 mpcomplete eng 12020761 Dec 14 15:24 Fitness.apk |
|
3MB is probably more than we want to pay in the default build. Can we make GCM an optional module that an app can add if it wants it? Rather than having a monolithic APK that grows as we add more services, I'd like to get to a model where a developer can pick the services they want from a gallery of services and they only pay the costs for the services they've picked. @collinjackson and I have been talking about how to do this for Firebase. It sounds like we'll want that sort of thing for GCM as well. |
|
Yeah, I definitely want to make it optional (and also in a separate repo). I haven't thought yet about how to do that, but I hope we can use the same mechanism for all the service types we want to add (location, camera, etc). |
BUILD.gn
Outdated
There was a problem hiding this comment.
This example no longer exists in this repo.
There was a problem hiding this comment.
Yeah, I have it symlinked for easy building. Not for checkin.
New gcm mojo service with Android implementation. Temporarily checking into flutter repo until it's easier to add third party services.
|
lgtm |
First steps toward GCM support
3 participants
This adds initial support for the Google Cloud Messaging API.