Samuel Littley, Google
In the server side world, we can and do lean heavily on redundancy, scaling, and direct control to engineer reliability; however, in the mobile world these well known facets of SRE (amongst others) are virtually non-existent. We typically have no binary rollbacks or downgrades, no forced updates/upgrades, and no ability to turn it off and back on again. Users rely on mobile applications more and more, and it's important that SREs consider client-side reliability. This talk discusses practices, principles, and processes that can be applied in the mobile world to make client-side code a first-class citizen, along with real-world case studies of what has and hasn't worked.
Note: Much of the talk will centre around Android, although many of what is discussed can be applied to other platforms
Samuel Littley, Google
Samuel Littley has been a Site Reliability Engineer at Google for 2 years, and is currently working in London on a team supporting the Google Search App and Google Play Services, as well as working on a wider effort supporting production best practices for Google's wide array of mobile applications.
SREcon18 Europe/Middle East/Africa Open Access Videos
Sponsored by Indeed
Open Access Media
USENIX is committed to Open Access to the research presented at our events. Papers and proceedings are freely available to everyone once the event begins. Any video, audio, and/or slides that are posted after the event are also free and open to everyone. Support USENIX and our commitment to Open Access.
author = {Samuel Littley},
title = {{SRE} for Mobile Applications},
booktitle = {SREcon18 Europe/Middle East/Africa (SREcon18 Europe)},
year = {2018},
address = {Dusseldorf},
url = {https://www.usenix.org/node/218966},
publisher = {USENIX Association},
month = aug
}