Ty is a Principal Engineer at Uber where he leads the Mobile platform group and is the chairman for Uber’s Open-Source program. He has a passion for tools, frameworks, and open-source to help developers make great mobile apps. He is a Google Developer Expert for Android and Kotlin, engaging regularly with the community through conferences, open-source, and writing, as well as an organizer for conferences and meetups. He is an angel investor and tech advisor, as well as a member in multiple venture capital advisory syndicates. Ty has been at Uber for 6 years and prior to that he worked at Twitter on the Fabric developer tools, Evernote, and a variety of smaller startups and consulting firms
Balancing Speed and Reliability: The Double-Edged Sword of Third-Party Libraries
14:35 > 40 min
Using third-party libraries in your apps can be a great way to save engineering time and move faster, but can also bring significant risk. If a library malfunctions and causes an outage, it may take days or weeks to get it solved for all your users. Apps have long update cycles and don’t have the luxury of hotfixes when something goes wrong. At Uber, as an app that people rely upon for making their income, getting to the doctor, or commuting to work, reliability in our app is the top priority. Learn how Uber decides when mobile libraries are safe to include and when they should be avoided.
We’ll review how Uber analyzes external libraries to reduce risk, walk through some horror stories when things went wrong, and discover some techniques that can help keep reliability for your user when the worst does happen. You’ll walk away with a tactical framework for evaluating libraries in your own apps.