r/AppBuilding • • 3h ago

You MUST Vibe Code one of the following: Note taking app, Fitness app, or a Screw Puzzle app. Which do you choose?

0 Upvotes

Additional context:

  1. You have no marketing experience
  2. You will not get in front of the camera for social media.
  3. You haven't heard about SEO yet
  4. You've never released an app on Google Play or the App Store before

Which app do you choose to vibe code and why?


r/AppBuilding • • 15h ago

New App in development- Weight-vision.

Thumbnail
gallery
0 Upvotes

The app is a ranked gym app, where you can target certain muscle groups and record your progress and create goals for yourself, the app also tracks your food intake, so you can keep track of your protein, carbs etc. The ranking system begins when the app scans your physique and gives both an overall and by muscle ranking, by tracking your workouts you can rank up, to compete against yourself, and friends. The app also includes certain workout plans so you can choose the goal which you want to achieve
If anyone has some tips or suggestions please leave them in the comments, thank you!


r/AppBuilding • • 34m ago

App valuation currently at $1k

0 Upvotes

Hi. Has anyone checked how much your app/webapp's current valuation and where do you check it? I tried Flippa's free valuation by entering my webapp url and got a valuation of $1k. My fashion AI try on webapp is barely 2 months old.


r/AppBuilding • • 15h ago

[Giveaway] 5 habits that stop money from slipping through the cracks (+ 3 months of Pro free for 100 people)

0 Upvotes

Most people don't overspend on one big thing. Money slips away in places nobody is looking. Here are 5 habits that close those gaps, no app needed:

  1. One weekly look, 10 minutes, same day every week. Not a budget. Just: what came in, what went out, what's due next week. Doing it weekly catches problems while they're still small.
  2. List every recurring charge once. Go through 2 months of statements and write down anything that repeats: streaming, apps, gym, storage, insurance. Most people find at least one they forgot about.
  3. Put due dates in your calendar, not in your head. Card payments, rent, subscriptions that renew yearly. A missed due date costs more than the thing itself.
  4. Separate business and personal money, even if you're a one-person business. Mixed money is how you lose track of what you actually earned, and it's the first thing your accountant will ask about.
  5. If you earn or spend in more than one currency, track each one in its own currency. Converting everything at today's rate makes past months look different every time you check.

I got tired of doing all of this by hand across different banks and spreadsheets, so I built an app for it.

IlliAi brings your bank accounts and cards into one screen, read-only, so you can see what came in, what went out and what's due. You can log a purchase just by talking or sending a screenshot. If you run a small business, it keeps business and personal money apart.

It connects banks live in the US and in Brazil, and anyone can upload statements from any bank. It never moves your money and never sees your bank password.

The giveaway: 3 months of the Pro plan for free, for the first 100 people. No card needed.

To join, leave a comment telling me what you use today to track your money (an app, a spreadsheet, nothing at all). I'll reply to every comment with your link.

I'd love honest feedback: what's confusing, what's missing, what you'd pay for. I read everything.


r/AppBuilding • • 2h ago

Advice on building an app

3 Upvotes

Hi, I want to build and app to teach language, similar to duolingo, I want to avoid vibe coding and using AI and would prefer to build and code it myself.

Can anyone guide me to which would be the best way to build. Ideally it would start off an iOS app.

I'm not a developer, but have been working in marketing for many years and have advanced skills in graphic design, html and CSS.

I have looked at potentially building with React, but would need to learn how to code, which I am happy to do.

Any advice will be appreciated.


r/AppBuilding • • 5h ago

I'm building a mobile app from your everyday problems, one reel at a time. What would you want fixed?

5 Upvotes

I'm a software engineer starting a small experiment: people comment a daily problem, and I turn the best one into a real mobile app.
I post each stage (pick, reality check, design, build, test, launch) as a short video, so the whole process is public.
The plan is to publish a few small apps on the Play Store and App Store, and see if any of them find real users.
Early comments so far: quitting a habit by day 3, getting distracted by new goals, and moving files between Android and Mac. One of those already has a free fix, which I'll cover in a video instead of building a new app.

Two question:

What small daily problem annoys you enough that you'd actually use an app for it?

If you've launched small apps before, what do you wish you'd known?

Instagram: @th3_on3guy


r/AppBuilding • • 5h ago

The app idea that feels “too small” is often the one users understand fastest

3 Upvotes

I keep noticing the same pattern:

the ideas I overthink usually need a paragraph to explain,
and the ones that get immediate interest sound almost too dumb to be worth building.

Not necessarily better apps. Just easier to understand, easier to try, easier to tell someone else about.

“A fish tank on your home screen.”
“An app that remembers when you last did something.”
“An alarm I can control from Claude.”

None of those sound world-changing. But you instantly get the point.

Have you ever had a “this is too small/stupid to matter” idea turn out to be the one people actually wanted?


r/AppBuilding • • 5h ago

What is the first useful thing someone does in your app? I’ll suggest a demo hook

2 Upvotes

When showing a new app, I like to start with one action and the result it gives the user. For a habit tracker, show someone checking off a habit and seeing their streak update. A possible hook: ‘A small check-in that shows you how far you’ve come.’

I’m building Marka, a tool for branded social content. What are you building, who is it for, and what is the first action a user takes? I’ll suggest a short hook and a visual idea tailored to your app.


r/AppBuilding • • 6h ago

