Android monetization

User pays you to use your app

Pro: You make more Con: People don't like paying

You don't need to write any code; you just specify when you upload the APK file to the Google app site how much the app costs.

Google takes about 30% of a cut.

Adds

Docs on how to show Adds, such as a banner

In-app billing

Much more complex than the other two options

• You set up a billing site
• You need to check if the user has payed for this thing before
• You have to launch a billing flow, so the user can actually buy the thing.

Use the Google Play Billing Library

Use something else as a payment processor

Stripe

• Used for many different things (ie, a wedding registry)
• Stripe takes 30 cents plus 2.8% for each transaction
• Can only be used for physical goods or services.
• Handles web, iOS, Android very well
• hardest part is that it requires a server or cloud function for making the final payment request.
• Has good docs.

Frontend - Stripe - Server relationship

Front end takes credit card info and sends it to Stripe. Stripe takes the CC info, stores it in its servers, and sends back a token that represents that credit card info to the frontend. The frontend takes that token and sends it along to your server. Your server talks to Stripe servers, to tell Stripe servers to charge money. Stripe responds with success/failure. Your server then tells your frontend if there was success or failure.