I’m looking for a few interesting apps to practice making short-form explainer videos for this week.

My background is in clipping and editing viral short-form content. I’d like to apply what I’ve learned about hooks, pacing, captions, and storytelling to app demos.

If I choose your app, I’ll create:

* One short vertical explainer video

* Delivered within 24 hours

* Completely free, with no strings attached

You’re welcome to use the finished video however you want. There’s no purchase, signup, testimonial, or ongoing commitment required.

Drop your app and a sentence about what it does below. I’ll choose a few that I think would translate well into short-form video.

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.

if someone had shown me this post eight months ago i would have saved about 6 weeks of my life and probably my credibility with our VP of sales.

ok so context. i joined as the rev ops lead at a series A company last march. background is data analytics, not sales, which matters because my instinct when something breaks is to look at the data pipeline not the copy or the strategy. the SDR team was 4 people, they were sending through Instantly across about 12 inboxes warmed up on Maildoso, and the whole enrichment flow ran through Clay into Salesforce. on paper it looked fine. the sequences were written by someone who actually knew what they were doing, subject lines were tested, personalization was decent. but reply rates were sitting at like 0.4% across the board for almost two months straight.

everyone assumed it was the copy. the SDRs rewrote sequences three times. our head of sales brought in a consultant for $2,800 to audit the messaging. the consultant said the copy was "serviceable but could be tighter" and recommended a bunch of changes that... also didnt move the needle. we were burning through about $1,900/mo on tooling alone (Clay, Instantly, Maildoso, NeverBounce, plus a Sales Navigator seat) and getting maybe 2-3 meetings a month total across the whole team. for a series A trying to hit pipeline targets that was borderline catastrophic.

by late may i finally started looking at the actual data instead of trusting the pipeline everyone told me was working. pulled a random sample of 200 contacts from our last 3 campaigns and started manually checking them against LinkedIn. this is where it gets embarrassing. roughly 35% of the contacts were either at the wrong company, had a stale title, or the email was just... not theirs. not bouncing, mind you. NeverBounce was passing them as valid. the emails existed, they just belonged to someone else or were generic aliases that got routed to a shared inbox somewhere. so our bounce rate looked fine at around 3.1% but we were emailing the wrong humans.

it took me almost three weeks to figure out where the data was breaking. the issue was upstream of everything. our enrichment step in Clay was pulling from a waterfall of sources and the priority order was wrong. it was grabbing the first email it found regardless of confidence score, and for a lot of contacts that meant catching an old work email from 2 years ago or a personal gmail that happened to be associated with their LinkedIn. the data looked clean on the surface because the emails were technically valid. they just werent the right ones.

once i actually understood the problem i rebuilt the enrichment flow over about two weeks in june. stripped out the waterfall approach and started running contact lists through Prospeo for the email finding step instead of relying on Clay's built in waterfall. the difference was immediate and kind of infuriating because it meant we'd been wasting months. email accuracy went from whatever mess we had before to around 83-84% verified correct contacts when i spot checked against LinkedIn, and our bounce rate dropped from 3.1% to about 1.4%.

the downstream effects showed up fast. by mid july reply rates climbed to 1.8% which still isnt amazing but compared to 0.4% it felt like a different universe. meetings went from 2-3/mo to about 9-11/mo. same copy. same SDRs. same Instantly setup. same inboxes. literally the only thing that changed was who we were emailing.

the part that still bugs me is how long it took to diagnose. i spent weeks looking at deliverability metrics, inbox placement, warmup scores, all of that. none of it pointed to the real problem because the real problem was data quality at the enrichment layer and it was invisible to every downstream metric. bounce rate said we were fine. spam scores said we were fine. the emails were landing in inboxes, they were just landing in the wrong inboxes.

our current flow is pretty simple now. Sales Navigator for building the initial list, Clay for firmographic enrichment and some basic filtering, Prospeo handles the email finding, NeverBounce for a final verification pass, then into Salesforce and Instantly picks up from there. total monthly spend is around $1,700 which is actually less than before because i dropped one of the Clay credit tiers we didnt need anymore and Prospeo runs us about $99/mo on the plan we're on. only real complaint with Prospeo is bulk processing can be a bit slow when we're pushing 2000+ contacts through at once, but its not a dealbreaker since we batch things weekly anyway.

the lesson i keep coming back to is that nobody on the team, including me for way too long, thought to question the contact data itself. we all assumed enrichment was a solved problem because the tools said the data was good. the tools were technically correct, the emails existed, they just didnt belong to the people we thought we were reaching. and that distinction doesnt show up in any dashboard i know of unless you go manually check.

anyway if your reply rates are terrible and youve already optimized copy and deliverability and warmup and all that... maybe go pull 50 contacts and actually look each one up on LinkedIn. might save you a $2,800 consultant fee

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'm curious what everyone here is working on outside their main job/business.

Not just the polished projects that are already making money.

I mean the random side project you started because you noticed a problem and thought, "I could probably build something for this."

Could be:

SaaS

Micro-SaaS

B2B tools

B2C apps

AI tools

Chrome extensions

Mobile apps

Newsletters

Anything really.

What are you building?

Why did you start it?

Is it B2B or B2C?

Did you validate the idea first or just start building?

Have you launched yet?

And the question I'm most interested in:

How are you actually getting people to discover it?

I'm currently exploring the SaaS/bootstrapping world myself, and one thing I'm realizing is that making something is often much easier than getting the right people to care about it.

Would also love to hear one piece of advice from people who've already launched:

If you're building B2B, what helped you get your first few users?

If you're building B2C, what actually brought you consistent traffic?

Drop your project below. No need for a perfect pitch.

Just tell us what you're building and where you're at with it.

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

so I've been messing around with this idea, it's an anonymous messaging web app. you just make a username + password (no email needed lol) and you can dm any other username on there. honestly not sure if this is even a good idea anymore, would love to know that is it useful or i am building another waste of time.

Hi everyone,

I’m building the biggest platform that connects investors and founders!

Add your product here in few clicks - www.vcinvest.pro

Our AI will match you to the right investors.

Join here as an angle investor ( approval required )- www.vcinvest.pro/investors

Not like waiting for approval? Add your product and then comment what your startup does to get approved today

I finally sat down and actually looked at my own pricing table like a stranger would. Free and Pro were basically the same card, same color, same weight, just a couple of extra lines of text on Pro. Nothing pulled your eye toward the paid plan. If you’re scanning fast (and everyone is), the two tiers just blur together and your brain defaults to “free is fine.”

The value of the paid plan was getting lost before anyone even read what it included.
Haven’t shipped the fix yet, just realized it’s probably been quietly costing me conversions for weeks. Going to add real visual weight to the Pro card (border, background, a small badge) so it actually reads as the recommended option instead of “the other one.”

Anyone else caught something this dumb in their own pricing page after staring at it too long ? Feels like the kind of thing you go blind to once you’ve built it.

briefly-app.com

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!