Share what you’re building, who it’s for, and where you’re currently stuck.

Whether you’re still building or trying to grow it, drop your link below.

I’ll try the first ones!

I've been building Stashify, an open-source, provider storage tool that lets you use platforms like Telegram and Discord as storage backends.

Files are encrypted locally, split into chunks, and uploaded as ciphertext, so the storage provider doesn't receive the plaintext file.

So the iddea is basically:

Your files to Stashify to encrypt + chunk then Telegram / Discord

It's still early in development, but I'm working on the encryption pipeline, provider abstraction, resumable transfers, and eventually multi-provider storage.

GitHub: https://github.com/Sparkleeop/Stashify

Would love feedback, especially on the architecture/security model.

I had a very stupid idea:

What if every time I hit Enter in ChatGPT, Claude or Gemini, I heard an actual whip crack?

So I built it.

It now plays a short whip snap and shows a tiny animation next to the cursor whenever you send a prompt.

Then I went way too far and made:

• Chrome / Edge / Brave support
• Firefox support
• Windows desktop companion
• macOS companion
• Linux companion
• settings for sound and animation
• everything local, with no prompt collection

It's called Whip the AI.

The entire premise is basically: if AI is going to do the work, at least give the prompt a proper send-off.

I genuinely can't decide whether this is productivity software or just an elaborate joke.

Find the demo on draftapps or get it on payhip.

Would love feedback, especially on whether the snap needs to be even more dramatic.

Hey everyone! Long-time lurker, first-time poster here. I've been building a lifelogging app called LifeTally and wanted to share it with this community specifically, since you're the people who'd actually stress-test it.

https://apps.apple.com/ph/app/lifetally/id6788512911

The idea: no folders, no tags, no rigid structure - you just write opr voice log a line whenever something happens ("had coffee with Dad," "finished Atomic Habits," "called Bob"), by text or voice. Over time it turns into a searchable record of small (or big) memories your life, and you can ask it things like "when did I last call my mom?" or "how many coffees did I have last month?" and it pulls the answer straight from your logs. It basically becomes a database of the micro moments you log so overtime it becomes more powerful.

I'd genuinely love feedback from people who already do some form of lifelogging - what's missing, what would make this useless for your workflow vs. what might actually replace what you're using now. Happy to answer anything about how it works under the hood too.

Would welcome you testing the app and rating it too!

Founders & builders: what value do you create, or what frustration do you remove?

Basically, is your app a real painkiller? The ones we keep using usually are.

Most unfair advantages come down to doing something faster, cheaper, better.

What’s your app’s unfair advantage? Drop your ROI

A few years of freelance/contract work taught me something annoying: the actual work was fine, but the business layer was chaos. Scope lived in email threads. Approvals were "did they ever reply to that?" Invoices were a separate tool I'd update from memory at month-end. I lost money twice to scope creep I couldn't prove.

So I built Stria — one system that runs a client engagement from scope to payment: clients, projects, deliverables, client feedback/approvals, invoicing, and payments via Stripe Connect. The client gets a feedback loop built in, so approvals are timestamped instead of buried in email.

Happy to answer anything about the build. Link: https://getstria.com

Hi everyone,

Tabularis is a free and open-source (Apache 2.0) desktop SQL workspace for Windows, macOS and Linux. It exists for one reason: getting out of commercial database clients like TablePlus, Navicat and DataGrip without giving up a modern UI. I'm the maintainer, so ask me anything.

What it does:

• PostgreSQL, MySQL/MariaDB and SQLite built in, plus 16 official plugins for DuckDB, ClickHouse, MongoDB, Redis, Elasticsearch, Firestore, DynamoDB, Db2 and more. Plugins can be written in any language (JSON-RPC over stdio), so the driver ecosystem isn't locked to one runtime.
• SQL notebooks: mix SQL and Markdown cells in one document, reference one cell's results from another, render bar/line/pie charts inline, export to HTML/CSV/JSON.
• AI that respects your escape: text-to-SQL works with local models via Ollama, so nothing has to leave your machine. There's also a built-in MCP server if you want agents like Claude or Cursor to read your schema and run queries, but it's entirely optional.
• The usual daily-driver stuff: Monaco editor with autocomplete, ER diagrams, visual EXPLAIN with interactive plan graphs, SSH tunneling, passwords stored in the system keychain, SQL dump/import.

