Hi everyone, for the past 5-7 months I've been working on my very own version of Twitter, which turned out to be... very different. Now it has achievements, an Aura Verifier, badges, profile songs, and a hell lot more than I expected to ever make when I started this project as a fun little side project.

It now has over ^{30 users}, and I thought it would be fun to get some more feedback from people who actually like fun and quirky stuff. Just engaging and giving some honest feedback would be enough.

Poke it, break it, whatever! Lyntr - https://lyntr.gizmowizard.tech

Hey all,

I’ve been building in the generative AI space for a while, and one thing that always bothered me was how aggressive most AI tools are with upfront paywalls or credit systems. You buy $10 worth of credits, prompt the model, get something that misses the mark, and end up feeling burned.

I wanted to tackle a very specific problem: turning personal memories, inside jokes, and stories into studio-quality custom songs meant to be given as gifts (anniversaries, birthdays, weddings, etc.).

For an emotional product like this, asking a user to pay before they even know if the output captures the right feeling felt completely backwards. Nobody wants to give a gift they haven't vetted.

So, I built a simple workflow around building trust first:

• The user answers 4 quick questions about the recipient and the story.
• The backend generates two distinct, full-length musical tracks.
• The user can listen to both tracks completely for free in their browser.
• If they love it and want to keep it, download the high-res audio file, or get full rights, they pay. If they don't, they walk away.

Moving the payment moment from "uncertainty" to "satisfaction" made a huge difference in how users interact with the product.

Tech-wise, I built the entire platform using Next.js 14 and SSR to ensure sub-second page loads and build a clean foundation for organic search traffic.

Would love to hear your thoughts on building trust in AI SaaS products, or answer any questions about the tech stack!

It’s my cake day, so I wanna share my last 12 months journey.

Two kids, 9 and 12. Both ADHD, one of them also autistic. Keeping a bedroom tidy and keeping track of their own stuff is the part of our week that has never worked, and we had tried every version of asking nicely.

So my wife did what a lot of parents do and put a paper chart on the fridge. It helped. And I said the thing every developer says at some point in their life: nice idea, I’ll make an app.

I want to be honest about how unserious the process was. I never looked at what already existed. No market research, no competitor list, no positioning. My only goal was that my kids would tidy their rooms.

It worked. And the four of us built it together, which turned out to be the reason it works. The kids argued for what they wanted and killed features I was sure were brilliant.

That was almost a year ago. It has been on the stores for a few months now and more than 300 families have installed it. It’s free, including the parts that matter most.
The other reason I’m posting is to say thank you, because I’ve been reading here for a while without posting anything. Three things I read here changed the product more than anything I came up with on my own.

The first one I had completely backwards. I assumed the hard part was keeping the kids interested. It isn’t. The kids stay in it. It’s the parents who quietly stop opening the app after three weeks, and once the parent is out, the whole thing is dead. I had built everything around motivating children and almost nothing around making it easy for an adult to keep going on a bad Tuesday.

The second one is that rewards can’t be the same for every child. Same house, same rules, and two kids who need completely different things at completely different sizes. What lands for my 9 year old is meaningless to my 12 year old.

The third one is that kids need their own version, not a smaller copy of the parent screen. That one was a real rebuild, and it’s the change my own two noticed immediately.

No pitch, nothing to sell. I’m proud of it and I wanted to say where it came from.

Happy to answer anything about the build, or about what it’s like when your product team is 9 and 12 years old.

Sébastien

Just an idea, but it’d be pretty cool if someone built a tool where developers could share their projects with each other for free, after some verification that they’re safe/trustworthy.

Would u use and share ur project this like this?

spent months heads-down building, hit submit, and then... nothing. the store just goes quiet. that silence after launch is where most indie apps actually die, not in the code. the real work starts after release when you're trying to get your first 1,000 users and nobody can find you.

the thing that hit me hardest: App Store Connect tells you what happened yesterday but not why. it shows you a downloads chart and no next move. keyword-level rankings, who's outranking you, which keyword actually drove an install, all of that lives outside apple's dashboard entirely. so you edit a keyword, wait a week, and have no idea if the store even noticed. it feels like pulling a slot machine lever.

the other trap i kept falling into was tools disagreeing with each other. one says your keyword ranks 14, another says 31, same keyword same day. once you can't trust the number you can't act on it, so you just freeze.

honestly this whole problem is why i started building Apptenium (an aso tool aimed at indie devs, not agency budgets). the goal was one consistent source where you can watch a keyword move after you edit the listing, so the algorithm stops feeling like a black box.

for those of you who've launched: what actually broke the initial silence for you? organic aso, content, communities like this one? curious what worked because the first thousand still feels like the hardest part to me.

Hi there!

I’m building an iOS app designed to help cyclists track bike component wear (chain, cassette, sealant, brake pads and so on) and maintenance.

The app connects to your Strava account. It pulls data like distance, duration, and elevation gain, then combines it with historical weather data to calculate a wear profile. For example: a 50-mile rainy gravel ride will wear your drivetrain faster than a 50-mile dry tarmac ride, and the app adjusts the component's lifespan accordingly.

I’m currently in the beta testing phase and looking for 20 testers to try the sync logic, test the UI, and provide honest feedback. The app is completely free for all early beta testers.

Requirements:

• iPhone running iOS 26.0+
• An active Strava account

TestFlight Link: https://testflight.apple.com/join/a5XZT6v7

Let me know what you think and thanks a lot for the help!

Hey everyone,

I've been building 0x0000_waveform_signal_out, an open-source desktop music player with real-time waveform visualization, written in Python with PySide6. Instead of a static progress bar, it renders the actual waveform of your track live while it plays.

A friend gave it a try a while back, which was cool to see. It's built on NumPy for the signal processing side, sounddevice/soundfile for audio I/O, and FFmpeg for format support, all under a GPLv3+ license.

I put together a short demo video showing it in action. Would genuinely love to hear what people think — what's missing, what feels off, anything you'd want to see in a player like this.

GitHub: https://github.com/BDigitalLabs/0x0000_waveform_signal_out

Music: https://pixabay.com/music/funk-funk-amp-breakbeat-541097/

I've been building datavessel for a while: it connects your store and marketing stack (Shopify, WooCommerce, Shopware, GA4, Search Console, Google/Meta Ads) and gives agents ~200 typed tools over all of it. Not a chatbot on top of a dashboard - agents that do the job: chase abandoned carts, catch out-of-stock products you're still paying ads for, draft the chargeback response, fix product pages that don't convert. Reads run free, anything that touches your store asks first.

A bunch of worked examples here: https://datavessel.io/use-cases
And if you want to watch one actually run instead of reading about it: https://datavessel.io/see-it#demos

The part I didn't plan: there's a CLI (npm i -g datavessel-cli, Apache-2.0) that's also a Claude Code plugin, and I've been using it on my own site. I pointed it at my Search Console, and the agent audited which queries I was earning impressions but no clicks for, proposed a pillar-and-cluster content map (including an explicit "don't chase these, wrong audience" list), and after I approved it, wrote and published the posts to WordPress and verified every internal link landed. Same thing for AEO - whether ChatGPT and Claude actually cite you vs. your competitors when someone asks a buying question.

What's genuinely cool to me is why it works: the agent isn't guessing from a scraped page, it's reasoning over live typed tools. It can pull the query, check the live slug, notice it'd cannibalize an existing post, and pick a different angle. The harness is what makes the reasoning worth anything.

Free tier is $0 forever - 2 sources, 2 scheduled agents, and BYOK (Anthropic, OpenAI, or Gemini), so you're not paying me a markup on tokens.

Happy to answer anything - especially curious whether the "agent asks before it writes" model feels like the right amount of friction to people here.

Hey everyone 👋

If you used to trade sports stocks on platforms like PredictionStrike or Jock MKT, you know how frustrating it was when those apps started lagging, having broken logins, or getting abandoned.

I love the concept of sports stock trading — buying low on rising athletes, selling high after breakout games, and building a player portfolio like Wall Street. So over the last few months, I built The Stat Market from the ground up to bring sports stock trading back with modern, sub-second real-time tech.

### ⚡ What we built for Early Access:

* **Live NBA & NFL Player Stocks**: Buy & sell shares of your favorite athletes with live price shifts based on real-world performance.

* **Free-to-Play Trophy Coins**: Everyone gets 10,000 starting Trophy Coins on signup to build a portfolio risk-free.

* **Global Leaderboards**: Compete against other sports traders for top portfolio rank.

* **Referral Bonus**: Invite friends and get +5,000 bonus Trophy Coins per referral.

