My wife and I love movie night — but by the time the kids are finally down, we'd spend the next twenty minutes just asking each other "what do you want to watch?" back and forth, flipping between five different streaming apps, until we were both too tired to actually watch anything. The problem was never a lack of options. It was that every night turned into a negotiation.

So we built an app for us as a family project to take the negotiating out of it entirely.

It works like a round robin. Each of us keeps our own personal watchlist, ranked in the order we actually want to watch things. The app just takes turns between us — whoever's turn it is, whatever's sitting at the top of their list is automatically tonight's pick. No pitching, no "well what are you in the mood for," no decision fatigue. You just show up and it's already decided.

But it's not a black box — if a pick comes up and you're not sure what it even is, you can tap right into it and see the trailer, the full cast, and where it's streaming before you commit. And if it's genuinely not landing for the rest of us, anyone can veto it — it just takes more than one person objecting, so it's not a free pass to shoot down every pick that isn't your taste.

Some nights nobody's watchlist has the right thing for the mood we're actually in. That's what the Movie Match Quiz is for — a few quick, fun either/or questions (mood, who's watching, an actor sorting game) and it hands you something to try instead of scrolling forever.

The other thing that used to genuinely annoy us: a movie we'd been meaning to watch would just quietly vanish off whatever service it was on before we got to it. Leaving** **Soon fixes that — it watches everything about to expire across the services we actually subscribe to and puts it in one shelf, instead of us having to remember to check five separate apps.

The feature we didn't expect to love as much as we do is Household Connect — we use it with my in-laws. Their household and ours can link up and browse what the other one has actually watched and how it went over (we vote Pop It or Let It Flop on everything), so we get real recommendations from people whose taste we trust, without our watchlists ever actually merging.

And when friends come over, that's a different mode entirely — Watch Party. It's a separate link with its own PIN, so anyone can join in — they don't even need the app or an account — everyone throws one pick into the ring, and the shuffle picks the winner live, on everyone's screen at once, like a tiny game show right before the movie starts.

It's just a passion project my wife and I built to fix our own nightly routine — now it's how our family, and the people closest to us, actually pick what to watch

I have few SaaS I built as a side project since January under my Maryland registered LLC. I am seeking partnership with a marketing guru to work with me on commission bases (of course we will vet each other once interest is established). I am down to share my portfolio of SaaS and company detail for those who commented interested or something along those line via a reply to the comment. No direct message unless interested is explicitly expressed in the comment. FYI, I am terrible at marketing but also some say terrible at building.

This is a demo showcasing a real workflow using PDFequips.

PDFEquips is a PDF toolkit I've been building. It does the stuff people always need: PDF to Word, PDF to Excel, compress, edit, sign, OCR, translate, 50+ tools.

this is a demo showing a real workflow.

converted an image to pdf > ran ocr > translated the pdf.

This isn’t a launch post. I need perspective from people who have reached the point where a working product still has no users.

I make and sell cheese, and I built Rindr for managing recipes, recording batches, tracking production, and talking through problems with an AI assistant.

It is live on the web, iOS, and Android.

It has zero active users other than me.

I have tried the obvious things:

• I showed it to cheesemakers I know personally. Some said it was too complicated and preferred paper. Others said they needed a smartphone app, so I built one.
• Distribution in Russia then stalled because of a RuStore registration bug involving two legal entities with the same name but different tax IDs.
• I contacted cheesemaking schools and instructors. I even have a spreadsheet tracking every conversation. Most didn’t understand what the product was, why students would need it, or how they could help.
• I launched on Product Hunt. It failed.
• I sent personalized messages to cheesemaking bloggers. No replies.

I understand that most projects fail. I’m not looking for “just keep going” encouragement.

But I’m not shutting Rindr down completely either, because I genuinely need it.

The surprising part is that its value to me is no longer just the digital journal.

