A presentation that Cam Barrie, James Brett and myself gave at Agile Australia 2013. The talk is about ways of building mobile apps that allow for the change and evolution you should expect when building exploratory mobile apps, and examples of the web and native code divide.

1. EVOLVING MOBILE ARCHITECTURES
@ MI9
James Brett, Mi9
Stewart Gleadow, Thoughtworks
Cameron Barrie, Bilue

2. Mi9 and Jump-in›❯
Initial mobile architecture›❯
Evolving Jump-in›❯
Recommendations›❯

3. Mi9 and Jump-in›❯
Initial mobile architecture›❯
Evolving Jump-in›❯
Recommendations›❯

5. 77%use another device
in front of the television

9. BUILD
MEASURELEARN

10. Mi9 and Jump-in›❯
Initial mobile architecture›❯
Evolving Jump-in›❯
Recommendations›❯

11. How do you build an app that’s
undefined and evolving?

12. OR

13. AND

14. NATIVE HYBRID WEB

16. WEB / NATIVE
BRIDGE
http://commons.wikimedia.org/wiki/File:Pont_du_Gard_HDR.jpg

18. ARCHITECTURE
MEANS YOU CAN
RESPOND TO CHANGE
FLEXIBILE
HAVING A

19. Mi9 and Jump-in›❯
Initial mobile architecture›❯
Evolving Jump-in›❯
Recommendations›❯

23. The app is just the
tip of the iceberg

24. App Backend

25. App BackendAPI
Decouple your app from the backend

26. App BackendAPI
Force logic to the API,
keep the app simple

27. How do we build simpler apps and
smarter backends?
• Principles of REST
• Serving data and style
• Product-aligned teams

28. Mi9 and Jump-in›❯
Initial mobile architecture›❯
Evolving Jump-in›❯
Recommendations›❯

29. CONCENTRATE ON BUILDING
A SIMPLE APP AND A GREAT API

30. DON’T LOCK YOURSELF INTO DOING
EVERYTHING NATIVELY
OR
EVERYTHING USING THE WEB

31. ARCHITECTURE
MEANS YOU CAN
RESPOND TO CHANGE
FLEXIBILE
HAVING A

32. Thank you

33. EVOLVING MOBILE ARCHITECTURES
@ MI9
James Brett, Mi9
Stewart Gleadow, Thoughtworks
Cameron Barrie, Bilue