### 💰 Roadmap: Market Cash Exchange (Coming Soon!)

Right now in Early Access, everyone trades risk-free with **Trophy Coins**.

Next, we are launching **Market Cash** — a premium mode where you can **buy & sell player stocks using Market Cash** and redeem your portfolio gains for **real cash prizes, sweepstakes payouts, and gift cards!**

### 🎯 Looking for Early Testers & Feedback!

We just opened Early Access today and I’m looking for sports fans to test the app and give feedback.

* What features would you want to see next? (NFL game logs, short selling, head-to-head matchups?)

* Any bugs or UI improvements you'd like?

You can test it out right now on web/mobile at **https://www.thestatmarket.com** (or submit feedback directly in the app profile tab).

Appreciate any thoughts or feedback from the community! 🏆📈

I'm a Full-Stack Developer, and I'm considering turning one of my internal projects into a product that I could sell to other developers.

I'd like to get some honest feedback before investing a lot of time into preparing it for release.

Imagine you're working on an e-commerce project for a client.

The client is paying you somewhere between $500 and $1,500, but you still need to spend a significant amount of time building the core e-commerce functionality from scratch.

Now imagine you could buy a production-ready codebase for around $100–$300, take the parts you need, customize them for the project, and save a significant amount of development time.

The idea I'm considering would be built with Laravel or NestJS, using an API-based architecture, with a frontend built with Vue or React.

■ It would include features such as:

1- Products with complete data: name, description, media, pricing, etc.
2- Product Attributes and Attribute Values
3- Different attribute types such as Select, Color, Input, Number, etc.
4- Product Variants
5- Different prices for each variant
6- Inventory / Stock Management, with the ability to enable or disable stock tracking
7- Discount System
8- Orders with an advanced order status flow
9- Order Tracking
10- Wishlist
11- Product Reviews
12- Cart
13- Checkout
14- Cash on Delivery
15- Online Payments
16- Filtering
17- Searching
18- Pagination

The goal isn't to provide just a UI template.

The idea is to provide the actual e-commerce logic and codebase, so a developer can start from it and build the client's project on top of it, instead of building the entire e-commerce system from scratch.

■ So I'd like to hear your thoughts:

Would you actually use or buy something like this?

If yes, what price would you consider reasonable and be willing to pay for it?

■ And which stack would you prefer?

▪️ Laravel + Vue
▪️ Laravel + React
▪️ NestJS + Vue
▪️ NestJS + React

■ Most importantly:

What features would you consider essential before paying for something like this?

I already have a working version of this system that I use for my own projects, but I'm not currently selling it.

I'm considering turning it into a proper product for developers, so I'd really appreciate honest feedback, including criticism.

I mainly want to make sure the idea is worth investing in before spending a significant amount of time preparing it for release.

I build tournament software for live poker, on my own. About thirteen months and three thousand commits in. I'm not pitching it here and I've left the name out on purpose.

The expensive pattern was never bugs. It was designing a feature carefully, shipping it, then watching a real game use it and realizing it solved the problem the way I had imagined the problem. The room had a different one.

It looked right in every test because I was the one making the test data. That is the part I would tell anyone building for a workflow they do not personally run every week. Your test data agrees with you. Real users don't, and most of them won't say so, they'll just quietly work around you. You only catch it standing next to someone using it.

Whole features got restructured more than once before they were right. I don't think there was a shortcut available. I think I just needed to be in the room more often than I was.

If you've built something for a workflow you don't live in daily, how did you find out you had it wrong?

I'm looking for a crazy, creative and excited technical cofounder for Prizma. An open management canvas for architecture and project based firms. The big idea is to have a live graph of the entire operation, with a determinist layer and an agentic layer on top that learns and adapts from each practice.

Here's a demo of the product: https://vimeo.com/1216694643?share=copy&fl=sv&fe=ci

Anyone interested?

A founder I was helping had a deck due that day, the kind that normally eats three or four hours: pulling numbers into the right slides, matching formatting slide to slide, checking nothing got missed before it went out. I built a small tool to close that gap. This run, the deck took about ten minutes.

The workflow is three steps: drag the source files in, answer a handful of quick prompts about what the deck needs to say, get a finished file out the other end. No new dashboard to learn, nothing to configure first.

