Pricing Request a Demo
Home / Google Play Services
Enjoy the best mobile SDKs news, tips & tricks, sent to you by mail

[Infographics] The State of Mobile SDKs at the Start of 2017

March 8, 2017 4:07 PM

During the course of 2016, we’ve published two reports uncovering the state of mobile SDKs: one in April and on in October. We explored which SDK categories are most popular, exposed which SDKs are leading their category and even compared global and local trends. And judging by last year, we knew 2017 would be as interesting to explore, if not more.

We’ve just published a new report, looking at January 2017. The data comes from a thorough analysis of over 100,000 Android apps, featured in various Google Play stores around the world and available to download for free.  Together, these apps integrate hundreds of SDKs, from the top industry players to new players hoping to take the mobile world by storm.

And let us tell you right now that looking at the January data, and comparing it to the data from our previous reports (and the months in between), we’ve spotted some truly fascinating trends…

Main Highlights

Please note that we are sharing here a partial selection of the findings that are presented in the full report. To access the full report (download is free) click here.

Continue Reading

Mobiles on Fire: Am I Using Firebase or Google Play Services?

September 13, 2016 5:15 AM

It’s been almost five months now since Google announced the new generation of Firebase with great fanfare at this year’s Google I/O, and true enough mobile developers have been adapting. In fact, our research at SafeDK uncovers that nearly 8% of top apps are already actively using Firebase, with Firebase Crash Reporting definitely leading the pack in strength (and that’s just a sneak peek spoiler at our next Android SDK Market Report).

But if you’re a mobile developer and have tried integrating Firebase then you may have found yourself feeling more confused than anything else.

You see, Firebase is this big SDK from the house of the rising Google that answers many of a developer’s needs with the premise being “and it’s all completely free”. Analytics, Crash Reporting, Database, Storage space, Push Notifications and more. Some aren’t even mobile SDKs, just great services for developers such as hosting services and so on.

But Google already has a huge amazing all-you-need-ever-wanted-and-can-ask-for SDK. It’s called the Google Play Services. An SDK which over 96% of [Android] developers use, according to our research. And well, that’s exactly where the confusing parts kick in.

For all of you TL;DR folks – Firebase is actually a part of Google Play Services. What does that mean? Well, read on.

Continue Reading

Android Developer? Here is what to pay attention to when using Google Play Services

September 21, 2015 8:09 PM

Most Android developers use Google Play Services. In a survey we run at SafeDK, we found that nearly 70% of all Android apps have at least one package of Google Play implemented, and often even more than that. From ads to analytics, through support of social media, cloud and push notifications, Google Play Services offer app developers a variety of capabilities, and it’s great. Having said that…there is also a downside to all this goodness.

In order to offer such rich support, Google Play Services module is comprised of many individual packages, and contains a whopping 29,000 method count which is problematic due to the 65K limit issue.

The Unbearable Lightness of Multidexing

Interestingly enough, based on SafeDK’s big data, we found that approximately half of the Android apps out there integrate the full module of Google Play Services, but actually use very few of the packages it contains. Naturally, Android developers would want to optimize their Google Play Services selection…

I’ve written about how to deal with this issue, in a previous post where I provided some insights on how to identify the packages that are right for you. I also touched on the number of methods each package adds to your app. 

But now, Google has released a new version of Google Play Services. And while some things have changed, the bottom line has barely shifted:

  • It still adds a large number of methods to your app.
  • You still must use the large “base” package in order to use any package.
  • You still have to use the entire play services (can’t pick-and-choose) to continue using the deprecated appstate package.

Continue Reading

Reducing Your Method Count: The Google Play Services Edition

June 30, 2015 3:50 PM

Avid Android developers have longed faced a headache-inducing problem with their apps. The number of methods an app can have is limited. Well, it used to be limited. At long last, the good folks at Google provided a solution last October, but it was far from ideal. Though very easy to implement, the multidex solution complicated and prolonged compilation time significantly. Not standing still, starting with Lollipop (Android 5.0), the entire Android virtual machine was revolutionized to offer a much more endurable solution, the kind that even improves on the regular compilation time.

However, for the time being, the Lollipop solution isn’t ideal too. It requires developers to develop against Lollipop only, which could be problematic since most apps want to be compatible with wider ranges of audiences and might fear using features that aren’t available in earlier Android versions. So right now, the Lollipop solution is a good future-Android solution, but might not have much impact in the foreseeable present.

So what can be done in the meantime? We all agree that you shouldn’t give up on features and capabilities, just to avoid reaching the 65K limit. But there is no doubt that the best practice would still be to reduce your application method count.

So how can you still try to reduce your method count without losing that little spark that makes your app special?

Continue Reading