Top Banner
How We Built Touch A behind the scenes look Pratima Arora, Product Manager - @pratima_arora Doug Chasman, Developer - @dchasman Matthew Davidchuck, Developer - @matthewsftouch Rachna Singh, Quality Engineer - @rachnasingh
18
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: How We Built Touch

How We Built Touch

A behind the scenes look

Pratima Arora, Product Manager - @pratima_arora

Doug Chasman, Developer - @dchasman

Matthew Davidchuck, Developer - @matthewsftouch

Rachna Singh, Quality Engineer - @rachnasingh

Page 2: How We Built Touch

Safe Harbor

Safe harbor statement under the Private Securities Litigation Reform Act of 1995:

This presentation may contain forward-looking statements that involve risks, uncertainties, and assumptions. If any such uncertainties

materialize or if any of the assumptions proves incorrect, the results of salesforce.com, inc. could differ materially from the results

expressed or implied by the forward-looking statements we make. All statements other than statements of historical fact could be

deemed forward-looking, including any projections of product or service availability, subscriber growth, earnings, revenues, or other

financial items and any statements regarding strategies or plans of management for future operations, statements of belief, any

statements concerning new, planned, or upgraded services or technology developments and customer contracts or use of our services.

The risks and uncertainties referred to above include – but are not limited to – risks associated with developing and delivering new

functionality for our service, new products and services, our new business model, our past operating losses, possible fluctuations in our

operating results and rate of growth, interruptions or delays in our Web hosting, breach of our security measures, the outcome of

intellectual property and other litigation, risks associated with possible mergers and acquisitions, the immature market in which we

operate, our relatively limited operating history, our ability to expand, retain, and motivate our employees and manage our growth, new

releases of our service and successful customer deployment, our limited history reselling non-salesforce.com products, and utilization

and selling to larger enterprise customers. Further information on potential factors that could affect the financial results of

salesforce.com, inc. is included in our annual report on Form 10-Q for the most recent fiscal quarter ended July 31, 2012. This

documents and others containing important disclosures are available on the SEC Filings section of the Investor Information section of

our Web site.

Any unreleased services or features referenced in this or other presentations, press releases or public statements are not currently

available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based

upon features that are currently available. Salesforce.com, inc. assumes no obligation and does not intend to update these forward-

looking statements.

Page 3: How We Built Touch

Pratima Arora – Product Management

Page 4: How We Built Touch

Agenda

• Story of Touch

• Architecture and Challenges

• Sneak Preview into Roadmap

• Panel

Page 5: How We Built Touch

Touch is a re-imagined

Salesforce experience across

any device, leveraging HTML5.

Page 6: How We Built Touch

Let’s start from the beginning…

Page 7: How We Built Touch

We need to think mobile first

Mobile can’t lag

Support ALL form factors

Wait a minute…

Native apps = Software

Salesforce = No Software

Page 8: How We Built Touch

HTML5 was the Winner

• You want customizations

• You want it on every device

• Our challenges:

• How far can we push HTML?

• How do you prioritize 12 years of

features from us and YOU?

• What about offline, contacts etc.?

Page 9: How We Built Touch

Touch on Mobile Safari and AppStore

Page 10: How We Built Touch

Doug Chasman – Developer

Page 11: How We Built Touch

Harder Then it looks

• Touch Architecture

• Web Version

• Hybrid App with Mobile

SDK

• Components made

ground-up using HTML5,

CSS3 and Javascript

Touch

Services App / Tab Set

Recents Lists

Page Layouts

Records

Related Lists

API Dynamically

Loaded From

Salesforce Cloud

Touch Services

(available in Safari

and hybrid app)

iPad Salesforce

Cloud

Actions

Chatter

Controllers

View

Controllers

Render Service

Event Service

Action Service

Storage Service

Loaded From

Apple App Store

Hybrid App

OAuth

Models

SmartStore

Models

View Defs

Page 12: How We Built Touch

Testing on multiple form factors is a challenge

• Tablets, Phones and In-between

• Automation

• 80% test coverage on browser

• Simulator testing

• Device testing

• Manual Testing

• Performance Testing –

• Mobile Network Virtualization

Page 13: How We Built Touch

Even Harder…

Performance Offline VisualForce

Page 14: How We Built Touch

Touch goes beyond Mobile

• Contacts 2.0 – Web Touch

Experience

• Touch Platform: Mobile SDK

Page 15: How We Built Touch

Try Touch Today

• Pilot in Dec

• iPad for Sales

• Chatter, Contacts, Oppty, Accounts, Tasks

and Custom Objects

• Beta July Release

• Edit and Create

• Design Iterations

• Today: Touch on Safari

Page 16: How We Built Touch

Touch Roadmap

• Touch tablet

• App on appstore

• App-picker, list views, other apps etc.

• Touch phone pilot

• Offline access

• Visual-force access

• Etc…

Page 17: How We Built Touch

Pratima Arora

Product Manager

@pratima_arora

Doug Chasman

Developer

@dchasman

Matthew Davidchuck Rachna Singh

Developer

@matthewsftouch

Quality Assurance

@rachnasingh

Page 18: How We Built Touch