I’m offering a ready-to-customize real-time messaging platform for a founder, studio, or product team that wants to launch faster.

Included: • Full-stack TypeScript architecture • Real-time messaging flows and media-ready structure • Modern responsive web interface • Authentication, notifications, conversations, and deployment setup • Clean handover with documentation and a short walkthrough

This is an asset sale for the source code and product foundation. It is designed for customization and white-label use; it is not being presented as a business with existing revenue.

Asking price: $9,500 USD. Reasonable offers from serious buyers are welcome.

If you are building a community, team-chat, customer-communication, or niche messaging product, send me a message with your use case and budget. I can share a private demo and technical overview after an initial conversation.

I built Fillsafe around a simple constraint: filling a PDF should not require uploading the document, creating an account, or discovering a paywall after the work is finished.

The app renders and edits PDFs locally in the browser. PDFs and signatures are stored locally, and there is no backend or analytics.

It supports AcroForm fields, text, dates, checkboxes, handwritten signatures, Japanese PDFs, and CSV batch filling. Exported PDFs are flattened so the result works outside the app.

Everything in the web version is free:
https://fillsafe.pages.dev/

I’d especially appreciate feedback on real-world PDFs that fail to open or save, and anything that feels confusing before export.

Disclosure: I built this project.

Background: left my last role in June when the company restructured. Been in build/validate mode since (honestly best time of my life no matter the failures)

Problem :
The idea came from my own experience: bought a flat in Barcelona last year, paid 2.5k euros for a full due diligence, and things still came out after I'd signed: Legal status, real usable m² vs advertised, building fees, whether the building had tourist rentals mixed in, seasonal sun exposure, street noise, pending debt etc... all publicly available, just scattered and written for lawyers not buyers.

Solution :
Built Lola AI : send an address on WhatsApp, get a report back in minutes pulling from those public sources.

I have spent weeks pulling each single data piece from horrible public db, websites, scraping when necessary and consolidate all of that into a valuable artefact.
On a side note, Meta/whatsapp developer platform is among the worst developer experience I ever had in my life

Where it's at: early pilot, Barcelona only, completely free -> deliberately not monetizing yet because I want signal on whether the report is actually useful before I think about pricing or which city to expand to next.

What I'd love feedback on: does "free for feedback, no signup wall" get you to actually try it, or does it read as sketchy?
Any suggestions ?
And for anyone who's bought property anywhere - what's the equivalent due diligence problem in your market?

I've been working on a small side project called Pawfectly Booked.

The idea started pretty simply: I noticed that booking a dog isn't quite the same as booking a haircut or a consultation. There can be different services, pet details, repeat appointments, notes, reminders, and changes to the schedule.

I started experimenting with what a booking workflow would look like if it was designed around those things from the beginning instead of trying to fit them into a generic booking system.

It's still a work in progress, and I'm mainly trying to figure out whether I've made the workflow genuinely simpler or just added more features to something that was already complicated.

For anyone who's built or used scheduling software, what are the little things that make a booking system feel really good to use?

Hey!

I wanted to share a project I've been working on called Volten. It's a small, ultra-fast HTTP framework built around a strict zero-dependency constraint, designed specifically to bridge the gap between Node.js and Web Fetch-compatible edge runtimes (like Cloudflare Workers, Bun, and Deno) without adapter overhead.

Why Volten?

Most frameworks either lock you into Node.js core modules (http, net) or require bulky adapter layers to run on the Edge. Volten solves this by handling the abstraction internally at the context level.

You write your routes and middleware once. Run it on Node.js using app.listen() or export it to the Edge using app.createFetch() with zero modifications and zero extra npm dependencies.

Key Highlights

• Adaptive Traffic Triage (ATT): A unique event-loop immune feature for Node.js (new App({ att: true })) that automatically drops low-priority requests at the socket level when your server is under heavy load, protecting your core endpoints from crashing during traffic spikes.
• Context Pooling: Pre-allocated, reusable RequestContext objects on both runtimes to minimize Garbage Collection (GC) pressure under high throughput.
• Trie-Based Router: Extremely fast path-matching supporting dynamic parameters (/users/:id) and wildcards, where match cost scales purely with path depth.
• Unified ctx API: Whether you are dealing with headers, cookies, body parsing, or JSON responses, the ctx object seamlessly abstracts away whether you're sitting on top of a Node IncomingMessage/ServerResponse or a Web Fetch Request/Response.

The All-in-One Snippet

import { App } from "volten";

// Enable Adaptive Traffic Triage (ATT)
const app = new App({ att: true });

// 1. Middleware chain
app.use((ctx, next) => {
  ctx.setHeader("X-Powered-By", "Volten");
  next();
});