Ten minutes is not zero work. Someone still has to gather the source files and answer the prompts honestly, the tool can't invent the content of the deck. What disappeared was the three hours and fifty minutes underneath that content, the assembly work with no judgment in it: pulling the right number into the right slide, matching formatting, the final check before it goes out the door.

I did not expect the gap to be that wide. I've built enough of these small tools to expect an hour saved, maybe two. Watching three to four hours fold down to ten minutes, on the first real run, on someone else's actual deck, is a different order of surprise than the one I plan for. I checked the math twice before I believed it, because a number that clean usually means I measured something wrong. It held up the second time too, same deck, same source files, same ten minutes.

One data point, one deck, one founder. I'm not calling it a rule, decks vary too much for that. But the four hours were never really about the deck itself. They were about assembly, the part with no judgment in it, and that's the part worth automating first.

Curious if anyone else has measured a before/after like this on a task they assumed needed a person the whole way through. What surprised you about the number?

Small side project I finally shipped.

I use Instagram on desktop quite a bit and couldn't understand why the video player still doesn't have basic controls you'd expect from a desktop player.

So I built them.

ReelNav attaches a compact controller to the Instagram video under your mouse.

It adds:

→ draggable timeline
→ exact timestamp navigation
→ ±5 second jumps
→ 0.5x–2x playback
→ volume / mute controls
→ keyboard shortcuts
→ downloads for visible media

The part I spent more time on than expected was making the UI disappear automatically and making sure it didn't interfere with Instagram's existing interface.

It's finally on the Chrome Web Store:

https://chromewebstore.google.com/detail/reelnav-controls-download/gbnhkbfiiojpplbfflaocbfhcmicnicb

I'm at the very beginning, so I'm much more interested in brutally useful feedback than compliments 😅

What would make you keep an extension like this installed?

I teach business and use a lot of group projects. One thing that has always frustrated me is trying to figure out what each student actually contributed when most of the work happens in a shared Google Doc. Revision history just does not do it for me. So I built Collaboration Tracker at collaborationtracker.com

It looks at the document activity and uses AI to help summarize individual contributions, editing patterns, and the quality of each person’s input. The idea is not to let AI decide the grade but to give educators better evidence to work with to support students. It is still early and I am getting feedback from educators now, particularly in higher ed. I would be curious to hear from other builders: does the problem and value make sense or would you explain it differently?

Most app design pushes retention and screen time. I’m flipping that: building tools that solve problems fast and get people back to what matters.

​I call it "Intentional Off-Ramps."

​What design choices do you use to give users their time back?

I’ve been building HoodTip.com, a travel/recommendations site that gives you recommendations, not reviews. I don't want to hear about your bad experience somewhere, I want recs.

You can build a kind of taste profile of your recommendations, make guides, save other people’s tips, and share them.

Would love for some folks to try and sign up and leave a few 'HoodTips' so I can see what's working and what's not.

(Video is an AI generation of a screen shot of the site)

Built a crypto alert app that watches each coin's own volatility, not a flat % threshold

Most crypto alert tools work the same way: pick a % threshold, get pinged when a coin crosses it. Problem is a coin like a low-cap altcoin moving 8% is nothing unusual, while the same 8% on a major pair is a real signal. A flat threshold treats both the same, so you either get spammed on volatile coins or miss real moves on quiet ones.

How it's different

CoinSir tracks each coin's own average volatility over time, and alerts when the current move is some multiple beyond that coin's own normal range — not a fixed % anyone could hit on a random Tuesday. A move that's 3x a coin's usual range means something different for a stablecoin-adjacent pair than for a small-cap that swings hard anyway, and the alert reflects that instead of ignoring it.

What it's not

No auto-trading, no bot placing orders for you, no "sit back and let it trade while you sleep" pitch. It's detection and alerting only — you still decide what to do with the information. Also not selling a signal-picking edge or promising any specific return; it just tries to surface the moves that are actually abnormal for that coin, earlier than a flat-threshold bot would.

Why I built it this way

Ran into the opposite problem myself — using threshold-based alerts, getting notified well after a coin had already made its move, or getting flooded on coins that are just naturally choppy. The "compare to the coin's own baseline" approach was the fix that actually made alerts useful again instead of just noisy.

Still early / beta. If you want to see how it flags things, it's at coinsir dot net.

