cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Disadvantages of the Web-Bridge Mobile Integration

tbaum93
Explorer
0 Kudos
976

Hi all!

Our Customer wants to keep the mobile integration as low as possible. When I introduced them the Web-Bridge and Plugin View, I found no disadvantages of the Web-Bridge version (except of course that you have to provide a hosted URL). Also in the training documents and on the developer side nothing else is defined.

Are there more disadvantages with Web-Bridge mobile Integration than the plugin view version?

Best

Tim

Accepted Solutions (0)

Answers (2)

Answers (2)

Hi Tim,

Please notice that our latest mobile SDK versions, Swift SDK for iOS and Android SDK v4, do not support the WebBridge approach. Therefore, if this is a new implementation, you should advise the customer to use the latest SDKs and to implement CDC Registration-As-a-Service with the PluginView approach.

https://developers.gigya.com/display/GD/Swift+SDK

https://developers.gigya.com/display/GD/Android+SDK+v4

I hope this helps.

Alejandro

Former Member
0 Kudos

Thanks for providing the web bridge. In Swift, what are the corollaries to these previous GSWebBridge Objective-C calls?

registerWebView -> attachTo ?
handleRequest -> ??
webViewDidStartLoad -> ??

Thanks for any help,
John

former_member629536
Participant

Hi Tim,

Web-Bridge/ plugin view implementations can not match the performance and responsiveness of a native application.

If these are key attributes required for the app, then you may want to reconsider the Web-Bridge approach.

Also when implementing the Web-Bridge it's important to note, you are required to install google and facebook mobile SDKs in your App. For example, as of April 2017, Google has blocked OAuth authorisation requests via web views. Please see the blog post from google

https://developers.googleblog.com/2016/08/modernizing-oauth-interactions-in-native-apps.html

regards
Ibrahim