Understanding the Terms of Service

Total Page:16

File Type:pdf, Size:1020Kb

Understanding the Terms of Service Appendix A Understanding the Terms Of Service This appendix provides an overview of the main documents and topics concerning the terms of service (TOS) of the platforms I discussed in the previous chapters. It is very important that you know how to legally use the previously mentioned technologies and also legally profit from them. There are some documents that I invite you to read carefully and in their entirety and whose main points I will comment on in the next pages. The documents to be familiar with concerning the first part of the book, which is about developing web apps using Google Maps services, are: Google Maps/Google Earth APIs Terms of Service and their connected documents: https://developers.google.com/maps/terms. Google Maps FAQ: https://developers.google.com/maps/faq. In particular, consider the sections “Understanding the Terms of Service”, “Usage limits”, and “Advertising on your Map”. In addition to these documents, it important to be familiar with the End User TOS of Google Earth/Maps (http://www.google.com/intl/en-us/help/terms_maps.html), which every user of the software and its services must accept. These TOS and their connected documents can be reached from within the maps itself, since the link to them must be explicitly displayed in every Google Maps implementation (Figure A-1). 299 300 APPENDIX A: Understanding the Terms Of Service Link to End User TOS Figure A-1. How to reach the End User TOS from within the map itself If you use jQuery and jQuery Mobile, you also need to agree to the framework license here (http://jquery.org/license). For the second part of the book (hybrid apps) and the third (native apps), you need to read and accept the Xcode License Agreement (Xcode ° About Xcode ° License Agreement). If you want to be enrolled in the iOS Developer Program you first need to register as an Apple Developer and agree to the terms and conditions of the Registered Apple Developer Agreement (https://developer.apple.com/programs/terms/registered_apple_developer_20100301.pdf), then you need to read and agree to the iOS Developer Program License Agreement (https://developer.apple.com/membercenter/index.action#agreements). If you create hybrid apps, you also need to know and agree to the Google Maps API TOS and related documents. In the following sections I will illustrate the most important points from these documents, however I recommend you read them in their entirety. APPENDIX A: Understanding the Terms Of Service 301 TOS for Developing Web Apps with Google Maps API First, you need to know that the terms are composed of the Google Maps/Google Earth APIs Terms of Service (https://developers.google.com/maps/terms), The Legal Notices (http://www.google.com/intl/en-us/help/legalnotices_maps.html), and the Privacy Policy document (http://www.google.com/policies/privacy). You should read every one of these documents. The basic take-away from the Google Maps API TOS is that you can use the API in a web app as long as your Maps API implementation is free and publicly accessible (Section 9.1 of Maps/Google Earth APIs TOS); otherwise, you need to use the Google Maps API for Business. So, for example, you cannot make an API implementation accessible only to members of an intranet or to people who registered for a site with a fee. However, and this is of the greatest interest to us, if you develop a mobile app, this rule does not apply (Section 9.1.2). You can sell a Google Maps-based hybrid app in the Apple App Store. This last exception was added in 2011 (see http://googlegeodevelopers. blogspot.it/2011/04/updates-to-google-maps-apigoogle-earth.html) and was clearly meant to encourage the use of Google Maps API in mobile app development. If you want to make a web app accessible to both desktop computers and mobile devices by selling it in the App Store, you must keep the desktop version freely accessible. Among the requirements for using the Google Maps API, I would like to highlight the requirement to show the link on the map to the End User Terms (see Figure A-1) and to show the proper attribution to Google and other third-party content providers (trade names, trademarks, service marks, logos, domain names, and other distinctive brand features). You must be careful not to hide the information in the bottom part of the map (Figure A-2), otherwise this may result in a violation of the TOS. Attributions Figure A-2. You must not hide the attributions of Google and other content providers Another important point concerns a user’s privacy and geolocation privacy. As I mentioned throughout the book, before using user location data, you must get the user’s permission and your app must let the user revoke consent at any time. These are some of the main points to know, but I strongly recommend you to read the TOS in their entirety. I also suggest you consult the FAQs here: https://developers.google.com/maps/faq. The “Usage limits” section explains the limits of the free Google Maps API (as well as the Google Maps JavaScript API, which I talked about in this book). The current limit is fixed at 25,000 map 302 APPENDIX A: Understanding the Terms Of Service loads per day. If you are lucky enough to exceed this maximum, you need to enroll in automated billing of excess map loads in the Google APIs Console or purchase a Maps API for Business license. You can find more information in the FAQ. Note that there are also usage limits for geocoding if you intend to use this functionality. In addition to the FAQ, you can consult the Permission Guidelines which includes a tool (Permissions Tools) that asks you questions about the content you plan to use and then displays the usage requirements and guidelines (Figure A-3). I did not find the tool so useful because it offers a very limited number of scenarios, but you can try it out here: http://www.google.com/permissions/geoguidelines.html. Figure A-3. The Permission Tool helps you understand the usage requirements for your Google Maps implementation Advertising on the Maps When using the Google Maps API, be aware that Google reserves the right to include advertising in the maps images and in the Places search results. (See Google Maps/Google Earth APIs Terms of Service, Section 4.3). As of November 2012, the service does not include advertising on the map APPENDIX A: Understanding the Terms Of Service 303 images (perhaps they do not want to drive away users in this period of competition following the introduction of its rival Apple Maps). However, it is possible that in the near future advertising on map tiles will become effective. If you do not want advertising on the maps (if and when such a practice should become effective), you can contact the Google Maps API for Business sales team to obtain a Google enterprise license, which will allow you to avoid advertising. In addition to advertising by Google, you can also monetize your maps through your AdSense account (if you own one). The Google Maps JavaScript API offers an AdSense Library, allowing you to put advertising on your Google maps, either in a web app or in a hybrid app. The section of the official documentation dedicated to the AdSense library is available here: https://developers.google.com/maps/documentation/javascript/advertising As you can see, the library is very simple to use and you can display advertising in many different formats (see Figure A-4). Figure A-4. Some ads displayed through the AdSense library. With this tool you can get a preview of different types of ad formats: https://google-developers.appspot.com/maps/documentation/javascript/examples/ads-adunit 304 APPENDIX A: Understanding the Terms Of Service If you decide to release an app for free on the App Store and you still want to generate revenue, you could simply implement advertising on the map through the AdSense library. TOS for Developing Hybrid and Native Apps with Xcode Before you begin developing hybrid or native apps, you must agree to the Xcode License Agreement (Xcode ° About Xcode ° License Agreement). Within that agreement, which you should read in its entirety, Section 2 (Permitted License Uses and Restrictions), subsection F Location Services, states, “Subject to these terms and conditions, you may only use such Location APIs and services to enable applications you develop (“Applications”) to access location data (for example, the real-time geographic location of a user’s computer) from users who consent to such access.” As I mentioned earlier in the book, it is necessary ask the user for location permission: By default, iOS asks the user for permission when a geolocation function is triggered. Whether you use the W3C Geolocation API or the Core Location library, you must be careful not to bypass or alter this default behavior. If you want to be enrolled in the iOS Developer Program, you need to register as an Apple developer and agree to the terms here: https://developer.apple.com/programs/terms/registered_ apple_developer_20100301.pdf. Then, you must agree to the iOS Developer Program License Agreement: https://developer.apple.com/membercenter/index.action#agreements (You need to be enrolled to view the documents.) In the last document you can find many references to how you can use location services and Apple Maps. At the beginning of the document, in Section 1.2 Definitions, the Apple Maps service itself is defined as “the mapping platform and Map Data provided by Apple via the MapKit API for iOS version 6 or later and for use by You only in connection with Your Applications”.
Recommended publications
  • Software Development Methodologies on Android Application Using Example
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by VUS Repository POLYTECHNIC OF ŠIBENIK DEPARTMENT OF MANAGEMENT SPECIALIST STUDY OF MANAGEMENT Ivan Bumbak SOFTWARE DEVELOPMENT METHODOLOGIES ON ANDROID APPLICATION USING EXAMPLE Graduate thesis Šibenik, 2018. POLYTECHNIC OF ŠIBENIK DEPARTMENT OF MANAGEMENT SPECIALIST STUDY OF MANAGEMENT SOFTWARE DEVELOPMENT METHODOLOGIES ON ANDROID APPLICATION USING EXAMPLE Graduate thesis Course: Software engineering Mentor: PhD Frane Urem, college professor Student: Ivan Bumbak Student ID number: 0023096262 Šibenik, September 2018. TEMELJNA DOKUMENTACIJSKA KARTICA Veleučilište u Šibeniku Diplomski rad Odjel Menadžmenta Diplomski specijalistički stručni studij Menadžment Razvojne metode programa na Android platformi koristeći primjer Ivan Bumbak [email protected] Postoji mnogo razvojnih metoda programskih rješenja koje se mogu koristiti za razvoj istih na bilo kojoj platformi. Koja metoda će se koristiti ovisi o zahtjevnosti samog projekta, koliko ljudi radi na projektu, te u kojem vremenskom roku projekt mora biti isporučen. U svrhu ovog diplomskog rada razvijena je Android aplikacija putem tradicionalne metode, iako su danas sve više i više popularne takozvane agile metode. Agile, ili agilan, znači biti brz i sposoban reagirati na vrijeme te prilagoditi se svim promjenama u bilo kojem trenutku razvoja projekta. U radu su objašnjenje najpopularnije agile metode te su prikazane prednosti korištenja agile metoda u odnosu na tradicionalnu metodu. (37 stranica
    [Show full text]
  • Google Earth Engine Sentinel-3 OLCI Level-1 Dataset Deviates from the Original Data: Causes and Consequences
    remote sensing Technical Note Google Earth Engine Sentinel-3 OLCI Level-1 Dataset Deviates from the Original Data: Causes and Consequences Egor Prikaziuk * , Peiqi Yang and Christiaan van der Tol Faculty of Geo-Information Science and Earth Observation (ITC), University of Twente, 7500 AE Enschede, The Netherlands; [email protected] (P.Y.); [email protected] (C.v.d.T.) * Correspondence: [email protected] or [email protected]; Tel.: +31-534-897-112 Abstract: In this study, we demonstrate that the Google Earth Engine (GEE) dataset of Sentinel-3 Ocean and Land Color Instrument (OLCI) level-1 deviates from the original Copernicus Open Access Data Hub Service (DHUS) data by 10–20 W m−2 sr−1 µm−1 per pixel per band. We compared GEE and DHUS single pixel time series for the period from April 2016 to September 2020 and identified two sources of this discrepancy: the ground pixel position and reprojection. The ground pixel position of OLCI product can be determined in two ways: from geo-coordinates (DHUS) or from tie-point coordinates (GEE). We recommend using geo-coordinates for pixel extraction from the original data. When the Sentinel Application Platform (SNAP) Pixel Extraction Tool is used, an additional distance check has to be conducted to exclude pixels that lay further than 212 m from the point of interest. Even geo-coordinates-based pixel extraction requires the homogeneity of the target area at a 700 m diameter (49 ha) footprint (double of the pixel resolution). The GEE OLCI dataset can be safely used if the homogeneity assumption holds at 2700 m diameter (9-by-9 OLCI pixels) or if the uncertainty in the radiance of 10% is not critical for the application.
    [Show full text]
  • A Google Earth Engine Wetland Extent Mapping Tool Using Open Source Optical and Radar Satellite Sensors
    1/16/2020 AGU - iPosterSessions.com A Google Earth Engine Wetland Extent Mapping Tool using Open Source Optical and Radar Satellite Sensors Melissa Ferriter, Erica O'Connor, Alice Lin, Christopher Notto, Benjamin Holt, Bruce Chapman NASA Jet Propulsion Laboratory, NASA DEVELOP National Program PRESENTED AT: https://agu2019fallmeeting-agu.ipostersessions.com/Default.aspx?s=02-1E-D1-3C-F1-F0-4D-AE-39-1A-14-5D-1A-41-19-95&pdfprint=true&guestview=true 1/13 1/16/2020 AGU - iPosterSessions.com BACKGROUND Google Earth Engine, a cloud based geospatial processing platform that hosts a multi-petabyte catalog of satellite imagery, allows for large scale processing and analysis It is challenging to map wetlands at a large scale due to their spatial heterogeneity, dynamic nature, and spectral similarity to other landcover types Due to the pivotal role of wetlands in our environmental law and their vulnerability to the changing climate, there is a need for fully automated, standardized, on-demand wetland mapping on national and global scales Our objective was to create an automated, multi-sensor, and seasonal approach for wetland mapping to aid end users in assessing wetland gain and loss across the state of Minnesota https://agu2019fallmeeting-agu.ipostersessions.com/Default.aspx?s=02-1E-D1-3C-F1-F0-4D-AE-39-1A-14-5D-1A-41-19-95&pdfprint=true&guestview=true 2/13 1/16/2020 AGU - iPosterSessions.com METHODS We used an object based random forest approach to classify three landcover types: wetland, upland, and open water The results of the random forest
    [Show full text]
  • Progressive Web Applications
    Bachelor’s thesis Degree programme in Information and Communications Technology 2019 Archana Karki PROGRESSIVE WEB APPLICATIONS - Powerful websites, functional as native mobile apps BACHELOR’S THESIS | ABSTRACT TURKU UNIVERSITY OF APPLIED SCIENCES Degree programme in Information and Communication Technology 2019| 60 pages Archana Karki PROGRESSIVE WEB APPS • Powerful websites, usable as native mobile apps Current web platform and browsers are adequately powerful to support mobile and desktop applications. Application Program Interfaces (APIs) that supports the integration of mobile device and web browsers can execute features such as notifications, push messages, home screen icon, device camera and so on. The concept of progressive web apps is to make regular websites functional as mobile and desktop app, without compromising the user experience of traditionally used native apps. In order to understand the concept of Progressive Web Apps (PWAs), a functional app was created using HTML, CSS, JavaScript, along with the manifest file, service workers, and web APIs. The primary objective of the thesis was to understand and implement the technologies of Progressive Web Applications (PWAs). Hence, a detailed study of the topic and development of a PWA was also carried out. The study showed that one PWA could serve the function of a website, mobile app and a desktop app efficiently. On one hand, the technology used for making a PWA is not too complicated for web developers using HTML, CSS, and JavaScript, and on the other hand, simple files can turn an existing HTTPS website into a fully functional app, saving the cost of developing a new native app. KEYWORDS: Web apps, web, native apps, hybrid app, service workers, app shell, cache API, device integration and notification API.
    [Show full text]
  • Exploring the Prevalence and Evolution of Android Concerns: a Community Viewpoint
    Journal of Software Exploring the Prevalence and Evolution of Android Concerns: A Community Viewpoint Sherlock A. Licorish* Department of Information Science, University of Otago, PO Box 56, Dunedin 9054, New Zealand. Manuscript submitted May 3, 2016; accepted August 12, 2016. * Corresponding author. Tel.: 64 3 479 8319; email: [email protected] doi: 10.17706/jsw.11.9.848-869 Abstract: In line with growing awareness of the need for systems to adapt quickly to change, there has been increasing interest in the evolution of software systems. Research has particularly considered developer-led activities change over time. Comparatively less consideration has been given to the study of software evolution as driven by the wider community of stakeholders. Although, a project’s wider community is central to the feedback system and project success. We have contributed to such efforts and studied the evolution of architecture issues and non-functional requirements in the Android project, as identified by the wider Android community1. We mined the Android issues tracker, employing n-gram analysis in our examination of 21,547 issues. We observe that most architecture-related issues were located in Android application layer, and these issues increased with time. Additionally, usability-related concerns were reported most when they were held to be given greatest attention. Outcomes suggests that Android’s open model and shared ownership have positively impacted Google’s success, which could provide a useful lesson for other similar projects. Key words: Android, android architecture, android non-functional requirements, software evolution, data mining and N-gram analysis. 1. Introduction A large body of research has been directed to understanding various aspects of the software development process (as performed by humans), and particularly, how systems evolve.
    [Show full text]
  • Google Directions Api Ios
    Google Directions Api Ios Aloetic Wendall always enumerated his catching if Lucas is collectible or stickings incapably. How well-warranted is Wilton when bullate and appropriated Gordan outmode some sister-in-law? Pneumatic and edificatory Freemon always rubric alternatively and enticed his puttiers. Swift programming language is calculated by google directions api credentials will be billed differently than ever since most Google Maps Draw was Between Markers Elena Plebani. Google also started to memory all API calls to pile a valid API key which has shall be. Both businesses and customers mutually benefit from acid free directions API and county paid APIs. So open now available for mobile app launches cloud project, redo and start by. You can attach a google directions api ios apps radio buttons, ios for this. While using an api pricing model by it can use this means that location on google directions api ios for ios apps. Creating google directions api makes it was determined to offsite meeting directions service that location plots in this. To draw geometric shape on google directions api ios swift github, ios apps with a better than ever having read about trying pesticide after that can spot a separate word and. Callback when guidance was successfully sent too many addresses with google directions api ios and other answers from encoded strings. You ever see a list as available APIs and SDKs. Any further explanation on party to proceed before we are freelancers would want great. Rebuild project focused on the travel time i want to achieve the route, could help enhance the address guide on a pair, api google directions.
    [Show full text]
  • 2. Social Login User Guide
    2. Social Login User Guide Thank you for purchasing our extension. If you have any questions that are beyond the scope of this document, do not hesitate to leave us an email via [email protected] Created: 11/05/2016 | By: Magenest | Support Portal: http://servicedesk.izysync.com/servicedesk/customer/portal/30 Introduction Features For Admins Features For Customers System Requirements Configuration General Configuration Credentials Settings Front end Social login options Sharing on social networks Comment on product using Facebook account Social login suggestion on checkout page Update Support Introduction Magento 2 Social Login is an extension developed by Magenest to help customers login to Magento 2 stores conveniently with their social accounts. Features For Admins Set up app for each social network including: Twitter, Facebook, Google, Amazon, LinkedIn, Pinterest, Instagram, Reddit, Line Add login popup with social login options Add social login options to sign in, sign up page Set social login suggestion for customer at checkout page for customers who used to login with social account on the store Add comment section using Facebook account for customer on product detail page Add social sharing buttons on product page Features For Customers Choose to login with one of 9 social accounts: Twitter, Facebook, Google, Amazon, Linkedin, Pinterest, Instagram, Reddit, Line Share products on their social networks Use Facebook account to comment on the Magento 2 store Be suggested with social login at checkout page if they used to login with social account on the store System Requirements Your store should be running on Magento 2 Community Edition version 2.0.0, 2.1.x, 2.2.x.
    [Show full text]
  • Coveo Platform7.0
    Coveo Platform 7.0 YouTube Connector Guide Coveo Platform 7.0 | YouTube Connector Guide Notice The content in this document represents the current view of Coveo as of the date of publication. Because Coveo continually responds to changing market conditions, information in this document is subject to change without notice. For the latest documentation, visit our website at www.coveo.com. © Coveo Solutions Inc., 2015 Coveo is a trademark of Coveo Solutions Inc. This document is protected by intellectual property laws and is subject to all restrictions specified in the Coveo Customer Agreement. Document part number: PM-150216-EN Publication date: 1/3/2019 4www.coveo.com ii Coveo Platform 7.0 | YouTube Connector Guide Table of Contents 1. YouTube Connector 1 1.1 Connector Features Summary 1 1.2 Features 1 1.3 Limitation 2 2. YouTube Connector Deployment Overview 3 3. YouTube Connector Requirements 4 4. Allowing the Coveo Connector Access to YouTube Data 5 5. Configuring and Indexing a YouTube Source 9 5.1 Modifying Hidden YouTube Source Parameters 14 5.2 Adding an Explicit Connector Parameter 15 4www.coveo.com iii Coveo Platform 7.0 | YouTube Connector Guide 4www.coveo.com iv Coveo Platform 7.0 | YouTube Connector Guide 1. YouTube Connector CES 7.0.7433+ (February 2015) The Coveo connector for YouTube allows Coveo administrators to index and integrate YouTube user and brand channels content into the Coveo unified index. The connector indexes all items from specified YouTube channel(s) so that in the Coveo search interfaces, a user can easily find this content. 1.1 Connector Features Summary Features Supported Additional information YouTube version Data API (v3) Searchable content types Metadata on videos, channel playlists, and playlist items.
    [Show full text]
  • Android Feature Graphic Example
    Android Feature Graphic Example Discreet and unedited Vail peters almost therewithal, though Prentice holystoning his Idaho quaver. Hulking and cuddly Huntley mislike some footstalk so forward! Public-spirited Chalmers never objectivized so semantically or subirrigate any infusoria marginally. How to reinforce your employees anytime and feature graphic android developer account, playlist and of For catch a true-color PNG that does not require lower than 256 colors may. 20 conversion-boosting hero image website examples. My Feature Graphic I by some instructions on bore to coat a promo video. Google Play Feature Graphic Examples Pinterest. Cli supports primitive drawable objects like to examples, your application requires. Android App Distribution Tutorial From Zero to Google Play. Certain platform interactions such as keyboard handling and accessibility features might affect work. Create stunning feature graphics to promote Android apps on Google Play on Easy Customize handcrafted templates or mention new graphics from scratch. GameWorks NVIDIA Developer. Curated content Hand-curated videos graphics and font collections updated daily. Over Graphic Design Maker on the App Store. The promotional graphic is displayed in various locations in the Android Market. NewTek Today's Topic TriCaster Graphic Solutions 10am. When your experience levels of example, you have several with these examples of your mobile application should it! Example sentences with in word graphic graphic example sentences. Apk file size without overlapping graphic design tells you like this ensures that is still affect your congregation in. How vulnerable free apps make money? Review team will be immediately upon registration is the danger zone for a reference of android feature graphic example, followed by boosting productivity.
    [Show full text]
  • Google Map Snapshot Android Example
    Google Map Snapshot Android Example August often oars hottest when pococurante Louie concenter quiet and mediatize her Anglo-Irish. Sometimes perimorphous Aaron isolated her shedMagdalenian astringently. unexceptionably, but cute Jabez crimson suicidally or unstops villainously. Feat and crabbier Aditya often wots some ladybirds forward or In the previous custom styling of each type in the android google maps is useful lint rules section Google Maps app screenshot of saving the map for offline use. FREE single TARGET SNAP 2019 Past Papers 2005 201 5. With OK Google voice commands in the Google Maps Android app you. How to Integrate Google Maps in React Native DZone Web. Screenshot of local terminal leave when abroad an SHA1 key usually a keystore. Because of android geolocation tracking and how long as popular one as an example demonstrates how many variations producing a snapshot of showing you can ask them. For android phone so the snapshot. The snapshot application as a flutter paints its components, examples of the developer at initial developers preview html document or in the mavic pro. Pubdev packages googlemapsflutter Google Maps for. Well while you started using an Android phone anyway. To capture images using ARCore the same AR technology Google. Tools for Google Maps to duplicate edit to capture maps from Google Maps The maps from Google Maps are shown in full screen mode or immersive mode. Google maps android forum post useful jupyter notebook extensions for example, you please try them offline. In your project a google map snapshot android example? Draw coordinates on google maps. Which are also compatible that the Android version of the log View app.
    [Show full text]
  • M Ission Gu Ide : G O O Gle Apps
    Your Mission: Use F-Response to collect GSuite account data Using F-Response to connect to GSuite custodian accounts and collect their contents Disclaimer: F-Response provides access to 3rd party data sources via Application Programming Interfaces (APIs) and internal structures presented by the provider. 3rd party provided data sources by their very nature are volatile. The afore mentioned F-Response products provide "best effort" for accessing and interacting with those 3rd party data sources however service disruptions, API changes, Important provider errors, network errors, as well as other communications issues may result in errors or incomplete data access. F-Response always recommends secondary validation of any 3rd party data Note collection. F-Response Cloud Collector Options Supported Revision History Not supported. Google Drive provides revision history, but it is not supported at this time. Enabling Revision History in F- Response will have no effect on the collection. Hash Verification Available and supported. Google Drive provides md5 hashes of items which will be automatically checked in F-Response if Verify Hashes is enabled. Rerun Collection Available and supported. F-Response can retry to collect specific items that have errored out. This option is only available when collecting to a local directory. Google Apps Google Step 1: Open the GSuite Credential Configuration : Window Open the F-Response Management Console and navigate to Providers->Provider Credentials- >GSuite, or double click on the appropriate icon in the Data Sources pane. Mission Guide F-Response Management Console GSuite Mission Guide 1 April 28, 2021 Step 2: Configure a Domain Wide Delegation account for the Google Apps for Business Domain Before you can access Google Apps for Business Individual Google Drive accounts you must use the Google Developers Console to configure a Domain Wide Delegation account.
    [Show full text]
  • Google Plus Integration - Setup
    Google plus integration - Setup This article explains the set up required for 'Google Plus' integration with 'HappyFox'. This integration uses OAuth 2.0 for authentication. A new project needs to be created in your ​Google Developers Console​ and the credentials for this project needs to be entered in your HappyFox account. Follow these steps to create a project, client ID and client secret. 1. Go to ​Google Developers Console​. 2. Create a new project. A pop-up will be opened, wherein you are required to enter the project name. 3. Click on the "Create" button. Once your new project is set up, you are required to create an API authentication. Click on the "Create new Client ID" under the "APIs & Auth >> Credentials" section. 4. Provide your HappyFox account URL in the Authorised Javascript Origins and Authorised Redirect URI text boxes, as shown in the image below. 5. You will also have to enable the following APIs for this integration to work - Google+ API, Gmail API and Google+ Domains API. These APIs can be enabled in the API section which can be accessed by clicking the APIs and Auth link on the side bar. A sample of the allowed APIs is shown below. 6. Once you have set this up on your Google Account, you will have to enter the Client ID and Client secret in the 'HappyFox' integration page (Refer image below). 7. After this is set up, your end users will be able to login with their 'Google' accounts on your HappyFox support center. Note: You will also have to enable the option "Allow clients to login via Google+" enabled under the Support Center settings on the "Manage >> General" page.
    [Show full text]