Skip to content
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

Create Java sample to showcase implementing Play Billing without a server #278

Closed
calren opened this issue Mar 5, 2020 · 5 comments
Closed

Comments

@calren
Copy link
Contributor

calren commented Mar 5, 2020

Currently we have the following samples:

ClassyTaxi showcases all the best practices we recommend when working with Play Billing, including having a server to validate purchases.

TrivialDriveKotlin, on the other hand, is an example of integrating Play Billing without a server. Based on some feedback, it seems like some developers would like to see a Java sample that showcases Play Billing without a server implementation. While we highly recommend you include a server solution with your Play Billing features, we understand that not all developers have the necessary bandwidth or need for a server solution.

This issue is to track feedback about what people would like to see in a potential Java sample that integrates Play Billing without a server. Requests could be something like:

  • I would like to see how to use the latest version of the Play Billing library if my app doesn't have a server
  • I would like to see how to best architect an app when integrating the Play Billing library
  • I would like to see how to implement {x} feature with the Play Billing library.

If you would simply like to see a Java version of TrivialDriveKotlin, you can also react to this issue with a 'thumbs up' emoji.

@DontTrustMicrosoft-MicrosoftIsAsshole

2 years later nothing. I wonder how much money Google lost on people that just said f*** it I'm not playing this "game" anymore, stopped coding all together and started a farm somewhere...The idea is growing on me more and more. Maybe that's what Google wants. Obviously it was a political not a logical change 🐄.🐄.🐄

@LordByron1788
Copy link

2 years later nothing. I wonder how much money Google lost on people that just said f*** it I'm not playing this "game" anymore, stopped coding all together and started a farm somewhere...The idea is growing on me more and more. Maybe that's what Google wants. Obviously it was a political not a logical change 🐄.🐄.🐄

Billing on Android is horrendous, and so is this repo. It has gone downhill completely this year. No progress is being made on anything, it is beyond a joke. Google stopped caring a long time ago. I guess free lunches and ping pong is all they do over at Google HQ.

@snoutholder
Copy link

I use serverless purchases with java and now Google Play is forcing me to update my purchase library, yet not providing me with a simple path with a working sample. I'm just trying to maintain my code. Where is the sample for trivialdrive java? I don't want to use subscriptions, so the existing java one is not adequate. And I don't want to hack something together using the bits and pieces provided by Google's migration.

@LordByron1788
Copy link

I use serverless purchases with java and now Google Play is forcing me to update my purchase library, yet not providing me with a simple path with a working sample. I'm just trying to maintain my code. Where is the sample for trivialdrive java? I don't want to use subscriptions, so the existing java one is not adequate. And I don't want to hack something together using the bits and pieces provided by Google's migration.

It's ridiculous, over 1 year ago this was logged, with 35 thumbs up over 2 issues, and still nothing.

If Google can't even deliver a sample in 1 year, then that should tell you everything you need to know about how good the Billing Library is. Not even Google developers can work with it. Either that or it's the developers that are at fault.

All we get are a couple of useless Medium articles on Billing.

If the original problem in #260 had been understood from the outset, then this issue #278 wouldn't have been raised.

@DAGalpin
Copy link
Contributor

DAGalpin commented May 3, 2021

TrivialDriveJava implemented, along with an update to TrivialDriveKotlin.

@DAGalpin DAGalpin closed this as completed May 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants