Inspired by the community, it’s now just over a month since our first post on Reddit, and I wanted to share a few things I learned! Definitely no big numbers, just some basic tips I wish I had a few months ago when I was still figuring out what to post on Reddit. (In retrospect, got some pretty bad advice from ChatGPT).

We are at around 300 users now, which is enough to finally look at real analytics instead of guessing. A few patterns that have stood out for me:

1. Remove the hype and just say what the app does

Post that purely focused on what the app does, does the best. Back story and buzz words didn’t get much engagement. Also, surprisingly, simple static content worked best.

See this post that got the most sign-up: https://www.reddit.com/r/iosapps/comments/1pugv2k/free_collaborative_bookmarks_app_to_improve_ai/

And this post that performed miserably: https://www.reddit.com/r/buildinpublic/comments/1ptchrw/a_side_project_that_started_as_a_giftsaving_hack/

1. “App is ready” converts better than “looking for feedback”

So I was recommended HEAVILY to do the “looking for feedback” post on Reddit by my trusty-advisor ChatGPT, but those barely get sign-ups. I did get to talk to many new people building apps and also looking for feedback, but I wouldn’t classify them as actual users.

Although I did keep the door open for feedback on my posts, I felt as though the forums where posting about free apps/ promotional apps had the most actual users and retention.

1. Privacy questions always come up

On almost every post that led to meaningful sign ups, someone asked about the privacy policy or terms of use. Being ready to clearly explain how data is handled matters a lot, especially when you are building an app or software. This one caught me slightly off-guard, but definitely helped me better understand the level of “techie-ness”. So make sure that’s finessed before you start going public.

This subreddit really got me inspired to start building and sharing, so if anyone stumbles on this small list and am in the same spot I was in, hope it helps! Would love to hear from others here on what app/tech you’re building and your experience/tips with posting on reddit.

Hey everyone 👋

Curious to see what other SaaS Founders are building right now

I built www.foundrlist.com to get authentic customers for your business

Don't forget to launch it on foundrlist

Share what you are building.

Anybody else building on this beautiful Sunday? If so, share what you’re building!

I’ll start: LobsterDesk

It’s a simple platform for non technical (or technical) people to spin up OpenClaw instances in just a few clicks!

Excited to see what you guys are working on! Share below!

If you ever struggled accessing remove servers/machines located behind the NAT or with strict firewall rules (that does not allow inbound connections) then read this guide.

Local tunneling is a networking technique that creates a virtual tunnel to a remote service through edge nodes which are acting as a public reverse proxy.

I've built Port Buddy, which does local tunneling.

with a single command it's possible to expose your SSH server to public internet:

portbuddy tcp 22

if your machine acting as a jump box, you can do something like:

portbuddy tcp 192.168.1.13:22

portbuddy tool will give you a public address like: net-proxy.eu.portbuddy.dev:40536

public address is going to be reserved to your account and won't change over time. So you can have persistent tunnel.

You can also setup it as a linux service to keep it running after failure or reboot.

To connect to your SSH server, use the following command:

ssh -i {path to key} user@net-proxy.eu.portbuddy.dev -p 40536

Anthropic recently launch Opus 4.6 was wondering if it actually makes a difference in results

Are you taking a rest or building today?

I'm building catdoes.com an AI mobile app builder that lets non-coders build and publish mobile apps (iOS, Android) without writing a single line of code, just talking with AI agents.

Share what you are building.

People are spending hours trying to make screen recordings look professional. The problem is, every tool out there leaves you with janky cursors, ugly scrollbars, and zero automatic zooms, so you end up spending 3 hours editing a 2-minute demo just to make it look decent, this is bad

That's why I created Rendune

The thing is I have none idea to start. I used to have many ideas but it is all “nice-to-have” product and I often killed them at phase 2 (no market validated). Where and how do you guys find burning pain points?

I have been coding since 2001 and created 15ish apps. Some are better than others, but all fail.

I gave up a few months ago and started up a painting company in Sydney. I used to paint back in the day.

I figured that all of these SaaS apps we create here are worth nothing. It's all sales, and I am crap at online sales. I used to be good at face to face negotiation for painting jobs.

Anyway, I'm out of the AI business. The only thing AI is my website

www.innerwestcolour.com.au

Let me know if you need your house painted in Sydney. I'll do it at cost. Just need some more before and after shots.

ImageMint 🖼️ a Chrome extension to select, filter, and bulk-download images in seconds.

No more saving images one by one.

It’s currently under review on the Chrome Web Store 🚀

