Item: Paddle
Rating: 8
Author: Andrew Liakh

Overall Satisfaction with Paddle

Use Cases and Deployment Scope

We use Paddle in our browser extensions to provide in-app purchase functionality. We also use Paddle and DevMate integration to sell licenses for our macOS application. It handles trials, as well as blocking the app usage if the user didn’t provide a license. We also use Paddle for in-app analytics for our Mac App Store app to collect user behavior data.

Pros and Cons

Pros

macOS application licensing/trials
JavaScript-based purchase page for web
Webhooks

Cons

Paddle support can be better
Paddle documentation lacks some important information
Mac analytics is very basic and limited

Return on Investment

Paddle takes only 5% of sales, in comparison to 30% as Apple does.
We added browser extension in-app purchases thanks to Paddle, which now generate our revenue.

Alternatives Considered

Stripe

We tried using Stripe before Paddle, but it was a pain integrating it and it lacked the licensing. Paddle allows us just to add a payment button and don’t ever think about payment methods, we don’t have to make a separate button for card payments and another one for PayPal. Paddle does all this in their checkout process.

Likelihood to Recommend

Paddle is perfect if you want to sell your macOS app from your website. It’s also very good if you want to provide in-app purchases in your web application or browser extension. It’s easy to integrate and the integration rarely needs any changes. It won’t be as good for e-commerce.

Paddle Feature Ratings

Comments

Please log in to join the conversation

Great for macOS and browser extensions