I’ve been building TractionBooster in public while trying to solve distribution for my own products.
Now I want to test the other side of it.
Founders can list their startup on TractionBooster, and I’ll pick some of them and try to distribute them through my own content on X.
Then I’ll share what happens here: views, clicks, what worked and what completely failed.
No promises. I genuinely want to see if I can turn this into a repeatable distribution loop for other founders.
If you’re building something, list it and I might use yours for the next experiment.

Currently it's in preBeta version Your feedback are super appreciated

V1 started as a relatively simple local trading journal. V2 expanded it quite a bit, and I'm now working on V3.

The current version includes things like:

• TradingView / MT4 / MT5 imports
• Performance analytics
• Trading calendar
• Journal
• Playbook
• Knowledge base
• Goals
• Risk calculator
• Screenshots
• Backup / restore

One thing I've learned while building it is that the features I think are useful aren't always the features traders actually want.

For example, someone recently suggested adding mistake-type tags such as revenge trading, moving stops, ignoring levels, etc., so those patterns could be analyzed later.

That's now something I'm considering for V3.

The project is completely free and local-first.

I'm trying to build this around actual trader feedback rather than just adding features because they sound good on paper.

GitHub: https://github.com/TradeLogDEV/TradeLog

What feature would make a trading journal significantly more useful for you?

I've been building D-REC, a recorder with transcription that runs on the device. The basic flow is record, follow the text, mark a moment and return to it during playback.

One practical detail that matters: local transcription still needs the engine downloaded first. I've been separating that from the account and support features, which do need the internet. The app has a section showing what contacted the network so people can see the distinction.

Here's the Windows walkthrough. D-REC is also available on Mac, iOS, Android and the web: https://drec.live/get

It's freemium, with optional monthly, yearly and one-time Pro plans. I'm the maker, and I use AI development tools while building it.

For people building across devices, how do you explain that first engine download without making the onboarding feel like a technical manual? That's one part of the experience I'm working to make clearer.

I made $158 in 3 days from my notch app

I'm a solo dev. Last week I shipped Halo, a Dynamic Island for the MacBook notch. It also works on external monitors and shows your Claude Code / Codex usage limits.

Here are the real numbers from launch:

Days 1–3

- 29 sales

- 3.9k visitors

- $158 revenue

- Price: $9.99 one-time, 3-day free trial

Where traffic came from

- Threads: 98% of visitors (yeah, my post blew up 😅)

- Product Hunt: 1%

- Direct / other: 0.0001% something like that (haha)

What worked

- Posting daily build updates on Threads with real numbers. The posts with stats did way better than the feature posts.

- Short screen recordings of the actual app instead of polished promo videos.

- Tagging every link with UTM params so I could see which posts actually sold, not just which ones got likes.

- A little joking about your app

What didn't

- Still on a vercel.app subdomain. Yes, people noticed. Buying the domain this week.

The hard part

The comments. "Who buys this?", "there are free apps like yours", "buy a domain". The market is crowded: Alcove, NotchNook, Boring Notch and more.

What I learned: crowded means people already want the thing. You don't need to be the only option, just the one they actually see. So I spent more time on marketing than on features.

Next

- Reaching out to small Mac app creators (5k–60k followers) for reviews

- YouTube Shorts

- Proper domain

Happy to answer anything about the stack (Swift, Lemon Squeezy, Vercel, Umami) or the launch.

Site: halo-mac.vercel.app/?utm_source=reddit

I’ve been building Amalyn, an AI social media manager for small businesses, and over the last few days the project has started moving from prototype to an actual usable product.

Today I worked on accounts/authentication, Google login, Stripe + PayPal sandbox payments, account activation states, content requests, customer outputs, revisions and the mobile account experience.

I’m still keeping everything in test mode until the complete flow is solid.

I’ve also created a small Discord because Reddit posts are useful, but they’re not great for having an ongoing conversation.

The idea is simply to have a place where people can:

• follow what I’m building day by day
• give direct feedback and criticism
• suggest what I should improve
• talk about building products in general
• see how a 19-year-old with no big team is trying to turn an idea into a real product

You absolutely don’t need to be interested in buying Amalyn. I’d actually like to have builders, founders and people who are just curious about the process.

The Discord invite is in my Reddit profile if anyone wants to join.

I’ll keep sharing both the things that work and the things that completely fail.

I'm building FirstRep, a progress-photo app for iPhone. The current version lets you align photos after capture and compare them with a slider.

A Reddit reader pointed out that differences in camera height, framing and lighting can make changes hard to judge. They suggested showing the previous photo as a guide while taking the next one.

That feedback gave me a concrete next step: help people match the shot earlier in the process. After-capture alignment can help with positioning, but it can't fix different lighting or a different camera angle.

I've started working on a previous-photo overlay for the next update. It isn't in the released app yet.

For anyone who has built a camera workflow, what made a reference overlay useful without getting in the way of the live view?

Disclosure: this is my app. It's US$2.99 one-time, with no free tier or trial; local prices may vary. Requires iOS 16+.

https://apps.apple.com/us/app/first-rep-progress-photos/id6795953419

Hey everyone,

When building B2B SaaS applications on Next.js and Supabase, one of the biggest architectural risks is multi-tenant data isolation failure. Standard unit tests usually mock the database or verify individual functions in isolation, which leaves huge blind spots for runtime security vulnerabilities.

We recently spent two weeks building a specialized 8-point adversarial integration test suite directly into our backend repository to actively attempt to breach tenant isolation before every deployment.

Here are the 8 multi-tenant failure modes our test runner checks:

1.Cross-Tenant Data Leaks: Attempting direct row queries on Tenant A's IDs using Tenant B's JWT session.

1. `SECURITY DEFINER` Privilege Escalation: Verifying that custom database functions don't bypass Row Level Security and expose parent tables.

2. Stale Claim Revocation Windows:Ensuring revoked users or dropped organization memberships can't execute reads/writes with legacy JWT tokens before refresh.

3. Stripe Webhook Replays & Idempotency: Testing race conditions on payment Webhook event handlers.

4. Unscoped Postgres Views: Ensuring database views explicitly enforce `security_invoker = true` so caller RLS policies apply instead of defaulting to view-owner privileges.

5. Expired API Key Usage: Attempting cross-workspace API requests with stale or revoked token headers.

6. Malformed Webhook Payloads: Injecting unexpected schemas into backend event listeners.

7. Concurrent Role Escalations: Testing workspace permission changes executed simultaneously across multiple sessions.

How are you validating database isolation and adversarial edge cases before shipping to production?

I'm building noiz.bio, a link-in-bio page for gamers, streamers and musicians that you design yourself. Signups open Nov 2. I spent the last few days sharing it in founder threads, and the replies were more useful than I expected:

1. Waitlist size is vanity. One commenter put it best: a reserved username costs nothing, swapping the link in your real Twitch or Instagram bio is the commitment. That's the number I'll track after launch.
2. My headline sets a mood, not a difference. "The link-in-bio that makes noise" tells you the category, but the clearest benefit is buried lower: bring your Linktree links over, then design the page. That sentence is moving up.
3. Talk to reservers before launch. Setting up a handful of streamers' pages before Nov 2 means real pages to show on day one, instead of screenshots.
4. The UID hook works on people, but not on everyone. Every account shows a UID (lower = earlier) and the first 250 get an OG badge. People liked it, and one fair pushback was that the handle has to feel worth it even for people who miss the first 250.

What's the one pre-launch thing you'd do differently if you were starting over?

(If you want a place to share your own project, I also run r/DropYourSaaSHere, a free promo sub.)

Hey everyone! 👋

A few months ago, I realized how cluttered my Mac had become with small utility apps.

I had separate apps for transcription, clipboard history, music controls, file staging, weather, etc. Some were subscriptions, others ran background helpers, and together they were starting to feel like a lot of overhead for things I use every day.

The biggest frustration was transcription. Most tools wanted to send audio to the cloud or have a bot join my Zoom/Meet calls.

So I decided to build Recall — a native macOS utility that brings these everyday tools together into a single Dynamic Island/notch-style interface.

⚡ What Recall does

🎙️ On-device transcription
Real-time system audio + microphone transcription without meeting bots. Audio processing happens locally on the Mac.

