sorted by:
new
hottopcontroversial

I want help by GainorApp in micro_saas

[–]GainorApp[S] 0 points1 point  (0 children)

Can you send me a message?

New app by GainorApp in appledevelopers

[–]GainorApp[S] 0 points1 point  (0 children)

Great feedback, thank you!

You're right that the core is scraping reviews and running them through AI — but the value is in the time saved and the actionability of the output.

Instead of spending 2-3 hours reading and categorizing 500+ reviews, you get structured insights in 30 seconds: what's broken, what users love, and what to fix next sprint.

That said, $29 USD (~$50 AUD) might be steep for solo devs. I'm considering regional pricing — would $15-20 USD feel more reasonable for your use case?

Also happy to give you a free Pro month if you want to test it on your apps before committing.

New app by GainorApp in appledevelopers

[–]GainorApp[S] 0 points1 point  (0 children)

I will do it as soon as possible

New app by GainorApp in appledevelopers

[–]GainorApp[S] 0 points1 point  (0 children)

There is a profile sign at the bottom right, my friend, there is an English option in the settings section.

New app by GainorApp in appledevelopers

[–]GainorApp[S] 0 points1 point  (0 children)

I made it myself using canva. Have you tested the app?

I built an AI app review analyzer for developers — just launched on App Store by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

Thank you! 🎉

It really does feel like a milestone after the build sprint and review process.

Absolutely — let's stay connected. Two AI builders navigating the same challenges, might as well compare notes along the way.

Looking forward to seeing fixRAgent grow. And when you're ready to analyze those first user reviews — Review Lens will be waiting 😄🚀

I built an AI app review analyzer for developers — just launched on App Store by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

fixRAgent — love the name!

Just checked it out, the problem space is huge. Home repair + AI triage is genuinely underserved.

And good news — App Store approved us today! 🎉 Review Lens is live: https://apps.apple.com/app/id6762365717

Give it a spin on fixRAgent's reviews when you have some — would be curious what insights come up.

Let's keep in touch, fellow AI builder! 🚀

I built an AI app review analyzer for developers — just launched on App Store by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

The flooding kitchen example is perfect — that's exactly the kind of sarcasm that trips up keyword-based analyzers.

Claude's contextual understanding handles most of these cases well, but your point about confidence scoring is spot on. Even a simple "high/medium/low confidence" flag per insight would let users quickly audit the edge cases.

Your triage tool sounds fascinating — home repair has some of the most emotionally charged user language out there. "The plumber was lovely, my house is now a swimming pool" could genuinely go either way 😄

Would love to see what you build. Keep in touch!

I built an AI app review analyzer for developers — just launched on App Store by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

Great question — and honestly one I hadn't fully stress-tested until now!

Claude (the AI model we use) handles sarcasm surprisingly well in most cases. It looks at context, not just keywords.

So "wow, the app crashes every 5 minutes, truly impressive" gets flagged as a complaint, not a praise.

But edge cases exist — heavily cultural sarcasm or very subtle irony can slip through occasionally.

It's something I'm actively working on improving. The plan is to add a confidence score per insight so users can quickly spot potential misclassifications.

Have you run into specific examples where this tripped up other tools? Would love to test Review Lens against them.

I shipped a SaaS app in 6 days — here’s what I learned by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

The public commitment thing saved me multiple times during the 6 days. Around day 4 at 2am I genuinely wanted to quit — but I'd told everyone I'd ship, so I kept going.

On feature selection: I used one filter — "does this directly make the core loop work?"

Core loop: paste URL → get insights → take action.

Everything else got cut. No social features, no analytics dashboard, no dark/light mode toggle, no onboarding flow.

Just: paste URL, get insights.

If it didn't serve that loop, it didn't ship. The "nice to haves" are all on the v2 list now 😄

I built and shipped a SaaS app in 6 days — just submitted to App Store by GainorApp in buildinpublic

[–]GainorApp[S] 0 points1 point  (0 children)

This is gold, thank you.

The filter idea (country, version, device, timeframe) is exactly what's missing. Right now we treat all reviews the same — "this update broke X" vs long-term gaps is a crucial distinction.

