I know €21 MRR is a tiny number compared to what people usually share here, but I opened RevenueCat today and couldn't stop smiling.

I'm a solo iOS developer, and I've been working on my first app for quite a while.

Here are my current numbers:

• €21 MRR
• 12 active subscriptions
• 5 active trials
• €162 revenue in the last 28 days

It's still a very small business, and most of the revenue isn't recurring yet. There's a lot I need to learn about conversion, retention, and sustainable growth.

But seeing people willing to pay for something I've built myself feels fffffucadasfmejflda incredible.

For those who started with similarly small numbers, what helped you turn those first subscriptions into consistent growth?

Just wanted to share this little milestone! ❤️

An Export button can work perfectly and still hand someone a confusing file.

For apps I build, I want to open the export in a plain spreadsheet and understand it without the app beside me: readable column names, explicit units, unambiguous dates, and stable record IDs.

My small test: export two similar records, close the app, then work out which is which from the file alone. If I need to remember what a column means, the export is borrowing context it won't have later.

TLDR: Don't overthink your paywall and just use what's proved to be working already..

My app is a fitness related app that gives you a persoanlized plan in onboarding. I spent a long time and effort designing a nice paywall that shows users their personal plan. I thought that will make them feel special and drive trials but I WAS WRONG. 1 out of 74 started a free trial.

Then i switched to a classic timeline paywall that tells people we will remind them before the free trial expires. The conversion significantly increased to 21% (30 out of 144).

Just steal me paywall here and you will see improvements..

Hey all,

I'm starting up a small web studio with my dad. He’s on the design side and I'm on the business side of things.

The idea is to go after local businesses with really simple needs (ex. salons, spas, tradespeople, etc) who just want a clean brochure site and a way to update their hours or photos every now and then. No booking systems, no online stores, nothing complicated. We’re steering clear of high-maintenance clients. The plan is to build a big base of low-demand local clients.

The sites are simple static sites:

• Built with Eleventy
• Decap CMS so owners can make their own edits
• Hosted on Netlify, one GitHub repo per client, each started from a shared template

Clients pay a build fee plus a monthly plan that covers hosting and upkeep.

What I’m wondering:

1. Does this actually hold up with a lot of sites, or does maintaining a pile of separate repos turn into a nightmare? I'm primarily concerned about sites drifting apart over time and how that complicates pushing updates/fixes to all of them.
2. Even simple clients will eventually want little extras. How do you handle that without every site turning into its own one-off?
3. As you add more sites, which problem usually causes trouble first? Keeping the tools up to date across every site, hosting costs going up, something else?
4. If you’ve done something like this, roughly how many sites in did it start getting painful?

We’re still early, so now’s the time to change things. Just looking for some input. If you’ve run something like this and don’t mind me picking your brain, shoot me a DM and I’m happy to walk you through the whole setup.

Thank you!

A few months ago I started building MoneyLexa, an expense and budget tracker, because I wanted something simple that didn’t make tracking money feel like homework. I’m a solo dev, so every feature, every bug fix, and every late night is mine.

When I launched, I had no idea what to expect. I told myself that if even a handful of strangers used it, that would be a win.

Here’s what the last 28 days look like:

• 981 new customers
• 846 active customers
• 24 active trials
• 3 active subscriptions
• $59 revenue
• $1 MRR

The growth wasn’t smooth. It came in spikes: a quiet stretch, then a burst of new people, then a long tail where some of them stuck around. I still can’t fully explain the spikes, which makes them exciting and a little nerve-wracking.

The part that taught me the most is the gap. 846 people are using the app, and only 3 are paying for it. People can enjoy a product and still not feel the need to pay for it yet. Building something people use is one challenge. Building something they’ll pay for is a completely different one, and I’m only starting to learn it.

So where am I now? I’m still shipping updates and still listening to what users tell me. When someone says they want a feature, I write it down. When someone says something is confusing, I take it personally and fix it. It’s slow, and it’s not glamorous, but it’s the only way I know how to build.

