Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Michael Montgomery - Scaleable App Deployment

Michael Montgomery - Scaleable App Deployment

Michael Montgomery discusses the process utilized by Victorious to deploy 100+ apps to the iOS and Android app stores every week

Sharif Ahmed

May 12, 2016
Tweet

Other Decks in Programming

Transcript

  1. Michael Montgomery Business | Product Implementation Engineer II LinkedIn Profile:

    Michael Montgomery 1. Roadmap 2. Scalability 3. Industry
  2. ROADMAP FEBRUARY 2015 Purpose Provide an internal tool to build,

    maintain, deliver and update all Victorious apps Requirements 1. VAMS: Victorious App Management System; source of all app data 2. Fastlane: the vehicle in which to deliver app information TIMELINE APRIL 2015 SEPTEMBER 2015 FEBRUARY 2016 FEBRUARY 2015 MAY 2016
  3. ROADMAP Before VAMS/Fastlane ❖ Fragmented app data ❖ Dependencies ❖

    Unreliable & error prone ❖ Integrated into CMS & runs locally ❖ Highly scalable ❖ Consistent results Cost (per build request) ➢ 2 hrs. setup/48 hr. turnaround ➢ 30 min update ➢ 0.5 hrs. setup/0 hr. Turnaround ➢ 8 min update
  4. SCALABILITY 1 LIVE (Manual) ❖ Eng hours, outside of client

    updates ❖ Fragmented release process ❖ Gathering & storing app information 100 + LIVE (Automatic) ❖ Reduce Eng hours spent/trajectory ❖ Optimize release process ❖ Self-serve platform
  5. SCALABILITY 100+ apps | two week sprints OPTIMIZE APP RELEASE

    REDUCE TIME TO SHIP CONTINUED DEVELOPMENT 1 2 3
  6. INDUSTRY Source © Statista WHO ❖ Releasing at minimum 5

    updates a month ❖ Location of clients ❖ Platform WHY ❖ Reduce Operational costs ❖ Anytime, anywhere ❖ Scalable Mobile App Downloads (in millions)