Gigya Job Openings

Mobile Support

Skip to end of metadata
Go to start of metadata


Gigya offers a range of out-of-the box features for powering your sites and apps on mobile devices for a seamless user experience and rich identity information all around. These include: 

  • Web Browsing: by default, all of Gigya's Screen-Sets, including those you customize using the UI Builder, are responsive and automatically optimized to fit the screen on which they are displayed. 
  • Native Apps: Gigya offers a host of Mobile SDKs for including our identity solutions in your mobile apps.


Mobile Web Browsing

By default, all RaaS screen-sets are responsive, resize to match the size of the device used and are optimized for mobile devices. This includes screens that are highly customized using the UI Builder. You only need to deploy once to receive registration, login and other screens that are perfectly adapted to the device being used. 



Adapted UI for Mobile View


The following plugins support mobile view mode:


  • When the Share Bar or Simple Share are set to deviceType mobile or auto (on mobile), clicking the email share will open the mail client rather than the Gigya Share / Share Bar UI. 
  • The rest of the plugins are displayed on the mobile device in their standard web design.


Enabling Mobile View Mode

To enable the mobile view mode, when calling the plugin method call, set the deviceType parameter to auto. For example:

var params =
     categoryID: 7623701,
     containerID: 'commentsDiv',
     deviceType: 'auto'


Gigya will identify the device (using user-agent) and if it is a mobile device, the plugin will be rendered in its mobile view mode.

For Gigya to automatically determine the device type using deviceType: 'auto'; you must also include the following meta tag in the <head> section of your site.

<meta name="viewport" content="width=device-width"> // This must be the first item beneath the document <title></title> of the <head> section of your page!

Handling Login on Mobile

When invoking login other than site login from a mobile device (e.g., Social Login, OpenID Connect), or any environment where pop-ups are unavailable or cross-window Javascript calls are limited, it is recommended to use the 'Redirect' authentication flow by passing the authFlow : 'redirect' parameter to the method that performs the login*.

The authFlow: 'redirect' parameter ensures that the login flow will complete without using cross-window scripting. To login, the user is redirected to the provider's authentication URL to perform authentication and then redirected back to the original page (or, if specified, to the URL provided to the redirectURL parameter).

When implementing the 'Redirect' login flow, it is important to note the following:

  • Logging in with authFlow= redirect from a screen-set does not redirect to the same state. This means that it is up to the partner to display the correct screen-set after login is successful.
  • * Any plugin that performs login can accept the authFlow parameter. For example, the following code will invoke the redirect flow on login:

    var params =
         screenSet: 'my-screenSet',
         authFlow: 'redirect'

Native Apps

The Mobile SDKs for AndroidiOS, and Cordova provide an interface for the Gigya API. The library makes it simple to integrate Gigya's service in your mobile application.

The SDKs provide access to Gigya's core API, while providing mobile UIs for RaaS Screen-SetsSocial LoginAdding Connections to Social NetworksCommentsRatings and Reviews, and Share Bar. Additionally, data for all of Gigya's plugins (except Reactions) can be retrieved via the REST API, enabling you to create your own custom UI's to fit with your native application.

Learn how to implement our SDKs in the dedicated guides for AndroidiOS, and Cordova.

Key Implementation Points

The mobile application (that uses a Mobile SDK) is a client-side application. Therefore the following client-side rules apply: 

  • Proper security measures should be taken. Please do not use your Gigya Secret Key in your mobile application. The Secret Key should only be used in server-server calls and should never be passed to the client-side application. For more information on how and where to set up your secret key, see the relevant section for AndroidiOS, or Cordova.
  • You can only make API calls on behalf of the currently logged-in user.
  • The mobile SDK stores login session information in a Gigya session object which is managed by the SDK. This is unlike our Web SDK which stores login session information in a cookie.