Wir helfen Unternehmen seit 18 Jahren,
bessere Software zu finden
RevenueCat
Was ist RevenueCat?
Mit RevenueCat kannst du auf einfache Weise plattformübergreifende In-App-Abonnements erstellen, deine Produkte und Kunden verwalten und deine IAP-Daten analysieren. Kein Servercode erforderlich.
Wer verwendet RevenueCat?
Mobile Anwendungen
Du bist nicht sicher, ob RevenueCat das Richtige ist?
Mit einer beliebten Alternative vergleichen
RevenueCat
Weitere gute Alternativen zu RevenueCat
Bewertungen über RevenueCat
Using RevenueCat server from app inception to release to the App Store
Kommentare:
The integration is stable. Once coded, I seldom need to revisit it.
So, it's now a seamless experience for my users and the app
Vorteile:
The integration mechanism into swift code base is detailed in RevenueCat docs. This made it possible to successfully integrate it. It is very helpful that testing in the sandbox is possible using a sandbox user
Nachteile:
The concepts of Entitlements, Offerings, Products is difficult to memorize. It's good that RevenueCat has readily available detailed documentation to cover these concepts
Simple Solution for In-App Subscriptions
Kommentare: We turned to RevenueCat because of the hassle that exists trying to verify purchases manually. Doing this ourselves would mean setting up a server, handling all the different cases across the App Store and Play Store, and making sure this server is maintained and always live. For a small team like ours, this just wasn't viable and any potential money "saved" doing it ourselves would be lost in the time we would spend setting up our own solution. That would also mean extra time before an app can be released which would increase our time to market. RevenueCat handled everything we needed it to and took about a week to fully integrate.
Vorteile:
RevenueCat made it really easy for us to implement In-App Subscriptions for our app with absolutely no prior experience in taking payments on mobile devices. It saved us the upfront cost of paying for our own server to verify purchases along with the potential months of headache to handle all of the different scenarios you need to plan for and handle with in-app purchases (buying, renewing, pausing, canceling, etc.) Being able to pull information directly from RevenueCat instead of hard-coding it into our app also meant we could have a single source of truth (the App Store/Google Play Store) where we would update our available products.
Nachteile:
The only thing I wasn't a fan of (which has since been changed) was the payment model. When we first integrated it, the payment model was a fixed monthly rate versus the percentage cut that it is now. Extremely useful features like webhooks weren't accessible for us at the time because of this, but as I stated they've now changed this. Because of that, I cannot name anything I dislike about RevenueCat.
Great idea, terrible execution and terrible support
Kommentare: It takes a lot for me to leave a bad review. RevenueCat is a great idea, but poorly executed. The documentation is scatty, their API is inconsistent, there has been 2 sets of downtime since I signed up and the level of support from RevenueCat is absolutely unacceptable. For a company that takes a 1% cut of your revenue forever—potentially up to thousands of dollars per month—this is beyond ridiculous. 5-10 business days for an email response? If I’m lucky, maybe 2-3 days. Their documentation is a joke, basically saying to try the obvious and failing that “Go ask someone else on the forums” And their forums? Just a graveyard of unanswered posts with people begging for updates. I’ve been stuck trying to fix Android issues for over a week. I’m confident my setup is correct, but still, nothing works. Getting any kind of timely help from RevenueCat is like pulling teeth. I even wasted time in one of their Q&A sessions on the recommendation of their support team, which was nothing more than a shameless product pitch. Their exact words: “We aren’t answering implementation questions today.” despite half of the people on the session voting for implementation help. It’s clear to me that RevenueCat doesn’t prioritise supporting their customers. Their strategy is obvious—sign up as many people as possible, then leave them hanging. When our success is literally their success, how can they justify this level of neglect? It’s infuriating.
Vorteile:
I like the idea of it, and the fact that it could consolidate.your monetisation strategy. (When it works correctly)
Nachteile:
The support is terrible, the documentation is terrible.
Best service for in-app purchases
Kommentare: Really happy with it, I like their documentations and the ease of use
Vorteile:
The simplicity to setup in-app purchases for mobile apps and the pricing
Nachteile:
Really I don't know what to say here. Maybe the cheaper plan could have a bit more features?
I Need RevenueCat
Kommentare: Over all I am 100% happy. I can continue to be happy when you keep iterating as we all must in the subscription world.
Vorteile:
I have to chose 1 thing? I can't. 1. I love how you built this for hardworking app developers. You saw the unmet need and you filled it with love. 2. I love your response from your team when I have a question or problem. 3. I love how you offer a very affordable service and when we want more features you hook us so we have to pay more but we like it ;)
Nachteile:
Better communication with Apple when we update our price of subscription. Have that reflect on our charts side.
