After the recent changes to Google Sign In's web SDK (Blog post), it has become somewhat clear that Google's Authentication and Authorization flows seem to be specializing on a per-platform level, to offer the best, most natural, experience on each platform.

In the web, for example, Authentication and Authorization have just been completely separated from each other while mobile is able to retrieve all authentication and authorization tokens at once, the OneTap experience exists for Android and Web, but not iOS, and many other little differences that make our unified APIs much harder to design, build and maintain.

It is very likely that eventually, we'll need to restructure this plugin as one that lets users have more control over the underlying APIs, rather than trying to hide that complexity under a common (minimal) API.

What does this mean for google_sign_in? What does the next generation of the plugin look like? How can we preserve a good developer experience, even when users need to use platform-specific code?