This document outlines a 5-step process for choosing the right third-party tools (SDKs) for a mobile app: 1. Create a list of needed SDKs based on the app's requirements like monetization, analytics, and performance. 2. Use a marketplace to compare SDKs and narrow down options by eliminating low-rated or unneeded SDKs. 3. Ensure SDK quality and behavior using in-app controls to monitor SDK performance in real-time. 4. Evaluate which SDKs provide the best cost-benefit and user experience by talking to developers about issues. 5. Periodically revisit SDK decisions to ensure they still benefit the app and users without new problems.

1. 5 Steps in Choosing the Right 3rd Party Tools
(SDKs) for your Mobile App

2. HIGH LEVEL STEPS TO CHOOSE THE RIGHT SDKS
Step #1: Additional Enrichment- Create a list
Step #2: Compare SDKs, narrow down your List &
Search for the stars!
Step #3: How to ensure SDKs quality & behavior?
Step #4: Which SDKs are keepers?
Step #5: Revisit your decision

3. STEP #1: ADDITIONAL ENRICHMENT- CREATE A LIST
Identify your app’s needs to understand which SDKs you
need to look for:
Monetization
Analytics
Retention
Performance
Crash reporting

4. SafeDK Marketplace
GET INSPIRED…SAFEDK MARKETPLACE FOR SDKS
For more SDK’s you might wish to try &
explore all SDK categories at the

5. Also try SafeDK App X-Ray, scan
popular apps or apps similar to yours,
and learn which SDKs they use
GET INSPIRED…SAFEDK APPS X-RAY

6. STEP #2: COMPARE SDKS, NARROW DOWN YOUR LIST &
SEARCH FOR THE STARS
Use SafeDK Marketplace to eliminate the low-rated SDKs, the ones that got
bad reviews, and the ones which don’t offer what you need.
* Check multiple parameters during the elimination process. Consider which parameters are important to you.
Analytics SDK 1 Analytics SDK 2

7. …AB testing SDKs may be slow and difficult to execute…
STEP #3: HOW TO ENSURE SDKS QUALITY & BEHAVIOR
But! you can speed things up…
Our In-App SDK Control & Protection
will provide data analysis on
how your SDKs behave in real-time, and
will allow you to instantly turn SDKs off or
on, in case you need to do so.

8. Well, it’s not a clear-cut…
 Estimate cost Vs. benefit
 Evaluate your app’s behavior
 Has your overall product improved?
 Is your product more broad?
 How would you rate your user experience?
STEP #4: WHICH SDKS ARE KEEPERS?

9. Talk with your development team members:
 How easy is the SDK to maintain?
 Did you experience any performance issues?
 How responsive was it? How easy to implement?

10. Get the habit of exploring new SDKs every now
and then and keep asking your fellows dev team
members if they are still happy with the SDK
Maintenance.
STEP #5: REVISIT YOUR DECISION
Remember:
It’s not a Catholic Wedding…!

11. Did you and your product benefit from
implementing these SDKs?
Keep asking yourself:

12. Do your users complain more about a
specific something?

13. If there’s a cost, is it one you can afford,
now that you know exactly what you’re
getting?

14. It’s always a good practice to revisit your
SDK decisions. Hey, that’s evolution!

15. THANK YOU!