When we built the Klarna App, most of us had experienced the fast feedback nirvana that can be achieved with backend services or web clients. Android and iOS are different worlds though and initially it looked impossible to have a similar experience on those platforms. We trudged on, convinced that we could find a better way. I’ll start by setting the context on what we wanted to achieve with the design of the Klarna App (i.e. single-language, many teams, fast feedback). Next I will talk about what sort of considerations we took into account overall and for each individual platform when designing the development/release process. Specifically: • how our web deployment evolved • on iOS, what are some of the unique challenges for iOS, how/why we deliver Yellow to everyone’s phones and how we enable even CXOs to get branch builds on their phone. • on Android, what are some of the unique challenges, how/why we deliver Yellow to everyone’s phones and how we enable even CXOs to get branch builds
Case Taintor
Case is an engineer that has been with Klarna for 7 years. He started in the Tel Aviv site and was part of the initial idea of what the KonferenSE could be, helping turn the first GDoc into a reality. He’s been part of every KonferenSE since. Passionate about great products, great developer experience and great ways to share ideas
Find out more about the life at Klarna: [ Ссылка ]
Information about current job openings: [ Ссылка ]
