@Scale is a series of technical conferences for engineers who build or maintain systems that are designed for scale.
Building applications or services that scale to millions or even billions of people presents a complex set of engineering challenges, many of them unprecedented. The @Scale community is focused on bringing people together to openly discuss these challenges and collaborate on the development of new solutions.
Scaling iOS @ Google
Google started on iOS with just one app and then scaled to over 60 apps. It’s been an amazing journey with lots of lessons learned and with a lot of improvements yet to come to scale even more not only on iOS but also on other platforms.
Michele is a passionate iOS developer. He’s currently leading the Google Calendar iOS app and other iOS efforts in Google. He worked on many Google apps including the Google Search app and Chrome for iOS and he develops and maintains shared libraries that are used in all of the Google apps.
Pieter De Baets
React Native: bringing the best of web development to native
React Native enables developers to build word-class native mobile applications using the React.js framework. Since launching last year on iOS and Android, the project has attracted a ton of interest inside Facebook and in the open-source community. We’ll talk about how React has allowed us to bring the velocity of web development to native apps, how engineers can use the framework to develop their product across platforms, and how React’s programming model helps us scale our codebase.
Pieter De Baets is a Software Engineer working on React Native at Facebook London. After growing up in the land of beer and chocolate, he moved to London to work on Facebook’s iOS app, contributing to projects like Comments, Year in Review and Navigation.
Infer: Moving fast with static analysis
For tech companies like Facebook, high quality software is important.However, new code is being produced and shipped fast in big code bases shared by hundreds of engineers. This makes it difficult to create error-free code. Automatic testing and dynamic analysis are very helpful and static analysis complements these techniques. Static analysis is a technique able to detect software errors statically, before a product is actually shipped, and without running the code. In a company like Facebook where the release cycle is fast compared to more traditional industries,the deployment of static analysis is very challenging. In this talk we describe the Infer Static Analyzer, its architecture and our experience integrating it into the software development cycle at Facebook.
Dulma Churchill is a Software Engineer at Facebook in the Static AnalysisTools team. She has worked in the field of static analysis for over three years, first at the startup Monoidics, and then at Facebook. Before that,she completed her PhD at the University of Munich in the field of analysis of memory bounds using type systems. She also co-authored several papers in the areas of static analysis and type theory.
Don’t forget the web
There’s a common understanding that native is inherently better than web when it comes to mobile. That was almost certainly once the case, but while our attention has been focused elsewhere, the web has been getting a whole lot better. Could it be that the web is just as viable as Android or iOS when it comes to a mobile strategy? Or could it even be – heaven forbid – that the web is in many ways *better* than native?
Jeremy Keith lives in Brighton, England where he makes websites with the splendid design agency Clearleft. You may know him from such books as DOM Scripting, Bulletproof Ajax, and HTML5 For Web Designers. Jeremy spends most of his time goofing off on the internet, documenting his time-wasting on adactio.com, where he has been writing for over ten years.
3000 images per second
Twitter creates approximately 3000 unique images and transfers approximately 200 gigabytes of images per second. Learn how Twitter’s media platform team has designed a system to meet these demands and adapt to the evolving needs of the product. This talk will also cover the ongoing transition to progressive JPEG, including the migration to Facebook’s Fresco image library on Android.
Henna Kermani is a software developer on Twitter’s Android platform team in San Francisco. Before moving to platform, she contributed to the client media composition and consumption experience, including the custom Twitter camera.
6 lessons learned scaling mobile at SoundCloud
SoundCloud’s Android and iOS apps fast became our primary listening platforms. This talk will highlight the biggest things we’ve gotten right and wrong in the process. We’ll discuss how and when we’ve been able to share code, APIs and values. We also face many platform-specific challenges. We’ll compare and contrast some of the problems faced, patterns adopted and tools developed for one platform or the other.
Jamie is a Mobile Engineer at SoundCloud, where he works on the Android app and mobile API. He has been focusing on the Android platform for over 5 years and has previously worked at The Guardian and Novoda. Matej has more than 10 years experience as a Software Engineer. He currently works on the iOS app at SoundCloud, before which he was on the Core Engineering team at the Central European Media Enterprise. While Matej is an engineer by trade, he is passionate about how software affects users and believes the user experience should be as important to developers as coding itself.
When mobile IDEs need to scale
Many developers use IDEs for smaller projects which may be hundreds or thousands of lines of code, but what happens when you’re developing apps which are 10x or more larger? James and Al will talk about the work they’ve been involved in to improve IntelliJ IDEA and Nuclide to address the issues faced by developers on large mobile apps, and how Facebook has interacted with the open source community to share the benefits of their work.
James manages the open source program at Facebook, and developer infrastructure projects such as Nuclide and Phabricator in Menlo Park and Seattle.
Al is part of the Developer Efficiency team at Facebook and focuses on issues related to Android development. He has been developing Android applications and devices for a variety of companies since the first version of Android was made available to the public, and worked on Java applications for a number of years before that.
Code of Conduct
We believe that any kind of harassment is unacceptable and so expect speakers and attendees to honour the Open Code of Conduct detailed here http://todogroup.org/opencodeofconduct/#@Scale.
If you experience or witness unacceptable behaviour – or have any other concerns – please report it by contacting us via email@example.com