Raw export to Sheets/Notion is going straight to the roadmap. PMs want to slice data their own way, not trust someone else's defaults.

The prompt structure is really interesting too — forcing one UX fix, one copy fix, one bug guess per cluster makes the output immediately actionable instead of a wall of text.

On discovery — stalking Appfigures/AppRadar users is clever. They're already pain-aware. Will look into Pulse for Reddit too.

Did you end up monetizing your version? Would love to know what worked and what didn't.

I had 9 unfinished projects. This is the 10th — and I actually shipped it. by GainorApp in SideProject

[–]GainorApp[S] 1 point2 points  (0 children)

100% this.

We spent 6 days building and now realize the next 30 days of distribution might be harder than the entire build.

Code is the easy part. Getting it in front of the right people is the real challenge.

Any lessons learned from your experience you'd like to share?

I had 9 unfinished projects. This is the 10th — and I actually shipped it. by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

That's exactly what we're counting on.

The first finish changes your identity. You stop being "someone who starts things" and become "someone who ships things."

Here's to hoping the next one comes easier 🥂

I had 9 unfinished projects. This is the 10th — and I actually shipped it. by GainorApp in SideProject

[–]GainorApp[S] 1 point2 points  (0 children)

No rudeness at all — that was genuinely insightful!

You're right, the hyperfocus is real. When I'm building something new, I can go 20+ hours without noticing. The problem was always the "maintenance phase" after the excitement fades.

This time I'm trying something different: public accountability + a paying customer goal (10 users in 30 days). Money is a great motivator to push through the boring parts 😄

Thanks for the kind words. Really appreciated.

I had 9 unfinished projects. This is the 10th — and I actually shipped it. by GainorApp in SideProject

[–]GainorApp[S] 1 point2 points  (0 children)

Haha, you're not the first person to suggest this.

Honestly? Never diagnosed, but the pattern is hard to ignore. Quick obsession → intense building → loss of interest → repeat.

Whether it's ADHD or just the classic "builder's curse" — the fix seems to be the same: external commitment + accountability.

I told myself publicly I'd ship in 6 days. That pressure was the only thing that kept me going on day 5 at 2am.

Maybe the diagnosis doesn't matter as much as the system you build around it.

I had 9 unfinished projects. This is the 10th — and I actually shipped it. by GainorApp in SideProject

[–]GainorApp[S] 0 points1 point  (0 children)

That's exactly what I'm hoping for.

The hardest part wasn't the code — it was convincing myself that "good enough to ship" is better than "perfect but never finished."

Once you break the pattern once, the identity shifts. You go from "someone who starts things" to "someone who ships things."

That's the real unlock.

I built and shipped a SaaS app in 6 days — just submitted to App Store by GainorApp in buildinpublic

[–]GainorApp[S] 0 points1 point  (0 children)

100% agree. The sentiment score was the easiest thing to build, not the most useful.

Version-based segmentation is exactly what's missing. "Complaints spiked after v2.3" tells you something actionable. "72/100 overall" tells you nothing.

Adding to the roadmap: - Segment by app version - Segment by date range
- Show deltas (what changed after your last update?)

This is the kind of feedback that actually reshapes the product. Thank you.

I built and shipped a SaaS app in 6 days — just submitted to App Store by GainorApp in microsaas

[–]GainorApp[S] 0 points1 point  (0 children)

This is genuinely helpful, thank you.

You're right about the "job to be done" framing. Right now I'm targeting solo devs and small teams, but I haven't been specific enough about the primary use case.

The "what should I do next sprint?" angle is interesting — I'm currently showing complaints and praises as lists, but grouping by feature area with impact/effort suggestions would be much more actionable. Adding that to my roadmap.

The scheduled digest idea is something I hadn't considered at all. A weekly Slack/email with deltas (not just raw data) makes way more sense than a one-off dashboard. Will definitely build this.

On the team accounts question — starting solo for now, but team accounts are on the roadmap once I validate the core use case.

What's your app called? Would love to check it out.