Add your SDK
Home / User Experience
Enjoy the best mobile SDKs news, tips & tricks, sent to you by mail

App Monetization vs. User Experience: Can I Have Both?

May 8, 2017 3:35 PM

Let’s get real for a second. App monetization is what it’s all about. Most of us get into the mobile app game not just to make the world a better place, but also to bring home the bacon. We put in hours upon hours trying to figure out where our users get lost, we pour hundred and thousands of dollars on trying to get the right users to notice us, and we consider most UX changes longer than we would a prospective spouse. That’s how important our app monetization is to us.

After all the hard work and long hours, we deserve a little something-something for our time and effort. So how frustratingly nerve-wrecking, not to say annoying, it is to learn that the very thing that should have turned a profit ends up hurting the bottom line? Especially when it’s not even the part of the app you wrote?

According to our January 2017 data analysis, most free Android apps use Advertisement SDKs in their app:

SafeDK | Most Popular Mobile SDK Categories Jan 2017

Ads are definitely the #1 source for app monetization in today’s market. It’s why we see their share consistent quarter after quarter.

And since SDKs are what we’re all about at SafeDK – ad-networks not excluded – we started monitoring what ad-networks are showing users. Allow me to share with you some real-life cautionary tales and answer the age-old question about user experience and app monetization: can I have my ads and eat it too?

Continue Reading

Enough with the Mobile SDK Mess: A New Technology Is Born

February 9, 2016 4:05 PM

SafeDK is presenting at MWC – Set a demo meeting!

In a previous blog post I’ve written (Mobile SDKs: Use with Caution), I mentioned the potential risks related with integrating Mobile SDKs into your mobile app. ‘SDKs’ as in these off-the-shelf 3rd party tools that app developers integrate into their mobile app for advertising, payment, analytics, social and many other functions. We all know that SDKs are a necessity in the mobile development process, but not all app publishers are aware of how these SDKs can affect the app’s performance, stability, battery consumption, security and privacy.

After going through an extensive analysis of a tens of thousands of apps and hundreds of different SDKs, we realized that there are 2 major domains of problems when using 3rd party SDKs. Both are crucial:

  • Security and Privacy – SDKs may contain viruses, malwares, backdoors or, most commonly, piggy-bag your app permissions to access your users’ private data.
  • User Experience – SDKs may contain bugs, consume a great deal of battery power and data, crash your app, slow down your app, and so forth.

During the last few months, we all read about major SDKs-related issues: apps that were banned from the stores because of a specific SDK that violated Apple or Google regulations, an ad-network SDK which  displayed ads that were  incompatible with the app’s ‘spirit’ (e-cigarette commercial in a kids app, someone?), marshmellow incompatibility of SDKs in an app that was supposed to be compatible… and the list goes on and on.

Basically, app developers must all ask themselves the following, ASAP:

Do I really know what’s going on with my app's SDKs? Can I really vouch for my app when I use so many 3rd party codes?

That’s exactly what led us to establish SafeDK. I focused my entire career on mobile development, and like everyone else, I constantly implemented SDKs the messy way… It took me a while, but I finally realized I was out of control, using so many SDKs. But I sure wasn’t going to work on all these SDKs’ functionalities in-house, so I created SafeDK to provide an optimal and elegant solution to this dilemma. This is simply what we say: Implement as many SDKs as you want, in order to create a wonderful app in the shortest time-to-market possible, but use SafeDK to maintain transparency and control over the SDKs code.

Continue Reading