• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Building Mobile Apps Using Salesforce Geolocation Features
 

Building Mobile Apps Using Salesforce Geolocation Features

on

  • 328 views

Salesforce provides native geolocation features that can be used to add location-based services to any mobile app. Join us as we review how one company used these features to add location-based ...

Salesforce provides native geolocation features that can be used to add location-based services to any mobile app. Join us as we review how one company used these features to add location-based searching to their mobile Property Portfolio application. Additionally, we'll discuss how the geolocation features are used in their mobile Shopping Center Incident Reporting application. We'll cover how the applications use a combination of geolocation custom fields, SOQL queries, and Google Maps to support location-based searching, tagging, and reporting.

Statistics

Views

Total Views
328
Views on SlideShare
328
Embed Views
0

Actions

Likes
0
Downloads
5
Comments
0

0 Embeds 0

No embeds

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Building Mobile Apps Using Salesforce Geolocation Features Building Mobile Apps Using Salesforce Geolocation Features Presentation Transcript

    • Building mobile apps using Salesforce geolocation features Christopher Barrett, DDR Corp, Senior Manager of Business Applications @DDR_IT_CBarrett Benjamin Pirih, NTT Centerstance, Senior Consultant @BenjaminPirih
    • Salesforce 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 any litigation, risks associated with completed and any 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-K for the most recent fiscal year and in our quarterly report on Form 10-Q for the most recent fiscal quarter. These 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.
    • DDR Corp. Safe harbor DDR considers portions of the information in this presentation to be forward-looking statements within the meaning of Section 27A of the Securities Act of 1933 and Section 21E of the Securities Exchange Act of 1934, both as amended, with respect to the Company's expectation for future periods. Although the Company believes that the expectations reflected in such forward-looking statements are based upon reasonable assumptions, it can give no assurance that its expectations will be achieved. For this purpose, any statements contained herein that are not historical fact may be deemed to be forward-looking statements. There are a number of important factors that could cause our results to differ materially from those indicated by such forward-looking statements, including, among other factors, local conditions such as oversupply of space or a reduction in demand for real estate in the area; competition from other available space; dependence on rental income from real property; the loss of, significant downsizing of or bankruptcy of a major tenant; constructing properties or expansions that produce a desired yield on investment; our ability to buy or sell assets on commercially reasonable terms; our ability to complete acquisitions or dispositions of assets under contract; our ability to secure equity or debt financing on commercially acceptable terms or at all; our ability to enter into definitive agreements with regard to our financing and joint venture arrangements or our failure to satisfy conditions to the completion of these arrangements; and the success of our capital recycling strategy. For additional factors that could cause the results of the Company to differ materially from those indicated in the forward-looking statements, please refer to the Company's Form 10-K for the year ended December 31, 2012, as amended. The Company undertakes no obligation to publicly revise these forward-looking statements to reflect events or circumstances that arise after the date hereof.
    • Christopher Barrett DDR Corp Senior Manager of Business Applications @DDR_IT_CBarrett
    • All about DDR Corp. DDR Corp. owns and manages approximately 440 retail properties in the continental United States, Puerto Rico and Brazil. Our prime portfolio primarily features open-air, valueoriented shopping centers in high barrier-to-entry markets with stable populations and high growth potential. ▪ DDR Corp. aspires to be the most admired provider of retail destinations and the first consideration for retailers, investors, partners and employees. ▪ The company is publicly traded on the New York Stock Exchange under the symbol DDR. More information: http://www.ddr.com
    • Benjamin Pirih NTT Centerstance Senior Consultant @BenjaminPirih
    • All about NTT Centerstance NTT Centerstance is a consulting company specializing in business transformation through process improvement and application of cloud technologies. ▪ Platinum Cloud Alliance Partner with salesforce.com with one of the highest customer satisfaction ratings ▪ Ranked in top ten "Best of the Best" professional services firms by SPI research two years running ▪ 110+ employees with extensive management consulting, technology and business process experience More information http://www.nttcenterstance.com
    • Geolocation for DDR We use this technology to enhance our mobile applications: ▪ AdvancedSearch • Visualize DDR shopping center locations • Display locations of nearby DDR shopping centers • Search and display locations of nearby retailers ▪ LocationPicker • Better manage our portfolio of shopping centers through geolocation tagging of shopping center incident locations
    • Geolocation in Salesforce How to store geolocation information ▪ Before winter 13 release stored latitude and longitude as text fields • Consumed two fields • No location-based searching ▪ Winter 13 release created new geolocation field type • Compound field that contains both latitude and longitude • Supports Degree or Decimal notation • WITHIN operator for list views based on location • Location-based search on Salesforce objects using Distance and Geolocation
    • Technology Overview The following technologies were used in our applications: ▪ Visualforce and Apex ▪ SOQL Geolocation functions ▪ Visualforce Javascript remoting ▪ Google Maps Javascript API v3 ▪ Google Static Maps API v2 ▪ Google Places API ▪ jQuery
    • Demo - Visualize DDR shopping center locations
    • Query Geolocation Fields Perform SOQL query to return location based information ▪ New query syntax
    • Shopping Center Visualization Implementation Apex Controller retrieved location information via SOQL query Defined public property for our result in visualforce controller class JSON Encoded query
    • Shopping Center Visualization Implementation In Javascript render a Google Maps Marker
    • Demo - Display locations of nearby DDR shopping centers
    • Visualize Nearby Shopping Centers How did we search for nearby centers? ▪ Winter 13 Supports the Distance and Geolocation SOQL Functions • Distance Function calculates the distance between two locations in miles or kilometers • Geolocation Function returns a location based on the provided latitude and longitude – Must be used with Distance Function
    • Performing Distance Based Query Use SOQL to construct query
    • Google Places Search vs. Salesforce Location Query Ability to search and display locations of nearby retailers ▪ Used Google Places API to retrieve business information • No way to filter results for specific business types • Results were misleading / incorrect • Usage limits ▪ Create custom Salesforce object to mange retailer location information • Allowed complete control over search results • Can filter based on object fields in SOQL • Location-based search on Salesforce objects
    • Demo - Search and display locations of nearby retailers
    • Google Places Search vs. Salesforce Location Query Calling Google Places ▪ Used Google Places API Rest to access retailer information
    • Google Places Search vs. Salesforce Location Query Calling Salesforce geolocation Query
    • Incident Management Using Geolocation DDR wanted to better manage Shopping Center Incidents ▪ Constructed a custom object to store incident information ▪ Used Google Maps to plot incident locations and store in Salesforce ▪ Developed the capability to capture static map images
    • Demo – LocationPicker for Incident Management
    • Incident Management Using Geolocation Define a method with the @Remote Action attribute in Controller Perform Javascript Remoting call to Apex Method
    • Incident Management Static Maps API Usage Retrieve Incidents and construct URL to Google Static Maps API
    • Incident Management Static Maps API Usage Make HTTP Request and Return Image Result
    • Incident Management Static Maps API Usage Save Http Result Blob as Attachment
    • Conclusion 1. Demonstrated DDR’s business benefits from the usage of native geolocation functionality. 2. Demonstrated real world mobile applications showcasing native geolocation functionality. 3. Explained the core technologies and methodologies used when working with geolocation fields. We would encourage you to develop applications using this technology.