Your SlideShare is downloading. ×
How We Built Touch
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

How We Built Touch

232
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
232
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
10
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. How We Built TouchA behind the scenes lookPratima Arora, Product Manager - @pratima_aroraDoug Chasman, Developer - @dchasmanMatthew Davidchuck, Developer - @matthewsftouchRachna Singh, Quality Engineer - @rachnasingh
  • 2. 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.
  • 3. Pratima Arora – Product Management
  • 4. Agenda • Story of Touch • Architecture and Challenges • Sneak Preview into Roadmap • Panel
  • 5. Touch is a re-imaginedSalesforce experience acrossany device, leveraging HTML5.
  • 6. Let’s start from the beginning…
  • 7. We need to think mobile first  Mobile can’t lag  Support ALL form factors  Wait a minute…  Native apps = Software  Salesforce = No Software
  • 8. 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.?
  • 9. Touch on Mobile Safari and AppStore
  • 10. Doug Chasman – Developer
  • 11. Harder Then it looks Salesforce • Touch Architecture iPad Cloud • Web Version Loaded From Hybrid AppApple App Store OAuth • Hybrid App with Mobile SmartStore Touch Chatter SDK Services View View Defs App / Tab Set • Components made Dynamically Models Recents Lists API Loaded From Salesforce Cloud Controllers Actions Models Page Layouts ground-up using HTML5, Controllers Touch Services(available in Safari Render Service Records CSS3 and Javascript and hybrid app) Event Service Related Lists Action Service Storage Service
  • 12. 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
  • 13. Even Harder…Performance Offline VisualForce
  • 14. Touch goes beyond Mobile • Contacts 2.0 – Web Touch Experience • Touch Platform: Mobile SDK
  • 15. 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
  • 16. Touch Roadmap • Touch tablet • App on appstore • App-picker, list views, other apps etc. • Touch phone pilot • Offline access • Visual-force access • Etc…
  • 17. Pratima Arora Doug Chasman Matthew Davidchuck Rachna SinghProduct Manager Developer Developer Quality Assurance@pratima_arora @dchasman @matthewsftouch @rachnasingh