-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Web support #128
Comments
This is not possible as there is no access to the Play Games or Game Center SDKs via web. |
I think for web we can use Google play game services Rest API, or any other wildly used service if there is any. I'll do some research and see, and if someone knows a good one that will be good. |
Maybe this helps google/googleapis.dart#583 |
According to the docs, the REST API is intended for server side access for an Android client. That is not to say that a solution couldn't possibly be built around it, using the API & GoogleSignIn but it may violate the TOS. Plus, it would only be available for Google Play Games users, which could be a downside. I would suggest people wanting web game achievements use a backend like nakama or roll a leaderboard/achievement system with Firebase or a similar service. Then you can allow sign in with various auth providers, with no risk of alienating an audience. |
As they mentioned, Google Play Games is also available now for PC. Why would it violate the TOS? |
Google Play Games on PC is uses virtualization to play Android Games on PC via some degree of Android emulation. It was implemented to compete with macOS's ability to play iOS games (only available on Apple silicon). You are still playing an Android game with access to the Android Play Games SDK if implemented.
UPDATE: After digging around, it is incorrect to say that Google Play Games support on the web is not possible. However, it still requires the implementation of server side calls to PGS. Therefore, I do believe it is outside of the scope of this package. |
Is this possible? If so, any plans to add it in the future?
The text was updated successfully, but these errors were encountered: