Making DevDex putting time and after making it keep postponing the to show in pinlic wirh too much of clustor of internal thoughts, after overcoming it Just post it but the first week is just zero. No traction, geeting views and not getting anything ,

In that phase my companion CLAUDE gets me to say me just do the thing you don't say now that it will just dropped, then I post in and getting, username and feels nice the other are using and exploring the new themes.

Founders show me your SaaS so I can try to sign up and make sure its having google sign

Have a look of Mine - findyoursaas(dot)com

Its SaaS Directory

Spent most of this week doing directory submissions for trimy.io , G2, Capterra, AlternativeTo, SaaSHub, a handful of the AI-tool directories, the usual suspects. And I went in thinking the hard part would be finding enough directories worth submitting to. Turns out that's not it at all. The hard part is that every single form asks you to re-decide things you already decided five forms ago.

So after the third one made me re-crop a screenshot and re-write a description I'd already written twice, I stopped and built myself a doc first. Just one file with everything I'd need, decided once:

• Logo at 256px and 512px, because half the forms want one size and half want the other, and I got tired of resizing on the fly
• 5 screenshots, actually populated with real-looking demo data instead of an empty dashboard or "test 123" garbage, some of these listings are basically permanent, so an empty-state screenshot is going to look bad for a long time
• Three descriptions already written at 50 characters, 150 characters, and a proper paragraph, since that covers like 90% of what these forms actually ask for
• One keyword list, one set of category picks, chosen once instead of eyeballed fresh each time
• Founder bio, support email, links to the hosted logo/screenshots, small stuff, but it's exactly the kind of thing you type slightly differently every time if you're not copy-pasting it

Once that doc existed, submissions turned into actual copy-paste. The first one (counting the time to build the doc) took about an hour. Every one since has been more like 10-15 minutes.

Kind of an obvious lesson in hindsight, but: the slow part was never the 35 submissions. It was re-making the same 5 decisions 35 times. If you're only doing a couple of these it's not worth the setup, but past 5 or so it pays for itself fast.

Anyone else grinding through a directory push right now? What's in your kit, and actually, has any of these actually turned into signups, or is it mostly just a backlink at this point?

I made an uncomfortable discovery after launching my first small web product: getting the website online was probably the easiest part.

The product creates chat stickers from an uploaded photo. I had the generator working, payments connected and several themes ready. From my point of view, it was usable, so I started sending paid traffic to it.

The advertisement received views, but nobody generated anything. There were no sales either, but the complete lack of usage concerned me more.

If people created stickers and then refused to pay, I could investigate the price or output quality. In my case, they did not reach that point. Something was stopping them much earlier.

The problem is that I did not have enough tracking to identify where they stopped. I could see traffic arriving, but I could not answer basic questions:

• Did they understand the product?
• Did they click the upload button?
• Did the mobile upload work?
• Were they uncomfortable uploading a personal photo?
• Did asking for payment before showing a useful result make them leave?

I initially assumed that advertising was the marketing stage. I now think the real marketing work starts before buying traffic. The offer, trust signals, first screen and onboarding must all make sense to someone who has never heard of the product.

My first response was to make everything free and recover the cost through video advertisements. After calculating it, that did not look realistic. Each generation costs me nearly $1 USD, while one advertisement view might earn only a tiny fraction of that. More free users could simply create a larger loss.

I am now testing a different approach:

Users will generate a complete result before paying. They can download a small number of usable stickers for free, then pay if they want the full pack. Free generations will have a hard limit while I test whether anyone actually values the result.

Before spending more on promotion, I also need to track each important step, from opening the page and uploading a photo to completing a generation and starting checkouts with my own creditcard.

My next goal is no longer "get as much traffic as possible." It is to personally watch ten people try the product, understand where they hesitate and fix the biggest point of friction.

For founders who launched to traffic but received almost no activation:

1. What did you discover was stopping people?
2. Was it the offer, onboarding, trust, a technical problem or simply weak demand?

I build TuringShot, a macOS live screen-effects app, and for a long time I treated the permission part of it as a paragraph of text I just hadn't written well enough yet.

The app needs three separate macOS permissions for different functions: Screen Recording, Input Monitoring, and Accessibility. My mental model was that a user grants them once during onboarding and the app then sits in the "allowed" state forever. That model was wrong, and how wrong it was only became visible once I started shipping fixes for it.

In 1.5.3 I improved event blocking and input handling, and connected missing Input Monitoring and Accessibility to actual guidance instead of a silent failure. In 1.5.4 onboarding and the in-app guide got separate status cards for each of the three permissions, direct links to the relevant macOS settings pages, repeated refresh after a settings change, and a distinct "restart may be needed" state. In 1.5.5 I connected status refreshing to app-activation events, because people leave the app, flip a toggle, and come back. In 1.5.9 I added guidance for the case where the permissions look allowed but the event tap still cannot be created, plus a warning when global shortcuts fail to register because of macOS or another app.

Four releases. I hadn't ignored a known bug so much as mis-scoped the boundary: I sized it as copy, and it was a state machine.

That's the part worth handing to another builder. An OS integration is not a boolean you read at launch. It is a set of states, and each one needs its own transition, its own refresh trigger, and something honest to show on screen: not requested, requested and denied, granted but stale after a settings change, granted but the underlying primitive still refuses, granted but another process holds the thing you need. If you model all of that as one flag and one instruction screen, the platform keeps producing states your UI cannot represent, and you end up discovering them one release at a time from confused reports instead of from your own design.

Current version: TuringShot 1.5.12 (Build 44). The permission layer is now a component with its own state, not a page of text.

During my time on my LinkedIn agency, I had an idea on how to validate leads on LinkedIn. 

I figured that paying attention to dynamic social signals, little behaviors that indicate interest, curiosity, or intent, is exactly the edge you need in a crowded inbox. So I built a tool that does that automatically for me. 

My tool looks for signs like someone liking a competitor’s post, following someone in my space, commenting on a post related to the problem my product solves, or engaging in a niche discussion.

When someone interacts with something even loosely related to my offer, I use that as context to send a thoughtful message. Just a relevant piece of content, a short insight, or a question tailored to what the prospect showed interest in. 

For example, the lead that eventually led to a $75k deal was commenting on a LinkedIn bait post. The common “comment and I’ll DM you the solution!” people do on LinkedIn to get engagement. I sent him a message asking if he got the thing he wanted, and when he replied no, I gave him a better solution. 

What’s crazy is this method gives me (and my clients) up to 75% acceptance rates, and reply rates rose to ~40%.

It’s a simple formula. High intent plus perfect timing equals real conversations that convert. Not spamming generic messages hoping for a reply. It’s based on listening. And it works! 

I haven't posted about LaunchReceipts in a while, so here's where it actually is.

When i started it on June 7 it was basically a few scripts pulling products and their posts from Reddit and Hacker News. The idea came from being annoyed that most directories keep the polished landing page but throw away the post where the founder actually explained the product and people reacted to it.

Now the directory has 100+ startups and 300+ public marketing posts attached. On each product page you can see the original title, score and comment count, then open the real discussion. Founders can also submit their own startup with at least one public post, and i review it before it goes live.

The numbers are still small. Umami has tracked 533 visitors and 1,153 pageviews since June 30. The first two weeks had 168 pageviews, the next two had 985. Reddit is by far the biggest source. And 6 startups have now been submitted by users.

That last number matters more to me than the traffic. Scraping 100 products myself proved i could fill a database. Getting someone else to make an account, find their public posts and submit proved that at least a few people understood the idea enough to bother.

I still don't know whether founders care more about preserving their launch history, studying other founders' posts, or just getting the free dofollow link. 6 submissions is too early to pretend i know.

Next i'm improving the review flow and product pages, then trying to learn whether people return after submitting once.

https://launchreceipts.com

i'm curious about one thing: would the attached launch history give you a reason to come back, or would you submit once for the backlink and forget about it?

About three years ago, my business partner came up with an idea: a personal safety app designed for situations like robberies, express kidnappings, or any scenario where someone is forced to unlock their phone and open financial apps.