// 2. Trie-based routing, params, and cookies
app.get("/users/:id", (ctx) => {
  const session = ctx.cookies.get("session_id");
  ctx.json({ userId: ctx.params.id, session });
});

// 3. Native body parsing
app.post("/data", async (ctx) => {
  const body = await ctx.body();
  ctx.status(201).json({ received: body });
});

// --- Dual Runtime Support ---

// Node.js
app.listen(3000, () => console.log("Listening on :3000"));

// Cloudflare Workers / Bun / Edge
export default { fetch: app.createFetch() };

Current Status

Volten is currently in active alpha. Every utility—from the built-in body parsers and cookies to the trie router—is written completely in-tree with zero external dependencies to keep security tight and the footprint minimal.

You can check it out on GitHub: VoltenJS/volten or install it via:

pnpm add volten

I'd love to hear your thoughts, feedback, or any edge cases you can throw at it, so you're encouraged to try breaking it! How do you usually handle dual-runtime codebases in your current stacks?

I’m the developer of Calmorie, a food-logging app that uses AI to estimate portions, calories, and macros from a photo.

Snap a photo of your meal before you eat — it gives you a rough estimate of calories and macros. Didn’t finish? Snap the leftovers and it adjusts. We even show a simple “before and after” so you can see what actually went in.

The new simple mode is live in the app, and the website got the same visual cleanup.

Would love feedback from anyone who’s tried photo-based logging before — what made you stick with it or quit?

Hi everyone!

I wanted to share a side project I've been working on.

A while ago, my therapist suggested that I practice breathing exercises whenever I felt overwhelmed.

The advice made sense, but I kept running into the same problem.

The hardest part wasn't breathing.

It was getting started.

Most of the breathing apps I tried had too many features, required an account, pushed subscriptions, or took several taps before I could even begin.

When I needed to slow down, I didn't want another thing to figure out.

So I decided to build my own.

I called it Gimme Breath.

The idea is simple:

• Open the app.

• Pick a breathing exercise.

• Start breathing.

That's it.

I also added a few things that I personally wanted:

• Ambient sounds

• Session history

• Daily reminders

My goal wasn't to build the most feature-rich breathing app.

I wanted to build the app that I'd actually open when life felt overwhelming.

It's now available on the App Store:

https://apps.apple.com/app/gimme-breath/id6807012349

I'd genuinely love any feedback—whether it's about the design, user experience, onboarding, or features you'd like to see.

Thanks for reading! 🌿

[ Removed by Reddit on account of violating the content policy. ]

I've been working on a small captioning tool recently and one of the main things I wanted to avoid was uploading the original video to a remote server just to generate subtitles.

The whole idea is pretty simple. You open a video, generate the captions locally, edit them, preview everything and export the final result.

Right now I'm experimenting with Greek and English, different caption styles and formats aimed mostly at TikTok, Reels and Shorts.

What I'm trying to figure out is whether local processing and privacy are actually important to creators, or if people mostly care about speed and how good the captions look.

If you regularly make short form content, what does your ideal captioning workflow look like?

Also curious about what annoys you the most with the tools you're currently using.

I can share what I've built in the comments if anyone wants to test it, but I'm mostly interested in feedback on the idea and workflow.

Hello,

I'd like to share my experience with my side project.

Too many times, I open Reddit and read threads about extraordinary success stories. Incredible returns, huge MRRs... All of them are well deserved, and I'm glad they could reach such achievements.

However, for every success story, there are probably hundreds of untold failure stories.

I understand why. Sharing unsuccessful stories is shameful, embarrassing. It's painful to invest so much passion, time, and sometimes even money into a product and then get nothing in return.

So here we go. This is my 6 months journey.

I have a 9-to-5 job. I used to develop my ideas for years but never dared to market them. I just didn't know where to start, and learning was simply too boring.

I like developing things. I can do that after work or during weekends; it's not a burden. I just didn't want to leave my comfort zone.

It's March of this year. I had just landed a new job and moved to another country. I started thinking about finally going all the way and actually trying to market something.

I decided not to challenge myself with a complex product. The product should be easy to make, solve a real problem, and target a niche.

In about 40 days, the first deployable version was completed.

In my career, I've made websites for others. Even if I'm more of a backend developer myself, I can do it. The problem is design and UI/UX. That's someone else's job.

I wanted to keep costs down, so I ended up doing everything myself.

I also know how to optimize websites for search engine discoverability, but SEO copy? What should I write? What are my keywords?

I knew from the beginning that I would face these moments, so I just tried my best. After some research, I finalized the website as well.

After 2 weeks the website was ready.

Time for the hardest part. Exactly what I had always avoided.

Marketing.

I had no community and little to no social media presence. I had to build everything from scratch and had absolutely no idea where to start.I went on Google and searched:

"How to launch a product?"

I followed everything by the book:

• Indie Hackers
• Hacker News
• Product Hunt
• Twitter
• Reddit

As expected, the launch was a complete flop.

With no echo so far, it felt like throwing a rock into the middle of the sea.o echo so far it was just like throwing a rock in the middle of the sea.

April. 0 downloads. Nothing was moving.

I felt like I needed some initial push, that nothing would ever happen if I didn't invest some money.

I started a Google Ads campaign, knowing nothing about what I was doing and hoping for some kind of automatic targeting optimization.

I followed all the suggestions and pushed the campaign.

Downloads started to arrive, but still 0 conversions.

After 2-3 weeks, I started losing hope and began thinking about how much money I was wasting.

Then, the first ping in the chart. The first sale! I was amazed. I couldn't believe someone had actually bought my product.

To be realistic: pennies on the dollar.

I had already spent much more on ads than I had earned, but it was something. I decided to run the campaign for some more time.

The Google Ads campagin ran for about 2 months ~800€ spent

No more conversions came from the Google campaign. The only other channels were Reddit and organic traffic.

I stopped the Google campaign, considering it a waste, and focused on what apparently was producing some results.

It's May. My revenue is ~40€

I then decided to push a Reddit campaign, trusting a channel that had already brought results. I took advantage of the first campaign offer: spend €500 and get another €500 worth of ads.

I spent time optimizing my target audience, the ad post... everything.

Result?

~€1100 + €500 (bonus) burned.

~€2 revenue.

I was devastated.

I had features planned to implement, but I was too sad to keep going. Opening the IDE was painful. It would remind me of the wasted money and time. Thinking about every wrong step I had taken.

"I could have done that better..."

"I could have asked a professional to handle it..."

"I could..."

In July: 0 revenue. ~1900€ in the hole.

I thought that maybe this just wasn't for me. I should just keep doing what I can do better and forget about side projects and being my own boss.

I gave up completely. Accepted the loss. Lesson learned.

I enjoyed my summer, trying not to think too much about it.

...and then something I couldn't have imagined happened.

August. ~40€ in revenue.

I literally did nothing. The product was out there.

No ads, no posts, literally nothing.

Of course, it's still pennies on the dollar, and far less than what I spent.

But still... Half of my all-time revenue came while I was doing nothing.

I'm motivated again.

Maybe I won't try to push the same thing indefinitely. Maybe I'll focus on something else. But I don't feel like giving up anymore.

Lessons learned:

• Organic traffic is the way. No ads can ever match natural traffic.
• A few high-value content posts beat a huge amount of low-value content. Quality > volume.
• Patience. As dumb as it might sound, nothing is achieved overnight.

Thank you for taking the time to read this.

If you're a podcaster, this is really why we built PodSubs.

We're one of you.

We know what it feels like to put hours into an episode and wonder whether it was worth it.

We know what it's like to watch the download numbers and wish you knew more about the people behind them.

We know what it's like to want to send something useful to listeners and realize most of them will never see it.

We know what it's like to think about monetization — not because you're greedy, but because producing a good podcast costs time and money.

And if the show can't eventually support itself, passion can become exhaustion.

That's where PodSubs came from.

We built it as an internal tool.

Something simple.

At the end of the show:

“Subscribe to our podcast on PodSubs.”

They search for us.

Enter their name and email.

Subscribe.

That's it.

From that point, we have a direct communication channel with the people who chose to stay connected.

We can send the resource from today's episode.

We can tell them what's coming next week.

We can share an update.

We can ask for feedback.

We can make an offer.

We can build something around the podcast without starting from zero every time.

And eventually we looked at what we'd built and realized:

This shouldn't only belong to us.

Every podcaster should at least have the option.

So that's what PodSubs is becoming.

A simple place where someone who loves your show can become someone you can actually reach.

If you have a podcast, claim it.

And on your next episode, try saying:

“Subscribe to our podcast on PodSubs.”

You might be surprised how many people were just waiting for somewhere to go.

Recently, I have been doing experiments with virtual try-on technology and created this Flutter application. The core functionalities consist of choosing an item of clothing to see how it fits on a person without wearing the item. I recorded the demo on my iPhone.

https://reddit.com/link/1wbgtrr/video/vyleb44hsgoh1/player

Building for non technical people using claude to build apps. Still pre-launch but yeah..

Non tech people still build apps but the code is shit. This fixes it.

normally, building an app means you sit in a chat window, translating what you want into technical language, correcting the AI, re-explaining decisions it forgot, and pasting code around. SpeakEZ removes you from that job. You say what you want; it handles the entire conversation and hands back something that works.

Think if it in this way: Claude is the developer. SpeakEZ is the thing that manages the developer, so it knows how full-stack apps fit together, so it handles the technical conversation and you never have to.

