GOTO Berlin is a vendor independent international software development conference with more that 60 top speakers and 600 attendees. The conference covers topics such as Java, Open Source, Agile, Architecture, Design, Web, Cloud, New Languages and Processes.

<< previous speaker next speaker >>

Mattias Björnheden, Front end chapter lead at Spotify

Mattias Björnheden

Biography: Mattias Björnheden

Mattias Björnheden has spent the last ten years developing software for mobile devices. He is currently an engineering manager at Spotify where he has been leading mobile teams in several parts of the organisation. Starting out three years ago in a small team responsible for the Android application Mattias helped build and launch the free product on mobile paving the way for Spotify's growth in the last couple of years. Now he manages a team that works on features related to Playlists, Your Library and since recently social. Before joining Spotify Mattias worked with feature phones at device companies like Sony Ericsson followed by joining the smartphone revolution on the day the Android platform was released.

Twitter: @amnbletochange

Presentation: Mobile at Scale

Track: Mastering Mobile / Time: Friday 15:50 - 16:40 / Location: Hall 10

The Spotify mobile applications are complex clients with multiple features and offline requirements. Building and releasing them involves hundres of people. This talk is about organisational and architectural trade-offs required to continuously deliver new features and improvements while ensuring that the user is always able to play their favourite songs without issues. Spotify uses a mix of technologies ranging from C++ client libraries to specialised backend services to deliver user content.

You will learn how technical decisions are influenced by the organisation and vice versa. We will look at the importance of great tools and infrastructure to build cloud focused mobile applications at this scale. In three years we have made the journey from ten mobile developers to almost a hundred and from a client centric mobile architecture to a feature focused architecture backed by online services. This is the story on how we made that journey happen, what went wrong along the way and how we ended up in a better place compared to where we started.