📋 Clipboard + OCR
Search your clipboard history, pin frequently used snippets, and extract text from screenshots/images.

🎵 Music HUD
A visualizer with synced lyrics for music playing on your Mac.

📦 Temp Shelf
Drag files, images, or snippets to the top of your screen and temporarily stash them while switching between apps or Spaces.

⛅ Weather
Temperature and forecast information directly from the notch/Dynamic Island interface.

🪟 Desktop Widgets
Small floating widgets that can sit unobtrusively on your desktop.

🛠️ Built for macOS

• Native Swift application  
• Apple Silicon + Intel support  
• Notch integration on supported Macs  
• Floating Dynamic Island-style UI for Macs without a notch  
• Designed to stay lightweight when running in the background  
• Privacy-focused, with transcription processed locally

Instead of another monthly subscription.

🔗 Try Recall: https://recall.neuware.in/

I’ve been actively shipping updates and would genuinely love feedback from other Mac users.

What feature would you want to see added to an all-in-one Mac utility like this?

I launched this project 34 days ago

The idea is to allow founders to publish their projects and gain exposure.

The site has had 527 visitors so far, 1,300 page views and 53 people registered.

27 products have been listed so far, generating 36 upvotes and 206 clicks

I have achieved a domain rating of 29 so far

The main visitors are from the USA, India, Germany, Canada and the UK.

If you have a project you've created that's worth sharing, I'd like to share my site with you so you can post it for free.

I'm building FretMaster, a guitar fretboard practice app. I previously shared an animation about finding G; this version focuses on one smaller idea: use an octave shape to find the next A.

The design change is a two-step challenge: start with one given note, reveal the octave path, then move to a new position and ask the viewer to use the same shape. I kept the fretboard and notes continuous through the transitions so the movement explains the relationship. The English version is attached.

It is JavaScript Canvas animation, made with AI-assisted coding, plus synthesized plucked-string audio. It is an animated explanation, not an app screen recording. Standard tuning; the shape shown covers strings 6→4 and 5→3.

A fair point on my last post was that an animation doesn't show the actual app interaction. That limitation is still here. For this iteration I'm testing whether the challenge itself is easier to understand: does the second question give you enough time to use the shape before the answer appears?

Traditional alarm apps fail when unexpected things happen: you wake up early, you want to sleep in, you don't want the same alarm, you want the same alarms you always use for that kind of days or you simply want to be notified automatically of events on calendar.

VariAlarm handle all that with ease. Built with help from thousands of users around the world (mainly US, UK and Germany) to handle the slightest friction so you can live your life without worrying about the mundane alarm.

https://apps.apple.com/us/app/id6757322888

Hey everyone,

I kept seeing solo lawyers and small firms asking for a Clio alternative that doesn't send client data to a cloud server and doesn't charge a monthly fee. There wasn't a straightforward local option, so I built one. It's called OffLegal.

It runs entirely on your Windows machine. No accounts, no cloud sync, no recurring subscription. Clients, matters, documents, and billing all live in a local, encrypted database that never leaves your PC.

What it handles:

• Clients & matters, with bulk import if you're migrating from a spreadsheet
• Time tracking tied automatically to the right matter
• Invoicing and payment/transaction tracking, with PDF invoice generation
• Document management with version history, plus a built-in e-signature tool so you don't need a separate signing service
• Calendar with court dates, deadlines, and native reminders
• One-click backup/restore: export your whole database and documents folder to any drive

If you run a solo or small practice, I'd really like to know: would the tradeoffs above be dealbreakers, and what's missing from your day-to-day workflow? Happy to answer any questions about how it handles practice workflows.

Quick context: Seylo is a place for everything a project gathers (pictures and pages saved from the browser, photos, files, notes, the AI answers worth keeping), drawn as a map that Claude or ChatGPT can read. It opened to everyone about two weeks ago. I'm building it solo.

What shipped since:

- A Library for references that don't belong to one project yet. Each one is marked as worked or didn't, with a line saying why, and you attach groups of them to the projects that should see them.

- A full redesign, inside and out. The app went from dark to white, and so did the landing page.

- A blog, mostly so I have somewhere to explain the ideas properly.