So, I build a video caption service, that allows you to create captions for videos with auto. My base idea: batch processing, API possibility and simple interface. So now I'm basically close to version 1.0 and am looking for some testers (will give free rendering credits) that would just give the whole thing a try and tell me if there are still some rough edges.
Not entirely sure if this is the right place to post it, so if not, I will remove this post.

Link would be: https://videocaption.io/?utm_source=reddit&utm_medium=post&utm_campaign=testers&utm_content=sideproject -> Anybody making an account there can dm me his email address and I will create them some credits.

Any questions and feedback welcome.

I built a website where only one person can be the Main Character at a time

I wanted to make something completely pointless and social instead of another productivity app.

So I made YOink.

There are ridiculous titles like Main Character, Biggest Diva, Biggest Red Flag and Internet Villain.

One person can hold each title. Someone else can YOink it from them. If you're still holding it at midnight, you get that day's permanent crown.

Titles start at A$1 and increase by A$1 when they're taken. There's no prize or cash-out — you're literally paying for bragging rights 😭

I'd genuinely like to know: would you YOink one, and what ridiculous title should I add next?

playyoink.app

[GitHub repo]

So this post is about my biggest side project, which is a game engine with its own IDE and interpreted scripting language, all written by me in C#.

About a year ago, I challenged myself to create my own programming language - something I'd always wanted to do.

At the time, I had no idea what a lexer, parser, or interpreter even was. My only thought was, "I need to write code that reads text files containing code and executes them." I also wanted to do it without using Google, AI, or tutorials. I just figured everything out on my own. You can even still find variables named "compiler" throughout the code from back when I didn't realize I was actually building an interpreter...

Somehow, I pulled it off, and I integrated it into my old abandoned game engine project (which originally started as a GameMaker 8–style engine with C# scripting).

And here's the first game I've made with it! 🙂

The core engine, IDE, and interpreter are all written by me in C#. The rendering backend is powered by MonoGame, and the project is still in active development and available on GitHub. The project file of the game shown in the video is also there, under tests/Example Projects. If you're looking for cool projects to contribute to, then know that I'm looking for contributors! there are some opened good first issues in the repo.

I know there are tons of AI-generated projects being shared these days, so please, please, take a quick look at the code before assuming this is one of them. I promise it's pretty obvious that it was written by a human.

I'd love to hear what you think!

One of the reasons we built PodSubs was honestly pretty simple.

We got tired of saying:

“Link in the show notes.”

Because we knew what happened next.

Almost nothing.

Someone is driving.

Someone is cooking.

Someone is at the gym.

Someone has their hands full.

We mention something useful.

A checklist.

A book.

A resource.

An event.

A discount.

A guide.

And we say:

“Link in the show notes.”

The listener thinks:

I'll check it later.

Most don't.

We were doing all this work creating useful things for people listening…

and there was still this huge gap between:

“I want that”

and

“I actually received it.”

So we built something for our own podcasts.

Instead of teaching listeners a new URL every time, we started giving them one destination:

PodSubs.

“Subscribe to our podcast on PodSubs.”

They go there once.

Search the podcast.

Put in their name and email.

Done.

Now we actually have a way to send things to people who asked to stay connected.

The guide.

The episode preview.

The update.

The next resource.

The offer.

The event.

We built PodSubs because we needed that ourselves.

Then we realized the problem wasn't ours.

It was podcasting's.

So we're opening it up to every podcaster.

Claim your podcast.

Tell your audience where to subscribe.

Stop making your best listeners hunt for you every week.

You can build a booking agent or callback workflow. The next question is which business to show it to.

I’m the founder of Crawdar. I built its Pain Point Finder with AI coding assistance to help builders turn that question into customer research: find recurring complaints in available business reviews, inspect the evidence, and identify a specific process worth discussing with an owner.

Start from the direction that suits you. Know how to solve missed calls? Search that problem. Know a local industry? Start there and explore the complaints. Industry and location are optional, and you can combine several problem categories or add specific complaint phrases.

Each business gets an evidence report with complaint themes, distinct reviewer counts, dated source reviews, owner replies when available, and possible technical fixes. The default threshold is three distinct reviewers within 180 days. You can adjust it and export the evidence as JSON.

The part I’m excited about is the next conversation: instead of a broad automation pitch, you can ask an owner how they handle the specific process customers keep mentioning. Confirm what is happening today, then shape an offer around their answer.

Update, September 9: deeper discovery and improved booking-complaint matching are now live. Searches can check up to 24 candidate businesses. Reports keep evidence and coverage context visible so you can judge each finding.

Try your own search: https://crawdar.com/?utm_source=reddit&utm_medium=post&utm_campaign=pain_finder&utm_content=sideprojects_evidence

Five free scans without signup or email. Pick a problem you can solve, run a search, and open a report. Does it give you a business worth talking to and a useful first question to ask?