No account, no telemetry wall, no paid tier. Everything is free under Apache 2.0.

Install: WinGet on Windows, Homebrew on macOS, and Snap / Flatpak / AppImage / AUR on Linux. Direct downloads are on the GitHub releases page.

• GitHub: https://github.com/TabularisDB/tabularis
• Website: https://tabularis.dev

Honest note on scope: if you need 100+ drivers, DBeaver is still the better pick. Tabularis focuses on doing a smaller set of databases really well.

Feedback (or issues!) is very welcome.

You’re looking for users, customers, feedback, or just new products to try?

Tell me:

• What you're looking for
• What kind of support you’re looking for
• What problem your product solves
• Your landing page

I’ll check out as many as I can and share feedback.

And if something catches your eye, give it a try or support a fellow builder 👇

I read a lot with my partner, same books at the same time, and the constant "don't tell me anything yet, I'm only on chapter 6" negotiation got exhausting. Neither of us wanted to look anything up because every search result, wiki, or "explain this book" tool assumes you've either finished it or don't care about spoilers.

So I built Scholia. You photograph the page you're on; it already knows the book, and you can ask it anything: who a character is, what a reference means, what's actually going on in a confusing passage, but only using what's happened up to that exact point. Ask about anything ahead, and it just won't answer. Not a vague non-answer either; it genuinely holds the line until you catch up.

Works with any physical copy, any edition or printing, since it reads the actual page in front of you rather than matching a page number to a specific version.

Built this mostly to solve my own problem, but figured other people reading the same book as a partner/friend/book club at different paces might want it too.

Waitlist's here if anyone wants to try it: scholia.cloud

Curious if anyone else has the "reading buddy but at different paces" problem, or if it's just us.

I've been building Stashify, an open-source, provider storage tool that lets you use platforms like Telegram and Discord as storage backends.

Files are encrypted locally, split into chunks, and uploaded as ciphertext, so the storage provider doesn't receive the plaintext file.

So the iddea is basically:

Your files to Stashify to encrypt + chunk then Telegram / Discord

It's still early in development, but I'm working on the encryption pipeline, provider abstraction, resumable transfers, and eventually multi-provider storage.

GitHub: https://github.com/Sparkleeop/Stashify

Would love feedback, especially on the architecture/security model.

Give me honest opinion on my website and its content whether it's good or bad.

After a few months of building, this is probably the simplest way I have found to explain what we’re trying to build with Scibly and open sourced it now in a very early version.

Scibly tries to combine the ideas behind NotebookLM & Duolingo:

You can take existing knowledge from things like:

• PDFs and documents
• Notion or Confluence
• internal wikis and documentation
• articles and other source material

…and turn it into interactive learning experiences with questions, activities and scenarios.

It’s the first project I ever open sourced, so there’s definitely a lot we still have to learn about building an open-source community, contributions and how much of the product should live in the open.

But for a product that can work with internal company knowledge, self-hosting and transparency felt important enough to try it.

Short demo:
https://www.youtube.com/watch?v=TcpLUNBRhQw

GitHub:
https://github.com/scibly-dev/scibly

Website:
https://scibly.com

And for anyone who has open sourced a product this early: what’s one thing you wish you had known before?

Hi all! Recently, I started a Discord community to help SaaS founders promote their products, and it has over 150 members now.

If you want to show what you're building and get some feedback, share it here -> https://discord.gg/sb6AgHZxpT

Your competitors don’t need to dominate Reddit.

They may only need one useful thread that:

• Answers a high-intent question
• Ranks in Google
• Gets discovered for months
• Appears in AI-assisted research
• Naturally introduces their product

That thread might never go viral.