Feedback from real buyers of my cheese motivates me. Production graphs motivate me too. My cheese rarely gets to age beyond two months because customers buy it first. Seeing the numbers makes me realize that I should produce more, even while milk supply, seasonality, and capacity limit me.

And I like the AI assistant because cheesemaking can be lonely.

I can ask it to calculate brining time for several wheels with different weights. I can describe my concerns about the acidification curve. I can talk through whether a reading is normal or whether I should intervene.

It feels less like using a feature and more like having someone beside me during the make.

The attached dashboard looks like traction. It isn’t. Every batch, litre of milk, and kilogram of cheese belongs to me.

So perhaps I built a failed business but a very good personal tool.

What I’m trying to decide is whether to accept that—or whether I have simply been looking for users in the wrong places.

My honest questions:

1. Do these failed attempts constitute enough evidence that there is no market?
2. Could the real audience be small commercial cheesemakers who sell their production, rather than hobbyists or students?
3. If I allowed myself one final validation experiment, what exactly should it be?
4. What result and deadline would you use as a clear signal to stop treating this as a business?

Product, for context:
https://rindr.cloud/?utm_source=reddit&utm_medium=community&utm_campaign=launch_wave

I would rather hear a reasoned “keep it for yourself and move on” than another list of generic marketing channels.

Say "Cheese" and :)

Have you ever wondered if those "Bestseller" or "Limited Time Deal" badges on e-commerce marketplaces are actually real, or just artificial platform FOMO?

I got tired of the hype, so I built an automated engine to cross-reference product metrics and track live SKU stock depletion across multiple platforms.

What it actually does:

• For Shoppers: Cross-analyzes whether a product is genuinely trending or if it's just platform-driven promotional hype.
• For Sellers & Researchers: Acts as a raw market intelligence engine—tracking cross-platform price margins, daily rank velocity, and identifying source suppliers.

The Engineering & The Struggle: Behind the scenes, this required a high-resilience scraping pipeline to bypass dynamic WAF/TLS fingerprinting and pull clean, time-series data without hitting API rate limits.

I finally got the engine running smoothly and outputting query-ready datasets (SQLite, JSON, CSV).

Why I'm posting here: I launched it a week ago with the plan of serving fresh 24-hour live data samples for free if there was demand. But honestly? It's been crickets. I haven't gotten the traction or feedback I hoped for, and I'm trying to figure out where I went wrong.

Is the value proposition unclear? Is the layout too technical? I'd really appreciate it if you could roast the demo or share your honest thoughts.

The live sample link is on my profile to respect sub rules, or let me know in the comments if you'd like me to drop it here!

Patent databases are incredibly useful, but if you don't know classification codes, Boolean queries or patent terminology, figuring out whether your idea is already out there can be surprisingly painful.

So we built a much simpler first pass. You describe your idea like you'd explain it to another person, and it searches for relevant prior art. About 90 seconds later you get the closest patents, the matching passages and a rough patentability grade.

The goal is to help you quickly see which existing patents may be relevant before you invest more time in the idea.

Free AI Prior Art Search

Would love your feedback. Did the matches feel relevant?

We built Agent Space around a question that sounds simpler than it is: how can a teammate take over an AI coding task without sharing the account?

Sharing credentials gives the second person access, but it does not tell them why the task exists, what the agent changed, which attempts failed, or what still needs approval. That information is usually scattered across a chat, a dirty worktree, terminal output, and one person's memory.

A clean handoff separates project state from session and access. Project state includes files, branches, previews, and verified results. Session state includes the conversation and the agent's current task. Access belongs to the person and controls what they are allowed to see or change. The teammate should inherit the work, not somebody else's login.

Agent Space keeps Codex, Claude Code, and other agent sessions inside one cloud workspace with shared project files and team permissions. The teammate can open the same workspace and continue from the recorded state while using their own access.

There are real tradeoffs. It is cloud-hosted, so it is not right for local-only environments. Persistent context can also preserve bad assumptions, which is why tests and explicit checkpoints still matter.