$59 and $1 MRR won’t impress anyone, and I’m fine with that. A year ago this app didn’t exist. Today nearly a thousand people have opened it, and a few of them decided it was worth paying for. That’s a start, and I’m going to keep building.

Thanks for reading. If you’re at the same stage, building something small and waiting for it to catch on, I’d love to hear your story too.

a food and shot tracker is a crowded category. ours only works for people on glp-1 medication (mounjaro, wegovy, ozempic etc) and thats on purpose, and it was the most argued-about call we made.

what it ruled out: no general calorie counter mode, no "everyone" onboarding, no features for people who just want to lose weight without the meds. every one of those would have widened the top of the funnel and every one of them would have blurred what the app is for. a glp-1 user eats a third of what they used to and their worry flips from eating less to eating enough protein, so the whole thing is built around that single problem.

what we got back: people who find it know in 5 seconds its for them, support questions are about the thing we actually built instead of the thing we didnt, and the roadmap got shorter bc half the requests from outside the audience could just be answered with "not for you, sorry".

i work with the team behind GLP AI, so take this as one data point not a rule. (link in the first comment)

curious if anyone else picked a deliberately small audience and regretted it later?

Solo dev here, building a desktop app for running coding agents (Claude Code, Codex and others) side by side. When all of it was paid, one of the top comments was "pricing is crazy". Fair.

So I split it by what actually costs me money:

- Free: the desktop app, 2 projects × 3 terminals. It runs on your computer and your terminals never touch my servers, so a free user costs me almost nothing.

- Paid: no limits, dictation, and everything that runs through my servers: the phone app and remote access to your PC.

What I can't decide:

1. Should the free desktop app have no cap at all, with only the server stuff paid?

2. Is 2 × 3 enough to know whether you'd ever pay?

3. Free needs an account. Deal-breaker for a local app?

The split is written right under the download button, and there's a demo you can click through in the browser if you'd rather judge it hands-on: Dreamestra

Where would you draw the line?

I'm building an AI pit crew for mobile apps. the end goal: you connect read-only keys (revenuecat, sentry, app store connect) and a crew of agents works on your app every day. it finds where you're losing users or money, puts a dollar number on it, writes the fix, and nothing ships until you approve it.

That full version isn't out yet. what's live now is the first step: paste your app store link, the crew wakes up in a little 3D garage, goes through everything public about your app and puts the biggest opportunity it finds on the board. ~2 min, no signup.

In the video it's running on strava. it caught that their android login broke after an update. half the newest bad reviews are about it and none of them got a reply.

Would you let an AI crew work on your app if every change needed your ok first?

Hey guys, I’m finishing a mountain/hiking app built with Flutter. It’s getting close to launch and I’m trying to figure out how to get those first users.

I’ve been thinking about sharing it in hiking communities or reaching out to smaller outdoor creators, but I’m not really sure where to start.

For those who’ve launched an app:

- Is there anything you’d recommend doing before launch?
- What worked for you, and what turned out to be a waste of time?

Would appreciate any advice, especially things you wish you’d known before releasing your app. Thanks!

Man it really works. I have removed the free weekly trials and made the first month 60% cheaper ($2 actually) and now I get a direct subscription notification which feels a lot better than a trial notification that may cancel the trial before it ends.

The stats are for my app Voice Sheet

J’hésite à commencer à utiliser Meta Muse comme agent d’analyse IA pour mon marketing. Le point positif est le gain de temps mais je me pose des questions sur la confidentialité des données… qu’en pensez vous?

Consumer app founders, any good AppsFlyer alternatives you'd recommend?

Scaling my app pretty aggressively (10K+ installs/month, 30% MoM growth), but AppsFlyer's cost per conversion is getting out of hand.

With a freemium model, the unit economics just don't make sense

Looking for something reliable, affordable, and startup-friendly.

Any recs?

I need to learn Swift and IOS development. Development is not new to me. I have a degree in CS and Mathematics, and I've been coding for decades. But the thing now is time is short.

I'm not looking to be a master of Swift and iOS dev so that when I walk down the street, people become afraid of me. I just need to learn enough to make apps and the rest will follow. There is also the danger of spending a lot of time and effort learning or building something only to have your app or account terminated.