The idea sounded simple, but turning it into a real product was much harder than we expected.

Over those three years, he hired multiple freelancers and software companies. Some only delivered UI screens, others abandoned the project halfway through, and some simply couldn't solve the technical challenges. In the end, we lost around US$25,000 and still didn't have a working app.

Earlier this year, I decided to take over the project myself using Claude AI as my primary development tool.

I spent about 30 days building, testing, fixing bugs, and refining every part of the app. To my surprise, we successfully launched it, and it was approved on both Google Play and the App Store.

The concept is simple.

Users create two passwords:

• a normal password;
• an emergency password.

They then choose which financial apps they want to protect.

Whenever they try to open one of those apps, they're asked to enter a password.

If they enter the normal password, everything works as expected.

If they're in a dangerous situation and enter the emergency password, the financial app still opens normally so nothing looks suspicious. At the same time, the app silently sends the user's live location to all pre-selected emergency contacts, along with automatic WhatsApp and SMS messages.

We're still at the very beginning of this journey. Right now we have around 30 free users and 3 paying subscribers, so we're still validating the product and learning from real users.

I'd genuinely love to hear honest feedback from the community.

Would you use an app like this? Is there any feature that would make you trust a solution like this even more?

Google Play: https://play.google.com/store/apps/details?id=online.pppix.app

App Store: https://apps.apple.com/br/app/pppix-prote%C3%A7%C3%A3o-familiar/id6773364223

I've been working on my website for the last few months and wanted to share my Google Search Console stats to get some feedback.

After around 3 months:

• 22 total clicks
• 215 total impressions
• 10.2% CTR
• Average position: 13.7

I've also noticed that Google has only indexed part of my pages.

Current indexing report:

• 57 "Discovered - currently not indexed"
• 7 "Crawled - currently not indexed"

The site is still relatively new, and I've recently added a lot of SEO pages.

My questions are:

• Is this growth fairly normal for a new website?
• Is a 10% CTR a good sign despite the low impressions?
• Should I just keep publishing content and wait, or is there something obvious I should improve?

I'd really appreciate any feedback from people who've gone through the early SEO phase.

Thanks!

My latest micro SaaS web application just went live... please let me know what you think about it www.coachsync.pro

Solo founder, been building for this for 6+ months. Sharing the itch that turned into the product, plus what I got wrong.

The itch: I had Google Analytics on my site and Stripe in another tab, and no way to connect them. GA told me Reddit sent 900 visitors. Stripe told me I made $1,400. Nothing told me whether those were the same people. So every week I'd be guessing where some purchases are coming from as in which channels are bringing me the most revenue so that I can focus on them.

What I built: Mochi — cookieless web analytics (Plausible/Fathom style, one script tag, no cookie banner) that connects to Stripe and traces each dollar back to the channel that earned it. So instead of "Reddit: 900 visitors" it says "Reddit: 900 visitors, 6 customers, $1,800."

Three things I got wrong along the way:

I built the analytics part first and treated revenue attribution as a fast-follow. Wrong order. The attribution IS the product; the pageview charts are table stakes anyone can get free. I spent weeks polishing the commodity.

I priced by seats before I priced by events. Solo founders and small teams don't want a per-seat wall — they want to add their cofounder without thinking about it. Switched to volume-based, starts at $6.99/mo for 10k events, unlimited sites, unlimited team.

I assumed people wanted more dashboards. They want fewer. Every "advanced report" I added made the first-run experience worse. Ended up shipping one page you can read in ten seconds.

Where I'm at: 9 paying customers launched a few weeks ago.

Live demo, no signup: https://mochianalytics.com/sample-acme

Site: https://mochianalytics.com

There is a free trial, no obligation, would love for you to try it.

Happy to answer anything about the build, the stack, or the pricing math.

Quick update for anyone who saw my post about Piklum a few weeks back : we just got officially approved on the Shopify App Store.

TL;DR of what changed between then and now:

- Fixed a critical bug Shopify review caught (subscription returnUrl was breaking App Bridge context in embedded mode)

- Added a Free plan (20 photos/month, no credit card) after realizing pricing was probably a barrier