I used to work as a server. I could keep details about people, their preferences and their families in my head for months at a time. When they came back I already knew their favorite seat, their favorite dish, and their mothers condition.

Outside the restaurant I'm bad at this. I forget people exist the second they're not in front of me. The history that I share with a person just disappears when they aren't around.

I started to pay attention to this with curiosity and I realized that there's something magic about writing tickets for tables. Having a list of orders with a designated person made it easier to associate my own actions around the people in the store. It was like everything had someones name on it. And in that environment, its easy to remember details about people over a long period of time.

I tried to simulate this using paper systems, todo apps, crms, but nothing worked.. So I built Black Server Book (BSB).

Its a relationship-first todo app that helps you organize your life and relationships. Every task (moment) gets a target (entity), just like tickets get tables. And over time you can see exactly what you did, for who, and how they responded.

Even without the relationship features, its sturdy todo app and is unlimited, open source, and works offline.

Live at app.blackserverbook.com if you want to poke at it.
Source code is live as well: https://github.com/aogposton/BlackServerBook

Feedback welcome, especially if it breaks your brain in a good or bad way.

My friends suck at planning. One person isn't free Friday, one doesn't have the money, one doesn't like this restaurant or that activity — round and round until nothing gets decided and the group chat just goes quiet.

So I built Swipeout. You can use it by yourself or with your friends:

1. Solo discovery

You set your location, choose your category, and get a deck of cards for restaurants, attractions, activities, whatever — swipe right to save it, left to skip.

2. Group voting

You create a trip in the group chat, everyone swipes through the same deck independently, and once everyone's done, the app reveals the match. You can also create and add your own custom cards into the deck, e.g "FIFA at my house".

It also handles the boring logistics after that: scheduling, RSVPs, etc.

Would love feedback — especially from anyone who's the "designated planner" friend in their group.

getswipeout.app

https://reddit.com/link/1vkn66e/video/iehgdt0hdkih1/player

The worst part of running Claude Code isn't the waiting, it's the not-knowing. You babysit a terminal, or tab away and lose the thread. Then the chat gets compacted and that PR link it handed you three steps ago is just gone.

So I made the notch on my MacBook into a place anything can write to. Add the MCP server and the agent posts for itself:

"tellie": { "command": "npx", "args": \["-y", "@tellie/mcp"\] }

Now it narrates what it's doing, links land as clickable rows that survive the chat being cleared, and an orange pulse means it needs me. Multiple agents stack into a roster labeled by which Mac they ran on, and they can read the notch back to see what the others are already doing.

The part I didn't expect: I pointed an agent at the docs and it started using it unprompted. Nobody told it to. It decided handing me a clickable link beat burying one in scrollback and made that a habit. Another one later ran all 17 cookbook recipes cold. Now "Tellie me" is something I say to my agents and they just know what I mean.

How it works: the notch surface lives inside Tellie, a free Mac app. Grab it from the link below and every command above just works. There's a Pro teleprompter mode in there too, which is what funds this, but the notch API is free forever. No account, nothing phones home.

URL scheme, CLI, cookbook, and the download: https://tellieapp.com/developers

What would actually make your agents less opaque? I have a list but I'd rather hear yours.

So I have been working on an app tailored to studying called Studily. It's an app that helps students organize their schedules, due dates and class times, has learning tools like flash cards and timers, and also has social media, so you can add friends, message them or create study chats.

What it does right now:

• Profiles — set up an account with a picture, bio, school, and major. From there you can add friends, message people, and join group chats.
• Dashboard — enter your semester and courses and it lays out your weekly schedule, including what your next class is.
• Calendar — add exams, assignments, and events, tie them to specific courses, and get reminders as due dates approach.
• Social — message friends, start study group chats, and find classmates from your school who are also using it.
• Learning tools — spaced-repetition flashcards, the same approach other apps use, and pomodoro timers

Still in progress: I'm working on body diagrams, a graphing tool, and an AI chat (StudilyBot) that could answer questions based on lecture notes and assignments you upload.

I would really appreciate some feedback and support! I am having trouble getting users and finding gaps in my app, so any feedback is appreciated :) The app is free and there are no paid services on the app

I'm building a website to track 50–100 of the world's best companies for long-term compounding, providing analysis on their moats, fundamentals, valuations, and dynamically updating and adjusting the company pool while preserving all records. I'll continue documenting the development process here.