When Should A Mobile Developer Reevaluate Their Tools?

#Crashlytics is becoming a part of Firebase, and #Apteligent is becoming a part of Workspace ONE. For mobile developers who currently use these tools, they must decide if adopting the larger platform is worth it to keep using the tool or if they need to search for replacements.

But there are many other reasons (besides deprecations and buyouts) that mobile developers should also consider when deciding if their current tools are the best ones for helping to improve their app's performance.

Eric Lanz, Senior iOS Engineer at Embrace, goes over what mobile developers and their teams should think about when making these decisions.

0:22 What Kinds Of Tools Do Mobile Developers Use?
1:17 How Often Does A Mobile Developer Change Their Tools?
2:03 What Happens When A Tool Is Deprecated?
2:49 What's Happening With Crashlytics And Fabric?
3:41 How Does A Mobile Developer Know They Need A New Tool?
4:46 What If A Mobile Developer Is Unhappy With Their Current Tool?
5:47 What Should A Mobile Developer Look For In A Tool?
6:24 What Features Would Help Improve An App's Performance?

Who We Are:
Embrace is a mobile monitoring and developer analytics platform. We are your one-stop shop for all your mobile application performance monitoring and error debugging needs, with full access to every user session, including all network requests, views, logs, and errors in the exact way a user experienced them.

Take the guesswork out of debugging, and solve bugs in minutes instead of days.

This video is brought to you by Embrace:





Connect with Eric Lanz:

mobile developer,crashlytics,apteligent,sdk,mobile monitoring,error debugging,