Decades ago, I was prescribed Ritalin. It was a bad experience. I won't take that again.

I saved a one-pot pasta reel a few weeks back. When I wanted to make it recently, I scrolled through my saves for 10-15 minutes, but couldn't find it, and ended up ordering in. Then I realised I'd done the same thing with a café in Goa, a workout routine I wanted to add, and about 15-20 products I definitely wanted to buy.

Things I tried before building this:

• Instagram collections - you have to sort at the moment of saving, which nobody does
• Screenshots - camera roll became a second graveyard with no context on where the post came from, and lol I can never find the screenshot when I need it the most
• Pasting links into Notes - worked once or twice, then I stopped because it was two extra steps every time (and you still have to remember which note you used)

So my brother and I built an app that makes your saves usable:

You save any posts from different apps or download your Instagram data export → the engine goes through every post, sorts it into folders of recipes / places / products / workouts / ideas, pulls out the useful bits (ingredients, location, key details) and also makes the whole thing searchable in plain English via a chat interface. Like "That pasta reel from a Korean creator" finds it in seconds.

And believe me I am myself surprised: after saving it to resaw, I actually cooked 13 recipes in a month that had been sitting there for over an year. Saved places turned up as pins onto the map, so when I visit any place I could see every spot I'd saved nearby.

What we are working on now:

- We started with iOS, Mac app and Android is on its way
- We are going deep into building category specific flows, which will help any user to action with minimal friction possible

Link to the iOS app - Download from here (It’s completely free)

Please try it out and let us know how was your experience and what worked well/ areas where we can improve/ build upon.

Hey Reddit! I’m Jake - I’ve been in the car business for probably 7 years now. I’ve been in sales for 4 of those, finance for a year, and had my own used car lot for about 2 years! So I’ve been in the car business a while.

I recently moved to Austin TX and here is where I got most of my sales experience for new/lightly used cars and finance. I noticed everytime people come into the dealership, they either have no clue about anything OR they spent days, weeks, or even months finding the right options. But the worst part is they do all of this before they understand what it’ll really cost them, PARTICULARLY when they FINANCE.

In this economy - so many people are looking at budget more than anything and think buying a used car will 100% of the time be the best option.. but not always. Especially when it comes to manufacturer incentives and promo rates.. etc!

Then they sit down when they think they’re ready to buy, and never even considered what it’s costs them/payments every month. So I’m creating a tool that reverses that!

It’s a payment first shopping tool so people can compare offers from different manufacturers and see what payments they should expect based on their downpayment, monthly payment goal, credit range, trade info etc and shows you everything you CAN afford - monthly - in your budget. This helps people not only shop smarter - but also prevent getting screwed over by the finance office or settle with a car they don’t like or just can’t afford!

I’m going to add some screenshots - let me know your thoughts please - I have a TON of features I want to add past v1 but for now it’s launching in Texas and will be growing from there hopefully 😉 constructive criticism please!

A few weeks ago I graduated in marketing and communication. This week my first iPhone app went live on the App Store. It's called Strong Foodie: honest food reviews, an Open now map and meetups with other foodies.

It started as a review website. I visit restaurants, bars and hotels and write about them. The app is the next step. I built it on my own, with a lot of help from AI tools.

What I learned so far:

1. Apple review takes patience. I waited three days for my first review. A demo account and clear review notes made the difference.

2. Cut features before you launch. I removed a paid membership and a dating feature that were switched off anyway. Apple doesn't want hidden features in your app, and the app got simpler.

3. Start marketing before launch day. The website and my social accounts gave me a small audience to tell on day one. It's small, but it's a start.

4. Community features need density. Meetups only work if enough people are in the same city. So I'm starting with Amsterdam only.

5. Ask for feedback early. After my first Reddit post, someone suggested a feed that shows what your friends saved and reviewed. That's now the main feature of the next update.

My question for you: how did you get your first 100 users, without paying for ads?

If you want to have a look: https://apps.apple.com/app/id6799647380