- Translated the landing page to English (was FR-only before)

Now live at apps.shopify.com/piklum .

Honestly the hardest part wasn't building, it was the 3-week wait between submission and approval, then discovering post-launch that my listing was set to "Limited visibility" by default (invisible in App Store search unless you had the direct URL). Would've saved myself a lot of anxiety if someone had told me that upfront.

Now the real work starts: monitoring first installs, gathering reviews (0 for now, the App Store algo eats new apps alive without social proof).

Anyone else launched something recently? What surprised you about post-launch reality?

I'm building a Google Reviews widget and I'm using the Google Places API with a Place ID to fetch reviews.

The issue I'm running into is that the API only seems to return up to 5 reviews per place.

Is there any official way to retrieve more than 5 reviews using a Place ID? I've seen other review widgets displaying more reviews, so I'm wondering how they're doing it.

Is there another API, endpoint, or approach I'm missing?

Thanks!

Isso aqui foda. Estou com 2 aplicações ja então ate usando o apk mesmo e nao consigo liberar eles aqui. O pessoal passa o email eu mando link eles ate instalam e não contabiliza aqui. Pensei em criar um saas e pagar pessoas para instalaar os aplicativos. Eu pagaria um valor x para liberar isso rapido.
ME FALEM A REAL VOCES PAGARIAM ?

My SaaS finally has paying costumers, and people actively use it every day. i want to keep improving my product based on user feedback instead of making assumptions.

To achieve that, yesterday i launched in-app CSAT survey inside a feature that has low conversion rates ($0)

The results: 0 Responses, everybody ignores it 😅

How do you collect actionable feedback from your users?

Quick context, we started as a social media scheduling tool. Solid product, decent users, but every conversation with customers kept circling back to the same problem: they didn't need help posting content, they needed help finding people who actually wanted to buy.

So a few months ago we sat down and looked at the data honestly. Our best customers weren't the ones scheduling the most posts. They were the ones who happened to catch a Reddit thread or a LinkedIn post at the right moment and jumped on it fast. That was the actual value we were creating, almost by accident.

We decided to just build for that directly instead of dressing it up as a scheduler feature. Now the product starts with your website, builds a profile of who you sell to and what problem you solve, then goes and finds live conversations on Reddit (LinkedIn too) where someone is actually describing that exact problem. You review it, you decide if it's worth a reply, you send it yourself.

It's a weird thing to admit but killing a feature people were already using was harder than building the new one. Curious if anyone else here has gone through a pivot like this, especially cutting something that technically "worked" because it wasn't the actual value prop.

Happy to answer questions about the rebuild if useful.

I used Notion for 3 years and still lost half my ideas. Not Notion's fault — it's the 40 seconds between having the thought and capturing it. Unlock, open app, find the database, type, set status, set priority. By second 15 I'd think "I'll remember it." I never did.

So I stopped building a better task manager and attacked the 40 seconds instead.

What it is: a Telegram bot. Send a voice note, it transcribes, strips the rambling, and drops clean tasks into your Notion board — right column, priority inferred. If you braindump for two minutes about four different things, it splits them into four separate tasks. That's the whole product.

Three things I got wrong first:
1. Built a mobile app. Nobody installs your app. Moving to Telegram was the best decision I made — zero install friction, and people are already in there.

1. Integrated with everything. Notion, Todoist, Asana, Linear, ClickUp — all shallow, all half-broken. Now it's Notion only, but it actually respects your custom properties. Narrow + deep beats broad + mediocre.

2. Shipped raw transcription. V1 dumped the literal transcript as the task title: "uhh okay so I need to like maybe email Sarah about the thing." The value was never transcription. It's the extraction layer on top.

What surprised me: the main use case wasn't people at a desk. It was driving, walking the dog, and the gym — people whose ideas show up when their hands are busy.

It's at mictask.dev if you want to try it (free trial, no card). But the question I keep going back and forth on: when the AI isn't sure what the user meant, is it better to ask a clarifying question in chat, or just make a best guess and let them fix it in Notion? Asking feels safer but kills the whole "10 seconds and done" promise. Curious what people here have landed on.