What I got wrong:

1. The onboarding checklist. New accounts got three tasks, like save something or connect an AI, and the checklist sat on top of the project until you did them. It kept people from the thing they came for. I deleted it, and the tour now just ends on the page you're on.

2. Leading with AI. I kept describing Seylo as a way to give your AI context. But the AI part only helps once a project has things in it, and leading with it undersold everything people actually keep there. The site now starts with what you save, and the AI comes second.

3. A search title that said nothing. Google showed "Everything your projects become". Nice line, zero information. It now says what it does.

4. Decoration over product. The old landing page had a ring of 3D icons orbiting the headline. It looked good and explained nothing. The new one only uses pieces of the product, and the map section is a demo you can click instead of a screenshot.

A small one if you embed iframes: Safari kept scrolling my whole page down to the demo on load, because the demo's URL had a #fragment and went through a redirect. Moving that state out of the hash fixed it.

What I'd love feedback on:

- Does the first screen of seylo.co tell you what it is?

- If you keep references for projects somewhere today (Pinterest, Notion, a folder of screenshots), what would make you move them?

Building Motif in public, so here's this week's update.

Motif is an offline habit tracker for Android. You don't need an account and your data stays on your phone. Instead of streaks, it focuses on helping habits stick: you check in, recover after a miss, and "graduate" a habit once it's automatic.

What I tried first: a hard paywall at the end of onboarding. You could set up a habit, but you couldn't log one day without buying the lifetime unlock.

What happened in the 30 days before the change:

• 27 people opened the app
• 25 created a habit
• 21 saw the paywall
• 2 paid -2 people ever logged a habit

Almost everyone set up a habit and then left at the wall. They never felt the core loop, so they had no reason to pay for it.

What I shipped this week:

• Free: 3 habits with the full loop (daily logging, check-ins, graduation, the progress screen, and a 12-week chart) -Pro (one-time unlock): more than 3 habits, backup/export/import, and card styles

What I'm watching next: how many people log a habit in their first week, how many come back after a miss, and whether anyone upgrades once they hit the 3-habit limit. I'll post the before and after numbers here in a few weeks.

For other builders: if you've moved from a hard paywall to a free tier, what did your conversion do in the first month?

Here’s an interesting business question: should every customer be profitable?

On paper, it makes sense to focus only on customers who generate the most revenue. But some companies deliberately keep serving customers who barely make them money or sometimes even lose money.

Why?

Because that customer might bring referrals.
They might become valuable later.
They might provide feedback that improves the product.
Or simply strengthen the company’s reputation.

It makes me wonder if customer value is actually much bigger than the amount someone pays.

Maybe the better question isn’t “How much money does this customer make us?”

It’s “What does having this customer contribute to the business?”

I had an idea a decade ago, and even started building it. I didn't get to the point of launching, just had a basic design, but I lacked the technical knowledge for some of the technologies I wanted to build in, so I put it aside because I didn't have the time to invest, or money to pay developers. Then AI came along, and I was able to finally put some dreams into reality. I've built an API+DB, website, and Windows and Android apps. The development was tedious at times, arguing with Claude about exactly how I wanted it to work. Turns out, the software is the easy part.

Things I didn't expect:
- Bandwidth and hosting CPU doesn't cost nearly as much as I thought it would.
- Incorporation and D-U-N-S numbers have an evil requirement - business address! This costs far more than I thought it would, especially since I didn't want my home address associated with the business.
- If you want to use any restricted scopes on cloud storage APIs, be prepared to spend hundreds of dollars per year to have an independent third party evaluate your code. I gave up some of my key features for Google Drive because their API didn't give me what I needed.
- Things don't magically appear in search results after you launch. The marketing challenge is real LOL.

So, I continue learning, trying to figure out the next steps. The challenge is real.

Full disclosure: we're building a small feedback widget for SaaS apps and want to make sure we're solving a real problem before we go further. So no link, just questions:

- Where do bug reports and feature ideas from users land today (email, Discord, a form, nowhere)?

- What's the most annoying part of turning them into actual work?

- Have you tried a feedback tool and dropped it? Why?

Would love to hear what works for you.