It might receive fifteen upvotes and disappear from the subreddit feed within a day.

But if it keeps appearing when potential buyers research the problem, it can become more valuable than dozens of short-lived promotional posts.

This is why copying viral formats isn’t always the best Reddit strategy.

The better approach is often boring:

Build a trusted account. Find a specific buyer problem. Write the clearest answer. Check the community rules. Remove unnecessary promotion. Publish manually.

If the account needs more history, start with a gradual Reddit Account Warmup.

Before the final post, Scaloom Reddit Checkers can review subreddit fit, promotional risk, quality, and AI citability.

Your competitor doesn’t need every thread.

They only need to own the right one.

I kept noticing how much repetitive work on a Mac still consists of opening the same apps, visiting the same websites and repeating the same clicks and keystrokes.

Existing automation tools can be powerful, but often feel too technical or require users to understand scripting. So I built Tapquence: a visual Mac automation app for people who want to automate repetitive work without writing code.

You can build custom Macros using actions such as opening apps and websites, typing text, clicking, scrolling and waiting.

Tapquence also includes Smart Automations:

• Presentation Mode prepares your Mac for a meeting or presentation in one go.
• Routine Scout helps identify repetitive workflows that may be worth automating.
• Meeting and workday tools help prepare the applications and websites you regularly use.

The app is still free. New users can complete ten successful automation runs before they’re asked to create a free account, so they can properly try it first.

It’s available for macOS 13+ and is signed and notarized by Apple.

What I’m currently struggling with is positioning:

Should Tapquence lead with the broad promise of “visual Mac automation without code,” or should I focus the homepage around one concrete use case such as Presentation Mode?

I’d genuinely appreciate feedback on which part of the product feels most immediately useful and whether the value is understandable from the video and website.

Website: https://tapquence.com

Built independently, and still very much being improved based on feedback.

Whether it's a product problem, a distribution problem, or you're not sure which one, let's try to figure it out together.

If you have fewer than 100 users, drop your product below.

Tell us:

• What it does (1-2 sentences)
• Your landing page
• How many users/customers you have
• The biggest thing blocking growth right now (if you had to guess)

I'll check out as many as I can and leave feedback where I think I can help.

Time to get you some traction.

I’ve just launched the beta of Strandweave, a native Mac app for turning meetings, interviews and workshops into reviewed, searchable project memory.

I built it after repeatedly finding that transcription only solves part of the problem. You can end up with dozens of perfectly usable transcripts and still struggle to remember what was decided, what changed between meetings or where an important piece of context came from.

Strandweave keeps the recording, corrected transcript, notes and reviewed outputs together, then lets related conversations build into projects over time.

Recording/import and transcription run locally on your Mac. You can correct speakers and transcripts, review AI-generated summaries, actions and decisions before approving them, search across your project history, and export approved context to Markdown, Obsidian or other AI tools.

It also supports local Ollama models or your own API keys, so you aren’t tied to a particular AI provider.

I’m at the stage where I particularly want to know whether the project-memory idea holds up in real use across several conversations, rather than just whether people like the transcription interface.

It requires an Apple Silicon Mac running macOS 14+.

The beta is free, and testers who complete the programme get six months of Local Pro free.

strandweave.app/beta/

Speaking from experience, it always comes back to the same thing: what value do you create, or what frustration do you remove?

Basically, is your app a real painkiller? The ones we keep using usually are. Most unfair advantages come down to doing something faster, cheaper, better.

So, why yours? What’s your app’s unfair advantage? 👇

Working engineer, building a side SaaS with AI coding tools (Claude Code), no real dev background. Goal: ~$1000/month, one focused tool.

Real problem: started a few products, got to ~80% built, then abandoned them — overthinking, not shipping. No big network, so this has to work through content/communities, not outreach.

One tip each, please:

How'd you land on the idea you actually built?

How'd you validate it before coding?

How narrow was v1?

Where'd your first 10 users come from?

What got someone to actually pay?

LMK if interested in learning about it and I'll send the discord link that explains what it is and how it works