continuous delivery - case study of the ios app swedish call?
DESCRIPTION
The purpose of this document is to serve as discussion material for CD practices. The app itself is not a bestseller but I want to highlight why I enjoy to continue to improve it. The Swedish name for the app is "Okänt Nummer?"TRANSCRIPT
Continuous Delivery Case Study, Swedish Call?
How I adapted Continuous Delivery practices when developing the iOS app
“Swedish Call?”
By: Anders Lundsgård, @anderslundsgard
The purpose of this document is to serve as discussion material for CD practices. The app itself is not a bestseller but I want to highlight why I enjoy to continue to improve it.
First architecture
Numberservice
X
Numberservice
Y Numberservice
Z
REST
REST
SOAP
The Problem
Number service
X
Number service
Y Number service
Z
REST
REST
SOAP
• Long iteration for adding new Number service
– Apple review takes 1-2 weeks
– Users have to update app often
• No tracking of app usage
– How many users do I have?
– Which number services are best?
I needed to learn what worked and not to feed new ideas.
New architecture
Number service
X
Number service
Y Number service
Z
REST
REST
SOAP
App service Business logic moved from app to cloud service
REST
Advantages
• No need for app update to add or modify number service
• Business logic written in .NET instead of Objective-C
• Ability to trace how and when the app is used
• Ability to toggle new features to lower risk
Feedback loop minimized
theleanstartup.com
From 1-2 weeks to about 30 minutes
Best of all…
…feedback makes it fun to continuously improve the app