RevenueCat
Auto Added by WPeMatico
Auto Added by WPeMatico
If you’ve ever bought a subscription inside an iOS app and later decided you wanted to cancel, upgrade or downgrade, or ask for a refund, you may have had trouble figuring out how to go about making that request or change. Some people today still believe that they can stop their subscription charges simply by deleting an app from their iPhone. Others may dig around unsuccessfully inside their iPhone’s Settings or on the App Store to try to find out how to ask for a refund. With the updates Apple announced in StoreKit 2 during its Worldwide Developers Conference this week, things may start to get a little easier for app customers.
StoreKit is Apple’s developer framework for managing in-app purchases — an area that’s become more complex in recent years, as apps have transitioned from offering one-time purchases to ongoing subscriptions with different tiers, lengths and feature sets.
Image Credits: Apple
Currently, users who want to manage or cancel subscriptions can do so from the App Store or their iPhone Settings. But some don’t realize the path to this section from Settings starts by tapping on your Apple ID (your name and profile photo at the top of the screen). They may also get frustrated if they’re not familiar with how to navigate their Settings or the App Store.
Meanwhile, there are a variety of ways users can request refunds on their in-app subscriptions. They can dig in their inbox for their receipt from Apple, then click the “Report a Problem” link it includes to request a refund when something went wrong. This could be useful in scenarios where you’ve bought a subscription by mistake (or your kid has!), or where the promised features didn’t work as intended.
Apple also provides a dedicated website where users can directly request refunds for apps or content. (When you Google for something like “request a refund apple” or similar queries, a page that explains the process typically comes up at the top of the search results.)
Still, many users aren’t technically savvy. For them, the easiest way to manage subscriptions or ask for refunds would be to do so from within the app itself. For this reason, many conscientious app developers tend to include links to point customers to Apple’s pages for subscription management or refunds inside their apps.
But StoreKit 2 is introducing new tools that will allow developers to implement these sort of features more easily.
One new tool is a Manage subscriptions API, which lets an app developer display the manage subscriptions page for their customer directly inside their app — without redirecting the customer to the App Store. Optionally, developers can choose to display a “Save Offer” screen to present the customer with a discount of some kind to keep them from cancelling, or it could display an exit survey so you can ask the customer why they decided to end their subscription.
When implemented, the customer will be able to view a screen inside the app that looks just like the one they’d visit in the App Store to cancel or change a subscription. After canceling, they’ll be shown a confirmation screen with the cancellation details and the service expiration date.
If the customer wants to request a refund, a new Refund request API will allow the customer to begin their refund request directly in the app itself — again, without being redirected to the App Store or other website. On the screen that displays, the customer can select for which item they want a refund and check the reason why they’re making the request. Apple handles the refund process and will send either an approval or refund declined notification back to the developer’s server.
However, some developers argue that the changes don’t go far enough. They want to be in charge of managing customer subscriptions and handling refunds themselves, through programmatic means. Plus, Apple can take up to 48 hours for the customer to receive an update on their refund request, which can be confusing.
“They’ve made the process a bit smoother, but developers still can’t initiate refunds or cancellations themselves,” notes RevenueCat CEO Jacob Eiting, whose company provides tools to app developers to manage their in-app purchases. “It’s a step in the right direction, but could actually lead to more confusion between developers and consumers about who is responsible for issuing refunds.”
In other words, because the forms are now going to be more accessible from inside the app, the customer may believe the developer is handling the refund process when, really, Apple continues to do so.
Some developers pointed out that there are other scenarios this process doesn’t address. For example, if the customer has already uninstalled the app or no longer has the device in question, they’ll still need to be directed to other means of asking for refunds, just as before.
For consumers, though, subscription management tools like this mean more developers may begin to put buttons to manage subscriptions and ask for refunds directly inside their app, which is a better experience. In time, as customers learn they can more easily use the app and manage subscriptions, app developers may see better customer retention, higher engagement, and better App Store reviews, notes Apple.
The StoreKit 2 changes weren’t limited to APIs for managing subscriptions and refunds.
Developers will also gain access to a new Invoice Lookup API that allows them to look up the in-app purchases for the customer, validate their invoice and identify any problems with the purchase — for example, if there were any refunds already provided by the App Store.
A new Refunded Purchases API will allow developers to look up all the refunds for the customer.
A new Renewal Extension API will allow developers to extend the renewal data for paid, active subscriptions in the case of an outage — like when dealing with customer support issues when a streaming service went down, for example. This API lets developers extend the subscription up to twice per calendar year, each up to 90 days in the future.
And finally, a new Consumption API will allow developers to share information about a customer’s in-app purchase with the App Store. In most cases, customers begin consuming content soon after purchase — information that’s helpful in the refund decision process. The API will allow the App Store to see if the user consumed the in-app purchase partially, fully, or not at all.
Another change will help customers when they reinstall apps or download them on new devices. Before, users would have to manually “restore purchases” to sync the status of the completed transactions back to that newly downloaded or reinstalled app. Now, that information will be automatically fetched by StoreKit 2 so the apps are immediately up-to-date with whatever it is the user paid for.
While, overall, the changes make for a significant update to the StoreKit framework, Apple’s hesitancy to allow developers more control over their own subscription-based customers speaks, in part, to how much it wants to control in-app purchases. This is perhaps because it got burned in the past when it tried allowing developers to manage their own refunds.
As The Verge noted last month while the Epic Games-Apple antitrust trial was underway, Apple had once provided Hulu will access to a subscription API, then discovered Hulu had been offering a way to automatically cancel subscriptions made through the App Store when customers wanted to upgrade to higher-priced subscription plans. Apple realized it needed to take action to protect against this misuse of the API, and Hulu later lost access. It has not since made that API more broadly available.
On the flip side, having Apple, not the developers, in charge of subscription management and refunds means Apple takes on the responsibilities around preventing fraud — including fraud perpetrated by both customers and developers alike. Customers may also prefer that there’s one single place to go for managing their subscription billing: Apple. They may not want to have to deal with each developer individually, as their experience would end up being inconsistent.
These changes matter because subscription revenue contributes to a sizable amount of Apple’s lucrative App Store business. Ahead of WWDC 21, Apple reported the sale of digital goods and services on the App Store grew to $86 billion in 2020, up 40% over the the year prior. Earlier this year, Apple said it paid out more than $200 billion to developers since the App Store launched in 2008.
Powered by WPeMatico
RevenueCat, a startup offering a series of tools for developers of subscription-based apps, has raised $40 million in Series B funding, valuing its business at $300 million, post-money. Founded by developers who understood the difficulties in scaling a subscription app firsthand, RevenueCat’s software development kit (SDK) solution gives companies the tools they need to build a subscription business, including not just adding subscriptions themselves, but maintaining them over time even as the app stores implement changes. It also aids by sharing subscription data with other tools the business uses, like those for advertising, analytics or attribution.
The funding round was led by Y Combinator’s Continuity Fund and included participation from Index Ventures, SaaStr, Oakhouse, Adjacent and FundersClub, as well as Blinklist CTO Tobias Balling and Algolia CEO Nicolas Dessaigne. With the round, YC Continuity Partner Anu Hariharan is joining RevenueCat’s board, which today includes Index’s Mark Fiorentino in addition to the founders.
Explains RevenueCat CEO Jacob Eiting, the idea for the company came about after he and co-founder Miguel Carranza Guisado (CTO) struggled to figure out subscription infrastructure while working together at Elevate. After years of untangling a “subscription mess” in order to figure out answers to basic questions like subscriber retention and lifetime value, they realized there was potential in helping solve this problem for other developers.
Apple and Google, Eiting explains, aren’t always up to date with what companies actually need to build subscription businesses. “They’re kind of learning as they go. They just weren’t able to provide us the data we needed, and then also the infrastructure to do that is non-trivial.”
Image Credits: RevenueCat
When Eiting and Guisado sat down to work on RevenueCat in 2017, no one else was even building anything like this. But the demand for the startup’s tools and integrations soon resonated with developers who had faced similar challenges in the growing subsection app market.
Using the service, developers can access a real-time dashboard that display key metrics, like subscription revenue, churn, LTV (lifetime value), subscriber numbers, conversions and more. The data can then be shared through integrations with other tools and services, like Adjust, Amplitude, Apple Search Ads, AppsFlyer, Branch, Facebook Ads, Google Cloud Intercom, Mixpanel, Segment and several others.
After launching out of Y Combinator’s accelerator the following year, RevenueCat was soon live with 100 apps and had crossed $1 million in tracked revenue by the time it raised its $1.5 million seed round.
Today, RevenueCat has more than 6,000 apps live on its platform, with over $1 billion in tracked subscription revenue being managed by its tools. That’s double the number of apps that were using its service as of its $15 million Series A last August.
With the additional funding, the company will lower its pricing to put its tools in reach of more developers. Previously, it charged $120 per month for its charts and some of its integrations, or $499 per month for access to all integrations. This was affordable for larger companies, but could still be a difficult sell to the long tail of app developers where revenues ranged from $10K to $50K per month.
Now, RevenueCat will charge a small percentage of an app’s sales instead of a flat fee. Developers with up to $10,000 in monthly tracked revenue (MTR) can get started with the service for free and as their demands grow — like needing access to charts, support for web hooks, integrations and others — they can move up to either the Starter or Pro plans as $8/mo or $12/mo per $1,000 in MTR, respectively.
“I’m excited to give those tools to developers, especially on the small end, because it might be what they need to get out of that ‘less than $10K range,’ ” Eiting says. “Also, the beauty of freemium, or having a really generous free tier, is that it makes your tool the de facto — you remove as much friction as possible for providing software services and then, if you get your pricing right — which I think we have — it all kind of pays for itself,” he adds.
The company also plans to use the new funds to further invest in its business, expanding from App Store and Google Play support to include Amazon’s Appstore. It will also grow its team.
As part of its expected growth, RevenueCat recently hired a head of Product, Jens-Fabian Goetzmann, previously a PM at Microsoft and then product head at fitness app 8fit. Currently 30 people, in the year ahead, RevenueCat will grow to 60 people, hiring across design, product, engineering, sales and other roles.
“The world is moving toward subscriptions — and for companies, building out this model translates to weeks of developers’ time,” says YC Continuity’s Hariharan. “RevenueCat helps developers roll out subscriptions in minutes and creates a source of truth for customer data. With developers creating solutions to problems in the world, it’s important that they can find ways to monetize, grow, and support their most committed customers. RevenueCat is doing so by building subscriptions 2.0.”
Powered by WPeMatico
RevenueCat, a startup that helps developers manage their in-app subscriptions, has raised $1.5 million in new funding.
The company was part of the most recent batch at Y Combinator, and CEO Jacob Eiting said growth has been “a rocket ship” for the past few months. As of this week, RevenueCat is working with 100 live apps, and it’s crossing $1 million in tracked revenue.
The startup offers an API to address what sounds like a straightforward task, supporting in-app subscriptions in iOS and Android. As Eiting put it when I first interviewed him a few months ago, it’s “boring work” solving a “boring problem” — but that’s one of the reasons why developers don’t want to deal with it. It also means they don’t have to spend time dealing with bugs and updates on the subscription side of either platform.
And RevenueCat continues to add new features, like allowing developers to bring their revenue data into analytics and attribution services. That, in turn, makes it easier for them to see which ads are driving real revenue.
The long-term goal is to build what Eiting (who’s pictured above with his co-founder Miguel Carranza) calls a “revenue management platform.”
“Our mission as a company is to help developers make more money,” he said. “I think we do become this one-stop shop, a service that you integrate with all the payment touch points in your app to help you track your revenue and help you understand how customers are spending.”
The new funding (which is on top of the $120,000 RevenueCat received from YC) was led by Jason Lemkin of SaaStr. Eiting said it’s “an obvious fit,” since the software-as-a-service entrepreneurs who read SaaStr articles, listen to its podcasts and attend its events form “this huge community of companies that are potential customers for us.”
Powered by WPeMatico
Startup founders don’t usually pitch their ideas by admitting that they’re fixing something “boring,” but it seems to work for RevenueCat‘s Jacob Eiting.
In fact, Eiting alternately described his startup (which is part of the current class at accelerator Y Combinator) as handling “boring work” and solving a “boring problem.” RevenueCat helps developers manage their in-app subscriptions, which Eiting said “is just boring — developers don’t want to do it.”
And yet it can be crucial for their business. After all, Eiting and his co-founder Miguel Carranza both worked at brain training app Elevate (where Eiting was CTO and Carranza was director of engineering), and he said shifting Elevate’s business model from one-off purchases to recurring subscriptions “saved the company.”
Eiting left Elevate more than a year ago, ultimately deciding to build a startup around “this weird skill I have.” RevenueCat offers an API that developers can use to support in-app subscriptions on iOS and Android, which means they don’t have to worry about all the nuances, bugs and updates in the way each platform handles subscriptions.
Eiting said this is the kind of thing that “holds a lot of companies back — maybe not forever, but it’s usually at a time when a company shouldn’t be worrying about this.”

The API also allows developers to bring all the data about their subscription business together in one place, across platforms. Ultimately, he wants to turn RevenueCat into a broader “revenue management platform,” allowing developers to try out strategies like offering different prices to different customer segments.
More broadly, Eiting suggested that subscriptions offer a way out of the current “race to the bottom in how software is sold” — particularly in mobile app stores, where many of us expect everything to be free or dirt cheap. Obviously, that’s not a great situation for someone hoping to make money by selling software, but Eiting pointed out that it can be bad for the consumer too, because it means the developer has less reason to support and update the app.
“Someone who pays for your 99-cent app once, they think they own your time,” he said. “You want to be helpful, you don’t want to let down a paid user, but your incentives aren’t really aligned.”
Subscriptions, even if they’re just for 99 cents a month, can re-align those incentives — Eiting has described this as a system of app patronage: “You want this thing to stay working, you need to pony up some money to developers.”
He also acknowledged that as more apps shift to this model, there’s a risk of subscription fatigue, which could lead to “maybe not a harsh backlash, but there might be a secondary correction.”
But in Eiting’s view, that’s less a problem for individual developers and more for the mobile platforms. Those platforms, he said, should be building better tools for consumers to manage all their subscriptions in one place.
Powered by WPeMatico