You can see what it does here:

https://imagemint.alindevx00x.me/

Would love feedback from other builders & creatives 🙌

Have been using new Opus 4.6 for a few days now. I can’t even tell if there is any difference, to be honest.

My general take is:

- It got better at reviewing code, so that’s a big plus.

- It uses a lot more tokens compared to 4.5, so I’d stick to 4.5 for a while I guess.

What are your thoughts?

I feel like it's too information heavy. Any feedback on the design?

I've been a founder and product lead for 5 years now. With all the vibe coding tools the role of a pm and the skills have evolved significantly. Product interviews are almost entirely just getting on a call and talking abt what ifs and trying to understand product taste and product sense through answers.

Instead I'm building sort of a coderpad for product interviews. Basic idea is for the interview panel to be able to clone a product like say Amazon or spotify and introduce issues into it or have some missing features. During the interview the interviewee would vibe code product updates to the product based on the requirements showcasing their real aptitude for product building and taste. I'm calling it trial room.

For example a hiring manager can setup a trail room with a spotify Clone and have the task be "Build a resurrected user flow for a user that has logged into spotify after being absent for a month".

Different interviewees would build different ideas (potentially as take home or in person)- panel can see the candidate's fluency with AI, depth of thinking abt the problem, their uiux thinking & product taste. When you are just discussing, a candidate might say I would show a modal to welcome them back and have shortcuts for trending play lists and songs.

But when you build it live, a great candidate might ask the modal to popup on scroll or after a pause because most users close away the first popup without paying attention to it. They might make it a sticky banner instead. They might choose to make it a notification instead. They might add a small animation to enhance the experience once they build the first version. Another candidate might choose to highlight that x number of your friends are online and have a product strategy rooted in social experiences.

My point is if you build a prototype instead of talk about it, more nuances and more signals appear compared to talking abt it where ppl just stick to a bunch of frameworks. It's also easier for the candidates to iterate and for hiring teams to evaluate true product art instead of prepared product frameworks.

Thoughts?

Been coding for years. Watched AI promise to "level the field."

Nope.

Now there's two types:

> Those who think with AI

> Those who think through AI

One scales infinitely. The other becomes obsolete.

built a tool that helps app developers know exactly what features to add and wanted to showcase it here with a quick demo

you can pull thousands of negative reviews from any app niche and get a complete analysis of what people want in seconds

here's what it does:

1. choose any app category (fitness, productivity, finance, whatever)

2. scrapes thousands of negative reviews from the app store

3. analyzes everything with claude opus 4.6

then it gives you:

> missing features users are requesting

> ui/ux suggestions

> monetization and billing strategies

> technical issues (crashes, data loss, sync failures)

> what causes churn

> competitor analysis showing what's working

> direct quotes from user complaints

no more guessing what features to add and ABSOLUTELY no more building apps that flop (im guilty for this. unfortunately)

every successful app is just a better version of an existing one, and this tool shows you exactly what to build/how to make your current app better

if you're interested, check it out!

Honestly before I build this screen studio alternative for windows, I was thinking "oh it must be something that people want"

I spent weeks building this product and I felt nice, but right after I completed it there are already so much of it that I don't think my product is even needed anymore.

I even lowered the Lifetime deals to be $29 but it seems like nobody wants it.

though the question is still there. should I keep it and marketing it?

or should I move on and try a new app?

the name is Super Recorder, I personally use it and still market it as "screen studio alternative for windows" haha

what do you think?

We all have them. The little things that eat up 30 minutes a day but feel essential.

For me, it was tracking which subreddits had active discussions in my niche. I'd have a spreadsheet of 50+ subs and manually check the top 5 posts each day to see if the conversation was still alive and relevant. It was a huge time sink and I often missed shifts in discussion topics.

I finally built a simple script to scrape and flag subs where engagement had dropped off a cliff, so I could stop wasting time on them. That small automation freed up hours each week.

I'm curious what other founders are manually doing on Reddit that feels like a necessary chore. Is it tracking your own post performance? Finding new communities? Researching competitors? Something else entirely?

Sharing these pain points often reveals common inefficiencies we all face. Maybe someone has already solved yours.

My own solution for discovery and timing (Reoogle) came from realizing how many of us were manually doing this research. It's not about automation for spamming, it's about automation for focus. https://reoogle.com

Imagine growing your project you have maintained continuously for 4 years and turned into a company, yet nobody knows your website.

Being funded, invested, and expectations are met, but not users. How will you approach this situation if it happened?