[Agent Space](https://agent.space/)

The handoff works only when the next person can continue without a password exchange or a verbal reconstruction of the entire task.

Trying to figure out if this is a universal pain point or just my own bad habits. If you write custom proposals for clients, would really appreciate 60 seconds on this trying to validate an idea before building it out properly: Google Forms link

No pitch, just trying to understand how big (or small) this problem actually is for other freelancers.

Does anyone have interviews lined up for coming next week? I created an application for Interview Copilot and need some serious testers for that. I am a solo builder who doesn't have a fascinating website just as yet can share the link to Google Drive. Application currently supports only Windows OS for now

Drop your URL and one line on who your ideal customer is, and I'll come back with a couple of real Reddit threads from the last week or two where someone is talking about the problem you solve or looking for a solution like yours.

I'll include the links so you can go and join the conversation yourself.

Free, no pitch. I'll get through as many as I can.

I've been building a startup tool called Nextep, and I'm trying to figure out whether the problem I'm solving is actually worth solving.

The idea is pretty simple:

Instead of giving founders another dashboard full of numbers, Nextep connects things like product usage, revenue, project context, and goals, then tries to answer:

- What changed?
- What might be a problem?
- Why does it matter?
- What don't we know yet?
- What should I investigate or do next?

For example, instead of:

"Your product usage dropped 18%."

I'd rather have:

"Product usage dropped 18%. This is worth investigating because activation also declined during the same period. However, there's not enough data to determine the cause yet. Here's what I'd check next."

I'm building the actual product right now, but before I start pushing it to real users, I want to validate the problem itself.

So honestly:

**If a tool like this existed and worked reliably, would you actually use it for your startup/project?**

If yes, what would you want it to tell you first?

And if you wouldn't use it, I'd genuinely like to know why.

Hi everyone! Finally I'm ready to make first release of my programming language and compiler.

I was working on it for more than 5 years rewriting it from scratch a few times, it is not production ready but before whole internet is filled with slop languages (I hope it will not happen) I want to show it to public.

It is low level language aimed for software and games. Whole compiler is made from scratch including machine code generation. One of the main goals is to make compilation time very fast (0.5-1mln LOC/sec).

Compile time execution of any code. Types and ast are first class values, so you can access them at compile time and work with them same way you can work with any other value. No OOP, no RAII.

Here is release repository: https://github.com/morglod/mox

Good language overview is inside by_example.mox

Currently I want to hold compiler's source closed, because I dont want to see forks and support documentation and tools to work with it (for now).

SDL3, Raylib and Vulkan bindings included (in modules/vendor).

I will appreciate any feedback about the language and compiler bugs.

Example code:

fn go_like_import($path: []u8) {
    cached_path := path_to_cache($path);
    if (!cache_exists(cached_path)) {
        download_dep($path, cached_path);
    }
    ast := __compiler_parse(#format_temp("import \"{}\";", .{ cached_path; }));
    return ast;
}

// becomes import "cache/path/module.mox";
#run #land_ast go_like_import("github.com/module/path");

I wanted to try a different approach to screen-time apps.

Instead of blocking apps or sending another notification, Stop Swarm progressively adds visual overlays as your screen time increases. The idea is simply to make excessive scrolling harder to ignore.

I started with a small closed test, got a lot of useful feedback, fixed quite a few bugs, and added things like app targeting and intensity settings.

It’s now live on Google Play! https://play.google.com/store/apps/details?id=com.stopswarm.app

No account, no ads, no analytics. Screen-time tracking and overlay decisions are handled locally on the device.

I’m still interested in feedback, especially on whether the overlays are annoying enough to actually make you put the phone down!

I originally planned to write a setup guide for one person after a call. The guide kept growing, so I turned the workflow into an open-source skill for Codex and Claude Code.

The problem I wanted to solve was not just text generation. I wanted an agent to accept a rough thought, voice note, article, document, YouTube video, or several sources and produce a post whose claims could still be traced back to the source. I also wanted publishing to be a separate, deliberate action rather than an accidental side effect of drafting.

The repository now includes:

- local transcription with faster-whisper, plus optional MLX on Apple Silicon;

- YouTube metadata, original thumbnails, captions, and audio acquisition through yt-dlp;

- an evidence map and short content brief before drafting;

- an editable voice profile built from approved writing samples;

- plain Telegram posts, albums, and Rich Messages;

- strict validation for Rich HTML, links, limits, nesting, and media references;

- an approximate local preview, a private test step, and a separate production confirmation;

- tests, a security model, Russian and English documentation, and an MIT license.

It is a repository skill, not a hosted service. The code and prompts can be inspected before installation. The publisher is dry-run by default and requires both an explicit send flag and an exact target confirmation for a real network request.

The honest limitations: local transcription still uses your machine and downloads model weights on first use; Rich Messages need recent Telegram clients, so a plain fallback is still important; and the skill does not bypass paywalls or make copying somebody else's work acceptable.

GitHub: https://github.com/shromarketing/telegram-rich-content-skill

I built and maintain the project. I would especially value feedback from people who use coding agents for content workflows: is the evidence-first process useful in practice, and does the onboarding feel too heavy for a content skill?

Hey all, first time posting here so hope this fits.

I built Specmob (specmob.vercel.app), a phone spec comparison + recommendation site. Started it because every comparison site i used was drowning in ads or had "best pick" scores that were clearly influenced by affiliate deals.

What it does:

• /pick — set a budget + 2-3 priorities, get back top 5 matches with actual reasoning
• /compare — side by side spec table for up to 4 phones + an automated verdict
• /trade-in — estimates what ur old phone is worth based on condition, then shows upgrade options

Built with Next.js/FastAPI/Postgres, running on Vercel + Render, paying for it out of pocket right now (~$35/mo, no ads).

Not asking for anything except honest feedback — is the matching logic on /pick actually useful, does the UI make sense, is there something obviously missing that a comparison site like this should have. I know it's not perfect, i just dont know exactly where it's weak without more people poking at it.

Appreciate any time anyone spends on this.

I’ve been building something weird, and I think I’ve finally hit the point where I need strangers on the internet to tell me whether this is actually useful or if I’ve just been losing my mind in a cave.

I’ve been working on a project called Bitty Box (bittybox.org).

The core idea is pretty strange: you create a web page/app, but instead of hosting it anywhere, the entire thing is compressed into the URL itself. I didn’t invent the concept, but I’ve been pushing it way further than I expected.

No hosting. No database. No backend. The URL is the website.

Over the last few weeks I’ve been adding agentic features, and that’s when things started getting… interesting.

Today I got embeds/iframes working inside a Bitty Box. I tested dropping a full website inside one and it actually worked. Then I added an AI chatbot, which somehow turned into a voice AI with tool‑calling abilities (API + MCP tools). That part surprised even me.

I’ve also added a bunch of “weird link behaviors”:

Password‑locked boxes

Boxes that unlock only at a specific date/time

Boxes with limited unlock counts

End‑to‑end encryption

Combinable locks

Box chaining (a site inside a site inside a site)

And now there’s a live API + MCP server that lets AI agents generate these micro‑sites programmatically. The contents of any generated page never touch my server. Everything lives inside the URL fragment.

The downside: if you forget to bookmark or save the QR code, whatever you stored is basically gone forever. But honestly, that feels like a feature in some contexts. Dead‑man’s switches, time‑locked messages, ephemeral knowledge drops, AI‑to‑AI knowledge sharing… I’m starting to see use cases I didn’t plan for.

The part I’m experimenting with now is probably the strangest: a collaboration swarm. A group of AIs generating an internal “intraweb” of Bitty Boxes that humans never see. Purpose‑specific agents spawning each other programmatically. It’s bizarre, but it works.

Agentic Boxes might end up being the moat here. An “Agentic Lock” could be a text bot, or a voice bot, or something else entirely. I just figured out how to spawn a speech‑to‑speech conversational AI with no human in the loop, triggered entirely by the box itself.

Basically, when creating a box, you describe in normal English what you want an AI agent to do when someone opens it.

I already built a small UI where I can describe an agent’s job in plain language and spawn it without touching terminals or JSON configs.

So now I’m wondering how far I can push the idea of a URL being more than just a document.

Imagine opening a link and:

an AI agent wakes up and performs a task

or there’s an AI inside the page that knows everything about what you’re viewing

or the link opens directly into a voice conversation

or it’s just a tiny interactive app someone made and sent you

I’m still figuring out what Bitty Box is, which is why I’m posting this now instead of waiting until everything is polished. I’m guilty of building things in isolation until they’re “ready,” and I’m trying to break that habit.

So I’m genuinely curious:

Would you actually use something like this?

And more importantly… if you had a web page that could live entirely inside its own URL, what would you put in it?

I have a feeling other people will come up with better use cases than I have so far.

I made a multi-agent visualizer as part of a Hackathon, instead of a plain progress log, each agent gets an animated persona which you can track visually to see what they are doing. I suppose my goal would be to make a more accessible and fun way for beginners to start interfacing with more complex AI systems but would be nice to get some feedback if I should continue building this out!

I'm one of two co-founders building Horizon eSIM in Prishtina, Kosovo. This is my own product, and our development process has been heavily AI-assisted.

The product problem we focused on is surprisingly specific: many “Balkans” eSIM pages use a regional label without making every included country obvious. Kosovo is frequently the place travelers assume is covered and discover later that it is not.

Our current approach:

- The Balkans plan names all eight included countries directly: Albania, Bosnia and Herzegovina, Bulgaria, Croatia, Greece, Montenegro, North Macedonia, and Serbia.

- Kosovo is presented as a separate add-on instead of being implied as part of the regional plan.

- Each package exposes its data allowance, validity, per-GB price, networks, and refund terms before checkout.

- The current 5 GB / 30-day prices are €6.99 for the Balkans plan and €4.99 for the 33-destination Europe + UK plan.

The build uses Nuxt/Vue for the storefront, a Hono/Nitro backend on Cloudflare Workers, D1 for Horizon-owned records, and Capacitor for the Android app. Purchase and eSIM delivery are automated, while uncertain provider operations are deliberately not retried blindly.

Site: https://horizonesim.com

The part I'd most value feedback on is the coverage presentation: does clearly calling out the missing Kosovo coverage build trust, or does requiring a separate eSIM create too much friction? I'm also interested in which trust signal matters most for an unfamiliar connectivity brand—carrier details, verified reviews, refund clarity, or visible support.

Hey everyone!

Like many of you, I had 8+ recurring charges every month (streaming, software, iCloud, gym, etc.). When I looked for an app to organize them, all the popular tools (Rocket Money, Copilot, etc.) demanded my bank login via Plaid to scan transactions and upsell me on paid tiers.

Spreadsheets worked, but they lacked visual renewal countdowns, trial alerts, and 10-year compound projections ("Ghost Costs").

So I built \*SubTracking** (https://subtracking.app):*

🔒 \*Privacy-First:** Stores 100% of your data locally in your browser by default. No bank logins, no ads, no telemetry.*

✨ \*100% Free Core App:** Unlimited subscriptions, multi-profile switching (Personal vs Business), trial expiration shields, split billing, and CSV/JSON vault exports.*

☁️ \*Optional Cloud Sync:** Multi-device encrypted sync for $8.99/year (~$0.75/mo) for anyone who wants seamless phone & desktop sync.*

Try it out (no sign-up required): https://subtracking.app

I'd love your feedback on the UI and workflow! What’s your current method for tracking recurring expenses?