3 ms·
That would be difficult, I think. "Cloud service" does not really define any capabilities present or absent in the library. Even if you split it up in things li
by DCKing 12y ago
That would be difficult, I think. "Cloud service" does not really define any capabilities present or absent in the library. Even if you split it up in things like "mapping service" and "cast service" then a lot of details will differ between otherwise equivalent providers. It's not something you can easily generalize. And if you generalize it, you're stuck with this generic API until your phone gets updated.
This project and some of Amazon's libraries basically take a subset of Google's Play Services API as canonical and reimplement those. That's not an ideal solution either, but at least it provides minimal pain for app developers.
- jayd16 12y ago>And if you generalize it, you're stuck with this generic API until your phone gets updated. The cloud service version and the client library code would not be coupled to OS version and updated with APKs just like how Google Play Services does. Its not any harder than exactly what Google is currently doing with play services. I'm not proposing anything that isn't already being done besides some standardized calls and some extra service discovery.