eddyverbruggen/cordova-plugin-googleplus

1. This repository is a Cordova/PhoneGap plugin, not an app. Its job is to expose Google Sign-In to hybrid apps through a single JavaScript API while delegating platform-specific auth work to native code on iOS and Android.

2. The top-level integration point is plugin.xml. It defines the plugin metadata, which source files are installed per platform, and the variables the app must provide at install time, especially REVERSED_CLIENT_ID and WEB_APPLICATION_CLIENT_ID. That file is the central boundary between Cordova and the native implementations.

3. The JavaScript surface area lives in www/GooglePlus.js. This is the public plugin API consumed by Cordova apps via window.plugins.googleplus. It is the only code the host application calls directly; everything else is behind the Cordova bridge.

4. Native sign-in logic is split by platform under src/ios/GooglePlus.m/.h and src/android/GooglePlus.java. These are the real authentication adapters that talk to the Google SDKs, handle login/silent login/logout/disconnect, and translate SDK results into plain JS objects returned to the callback layer.

5. The data flow is consistent across platforms: app code calls the JS wrapper, Cordova forwards the request to the native side, the native SDK performs authentication, and the result is marshaled back as a JSON-like object containing profile fields plus optional idToken, serverAuthCode, and accessToken.

6. Browser support is implemented separately in src/browser/GooglePlusProxy.js. This is a Cordova proxy layer for the browser platform, meant to keep the plugin callable in non-native environments. It is part of the same API surface but does not use the iOS/Android SDKs.

7. There is also a simulation layer in src/simulation/, with sim-host.js and sim-host-handlers.js. This appears to provide a host-driven fake environment for testing or demoing plugin behavior without a real device auth flow, forming a separate non-production execution path.

8. Build-time behavior is customized with hooks. hooks/browser/after_prepare.js adjusts browser platform output after Cordova prepare, and hooks/ios/prerequisites.js plus hooks/ios/package.json support iOS dependency/setup handling. These hooks are important because they bridge the plugin into platform build systems rather than runtime auth.

9. The iOS side depends on CocoaPods, as called out in the README. That means the plugin is not fully self-contained on iOS: the Cordova plugin installs native code, but the final app build also needs Pods resolution for Google Sign-In libraries.

10. Android integration depends on Google Play Services and OAuth configuration rather than bundled credentials. The plugin code expects the app developer to provide the correct SHA-1 / client IDs, while the plugin itself focuses only on the sign-in flow and token retrieval.

11. The demo/ directory contains reference host apps for different Cordova stacks: plain Cordova, Cordova with Firebase, and Ionic 2. These demos are not part of the plugin runtime, but they illustrate the expected call pattern and serve as integration examples.

12. Overall architecture: a thin cross-platform JS API at the top, Cordova bridge and platform proxies in the middle, native Google Sign-In implementations at the bottom, and a small amount of build-time glue around the edges to wire in platform dependencies and configuration.