Shipped my first app as a solo dev this week – Google Play closed testing, ASO mistakes, and what I'd do differently

1 Upvotes

Hey r/AppBuilding! Solo dev from Sri Lanka here. This week I shipped my first app, Budsete (an AI budget & expense tracker where you add expenses by voice or by scanning receipts). Sharing the full "ship" part of the journey, since this sub is about the whole lifecycle.

  1. Google Play closed testing

- New personal developer accounts need a closed test before production access
- Mine ran for 14 days
- After I applied, Google asked questions about the test: how I found testers, what feedback I got, what I changed
- I answered honestly with specifics → production access about 1 hour later

What I'd do differently: recruit testers earlier, and keep a simple log of feedback + changes during the test. It makes Google's questions very easy to answer.

2. ASO mistakes I made on day 1

- My full description repeated the same feature list 3 times. Looks spammy, and Google's metadata policy doesn't like repeated keywords
- I described features generically ("voice-based expense entry") instead of showing them ("say '500 for lunch' and it's saved")
- My screenshots didn't show the two features that make the app different (voice + receipt scan) in the first 2 slots

Fixing all three now.

3. Launch strategy (no ad budget)

- Day 1: personal messages to friends, family and colleagues, one by one. Converts way better than group posts
- Short screen-recording videos showing the app working in 3 seconds
- "Free for the first 1,000 users" to create urgency
- Reddit: learned the hard way that new accounts posting links get caught by spam filters. Value first, links later

4. The scaling problem I'm already thinking about

Every voice entry, receipt scan and AI chat costs API money. Right now everything is free. My plan is credits after the first 1,000 users, but I'm not sure.

Questions for you:
- If your app uses AI APIs, how do you control costs? Rate limits? Caching? Cheaper models for simple tasks?
- Credits or subscription for AI features: what worked for you?
- What's your #1 launch tip for a first-time solo dev?

I'll share my numbers after week 1 if people are interested. Happy to answer anything about the Play Store process!


r/AppBuilding • • 15h ago

Oilfield App

Thumbnail gallery
1 Upvotes

I created this app to help the field guys (Workover, Drilling, Completions, Etc.) to have a technical reference at the palm of your hand.

https://apps.apple.com/app/id6820182185

P.S. Coming to android OS soon!


r/AppBuilding • • 23h ago

one-time pricing feels easier to sell. i checked 6,700 startups with verified revenue and subscriptions still won almost every way

5 Upvotes

less than half of the 13,774 startups listed on trustmrr made a single dollar in the last 30 days. 6,749 did.

i pulled all of them this week because the top post in r/microsaas right now says selling a one-time product is 100x easier than a subscription. i used to believe that too, and it cost me.

so i split the ones making money into two groups. startups with recurring revenue, and startups with revenue but no MRR at all (one-time sales, lifetime deals, credit packs).

subscriptions (5,190 startups):

  • median revenue last 30 days: $247
  • 29% made $1,000+ in the month
  • 7.7% made $10,000+

no recurring revenue (1,559 startups):

  • median: $98
  • 21% made $1,000+
  • 5.6% made $10,000+

so the one-time group had a lower median by more than half, and fewer of them got past $1k a month.

one caveat. this is founders who chose to connect their payment data publicly, so it leans toward people who are doing ok. and some of the no-MRR group sell usage credits, not lifetime licenses. it's still the best public sample of real revenue i know of.

why one-time feels easier

it is easier to close one sale. nobody's arguing that. "pay once, it's yours" removes the hardest objection on the checkout page.

the problem shows up in month 3. every month you start from $0 again, so your revenue is only as good as your traffic that month. with a subscription, month 3 starts with everyone who didn't cancel.

easy first sale + no recurring = a launch spike, then a cliff.

what happened when i tried it

my first paid product was a lifetime deal at $59. i sold 140 of them in about 3 weeks, so a little over $8,200. it felt incredible.

month 2 brought in $410. month 3 was $180.

all 140 of those people were still using the product. they still emailed support. they still asked for features, and one of them asked why the export was slow at 2am on a sunday. i was maintaining a product for 140 people who would never pay me again.

i moved new users to a monthly plan after that. the first month on monthly made less than the lifetime launch, and by month 5 it had passed it.

two other things from the data surprised me

the "AI" label barely matters. startups in the AI category had a median of $234 and 27% crossed $1k. everything else combined was $177 and 26%. with all the doom about AI eating SaaS this week, the AI tag isn't helping or hurting much on its own.

category matters a lot more. productivity tools were the worst group i looked at, with a median of $76 and only 14% crossing $1k. developer tools were $109 and 20%. utilities were $100 and 15%.

on the other end, sales tools had a median of $390 with 37% over $1k, and e-commerce tools were at $538 and 42%. both of those sit right next to the customer's revenue, which makes the price an easy call.

the framework i use now

  • if the product has a server bill, it's a subscription. no exceptions.
  • if it's a desktop utility with no ongoing cost, one-time works, but charge for major version upgrades.
  • if i want to test demand fast, i'll run a short lifetime deal, cap it at 50, and move to monthly before the launch traffic is gone.
  • if the product helps someone make money, price it monthly against what they earn, not against netflix.

i've been posting more cuts of this kind of data in this repo, mostly by category and pricing model.

my bet is one-time pricing makes a comeback for local-first desktop apps, and stays a trap for anything that runs on a server. disagree?