App Templating

Here is a presentation we made at AppDays 2015, based on our experience on large projects.
For more insight, you can read our blog post upon the topic:
http://applidium.com/en/news/app_templating/

Transcript

1. App templating One core project, several apps @AdrienCouque - @Applidium - @The_Minh
2. What brought us to make app templates? One project can become multiple applications.
3. What brought us to make app templates? One project can become multiple applications.
4. Customisation needs Features • Timetables • Itinerary search • Maps • Around me • Traffic info • … 4
5. Customisation needs 5 Itinerary search Around me Traffic info
6. Customisation needs Look • Colours • Pictograms • Fonts • … 6
7. Customisation needs 7 TADAO Ametis Bibus
8. Customisation needs Content • Various back-end technologies 8
9. Real-time Theoretical Customisation needs 9
10. App template? • An efficient way to replicate (native) apps • Same core codebase • Allows you to adjust: ◦ features ◦ look ◦ content 10
11. Criteria for an app template Is your project suitable for the app template format? 11
12. Criteria for an app template Is your project suitable for the app template format? 12
13. LIFECYCLE An app template is not trivial and requires you to organise consequently.
14. • Reliability • Time-to-market Industrialisation 14 • Scalability • Overall Product approach
15. Product team 15 Build phase + roadmap
16. Operation team 16 Deployment of apps
17. Teamwork 17 Staged rollout + quick iterations
18. LESSONS LEARNED Little app template will grow big!
19. A longer conception phase… 19 Make the right choices with all the target apps in mind
20. … for a large-scale impact! 20 Time spent is then amortised with the number of variations
21. Extra care while designing • Functional & graphic specificities should be thoroughly explored ahead of developments • Specificities should only rely on a configuration • APIs should be consistent across all apps 21
22. WRAP-UP 22
23. Thank you! @AdrienCouque - @Applidium - @The_Minh