Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

20
Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice Gordon Jackson, Principle Architect – Heroku [email protected] Tom Scott, VP Appirio Thursday, September 17, 2:00 - 2:40 Moscone West, 2006

Transcript of Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Page 1: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

 Gordon Jackson, Principle Architect – Heroku  [email protected]

Tom Scott, VP Appirio Thursday, September 17, 2:00 - 2:40 Moscone West, 2006

Page 2: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Introductions

Page 3: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Heroku Connect: Seamless Data Sync between Force.com & PostgresQL

Page 4: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Heroku Connect Syncs Directly to Salesforce Clouds Seamless two-way data between customer-facing apps and your business on Salesforce

Employee Apps Customer Apps

Heroku Connect

Page 5: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

About Diageo, Appirio & the Mobile Survey App

Page 6: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Diageo is a global leader ($21B revenue in 2014) in beverage alcohol with iconic brands in spirits, beer and wine.

About Diageo

Page 7: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Who is Appirio

Cloud & Crowd Strategy | Technology Implementation | Systems Integration Custom Development | Management Consulting | Change Enablement

More than 3.5 million users and 900 enterprises moved to the cloud

Page 8: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

WHY?

•  Capture field intelligence from retail stores in order to evaluate distribution partner performance against goals and use as input to business decision-making.

HOW?

•  iOS and Android app for field sales to answer surveys about retail pricing, positioning, special displays, etc.

•  Salesforce as authoritative source of survey and result data. Heroku and Heroku Connect to act as “service layer” for mobile app.

WHEN?

•  October 2013 original rollout; now in version 3 with 100k+ surveys/month.

Diageo Mobile Survey App

Page 9: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

The App in Action

Page 10: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

•  Login; Nearby accounts; Survey List, Answer questions (types, photo), Review, Offline Live Demo

Page 11: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Salesforce Survey Setup

Page 12: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Salesforce Survey Question Creation

Page 13: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Salesforce Results

Page 14: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Salesforce Results

Page 15: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Application Architecture

Page 16: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Architecture Diagram

Page 17: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

•  Why Heroku?

•  Scalability (10k to 100+k overnight), licensing, de-couple db for better mobile UX

•  Why Heroku Connect?

•  SFDC as master source for contacts, surveys/questions, results

•  Building integration code would take months and significant budget

•  Why Custom App?

•  Need Diageo-specific UX – everything from app icon to fully custom branding and UX

•  Hybrid – speed to market and need for both iOS and Android support

•  Environment Management?

•  Multiple full stack environments for dev, test, prod (mobile app, heroku, heroku connect, sfdc sandboxes)

Mobile Survey Solution Architecture - FAQ

Page 18: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

•  Benefits

•  Very simple to setup and configure

•  Simply does its job – synchronize data between SFDC and Heroku

•  Issues Encountered

•  Sept 2013 – 10 min delay before Contact data available in Postgres (now can be real-time w/streaming API)

•  Nov 2013 – failed during SFDC maintenance (now self-corrects)

•  Mar 2014 – switch from CloudConnect to HerokuConnect and default schema name change

•  Nov 2014 – DB upgrade – bug restricted change of Postgres DB without re-install

•  Mar 2015 – DB upgrade – delay provisioning new HC instance

•  Apr 2015 – issue with related data creation when we populate NAME field (HC now protects against this)

• 

Heroku Connect Lessons Learned

Page 19: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Q & A

www.heroku.com/connect

Page 20: Unite Customer-Facing Apps with a Salesforce Backend: Heroku Connect in Practice

Thank you