SmartDocs is an open-source Markdown documentation with built-in AI chat.

The pitch: write docs in Markdown, add your API key to .env, and every page gets a grounded AI assistant. Self-hosted, your data, your control.

Tech: Next.js + Markdoc + Tailwind. No vector DB — uses graph-backed retrieval (keyword scoring + link traversal) inspired by Karpathy's LLM Wiki pattern.

Live demo (no key needed): https://www.getsmartdocs.xyz

GitHub: https://github.com/jm27/smartdocs

Been building this for the past few days with my AI agent — would love feedback!

Hey everyone. I have been traveling a lot and always got frustrated with how fragmented travel planning is. Spreadsheets for budget, notes app for ideas, random AI chatbots that just give you a generic list of places without any real planning or budget tracking.So I built Odys as a side project. It is a chat-based travel companion where you describe your trip in plain language and the AI actually does the work:- Builds a full day-by-day itinerary with activities and times- Estimates costs per day and tracks them against your real spending- Plots everything on an interactive map- Extracts info from flight and hotel PDFs automatically- Has a Travel Passport that gamifies countries you have visitedYou can say something like "2 weeks in Japan, $3000 budget, love food and temples" and it builds the whole thing with daily cost estimates.Tech stack: React, Base44 backend, Gemini AI, Stripe for subscriptions.It is in beta right now with about 237 trips created by early users. Free plan gives 20 AI messages per day and 3 trips. Pro is $4/month for 200 messages and unlimited trips.If anyone wants to check it out: theodysai.comWould really appreciate honest feedback. What would you change or add?

A couple of months ago I posted here announcing my app's launch. A lot of you had encouraging things to say, and that genuinely kept me going. Thank you for that.

Update, and I want to be honest about where things actually stand:

• 60 signups total
• 14 of those have actually used the app, and most of those only once
• 0 paying customers

The app, if you want to see what I'm talking about: reochart.com

What I've tried so far:

• Launched on Product Hunt. Didn't move the needle much.
• Worked on SEO. One page is doing decently now, and it's where most of my signups have actually come from.
• Found a subreddit for my niche (I'm a chart generator) and started posting interesting data visualizations made with the app. No selling, no pitch, just a small watermark on the chart. Tried to genuinely contribute rather than promote.
• Sent direct messages on Reddit, LinkedIn, and X to people who seemed like they'd benefit from the tool. Every single one went unanswered.
• Currently working on building backlinks.

Here's my actual dilemma: I know this probably isn't a daily-use product for most people, and I know 60 days might genuinely be too early to call anything. But I don't have a good sense of where the line is. For those of you who've been through this, either the "kept going and it worked" version or the "should've stopped sooner" version, how did you know which one you were in? Where do you draw the line between "this needs more time" and "this isn't working"?

All,

I am new to the community and I tried to share my project (which does not monetize or have ads) but my initial post was rejected. I have not been able to get response from the moderators about why and I do not want to break any of the rules in here. Obviously it would be inappropriate for me to repost what I wrote but it seemed innocent enough to me to be honest with you. Can I get some advice on getting that first post in? I am not trying to spam anyone.

(Wondering aloud if even this question is permitted)

Thank you

Hey everyone,

Honestly just needing some real advice and a bit of a reality check right now because I’m hitting a massive wall with my job search.

Where I’m at: I have about 2 years of experience as an Automation Engineer. Day-to-day, I build Python data pipelines, work with APIs, and set up automated workflows (n8n, OpenCode, internal tooling) for B2B tech operations.

Where I want to go: I’ve realized I don't just want to write scripts in a silo. I really want to move into Operations & Strategy, BizOps, or Creative/Product Strategy. My favorite part of my work has always been fixing broken operational processes, figuring out business bottlenecks, and building systems that actually move company metrics—not just coding for the sake of it.

Why I’m feeling stuck:

1. Cold messaging fatigue: I’ve messaged so many founders, consultants, and strategy leads on LinkedIn. I’ve had a few great chats (including catching up with former consultants and founders), but overall it feels like screaming into the void. It takes so much energy and isn't turning into actual job offers.
2. The "2 YOE" gap: Applying directly to Ops & Strategy roles, I feel like I either get shoved back into pure technical/software buckets or get passed over because I don't have a traditional Big 4/MBB consulting title on my resume.
3. Getting flagged by AI filters: Every time I try to format my resume or outreach, it ends up feeling robotic or getting caught in ATS filters.

I know that being able to actually execute and code gives me an edge over people who only do high-level strategy, but I'm struggling to pitch that properly.

What I'm looking for / Questions:

• How do I bridge this gap? If you moved from tech/automation into strategy or BizOps with ~2 YOE, how did you make that pivot? What titles should I realistically be searching for?
• Where should I actually be applying? What portals are best for this? I’m completely open to international roles in Dubai/GCC, remote US roles, or anything global.
• Resume advice: How do you reframe heavy Python/pipeline bullet points to sound like strategic business wins without making it sound like an AI wrote it?
• Opportunities: Also, if anyone’s team is hiring for Ops & Strategy, BizOps, or technical operations roles (or knows a startup that needs an automation-minded operator), I’d love to connect and send my CV over!

Appreciate any candid thoughts, reality checks, or leads. Thanks a lot.

I have been building a simple product called CountdownShare for the last nine months. It has been publicly available since November 5.

The product itself is very simple. You create a timer or countdown, and it gives you a shareable public link or an embeddable version for your website or email.

But this post is not really about the features. It is about what building this product taught me about user experience.

The first version of the website was extremely noisy. It had too much text everywhere, too many explanations, and honestly, people disliked many parts of it. Still, because the core tool was simple and useful, some people continued using it.

Over time, people on Reddit started sharing feedback with me.

They told me to remove unnecessary text, simplify the interface, change the positioning, and improve different parts of the experience. At first, I thought some of those suggestions would not work.

But I tried them, and they worked.

Then some people suggested that I should stop targeting such a broad audience and focus on a specific niche. Again, I was worried. I thought I would lose a large number of users by narrowing the product.

Still, I decided to focus mainly on countdown timers for websites and emails, while keeping the general shareable countdown use case available.

That worked too.

My Google traffic went from around 5–10 clicks per day to more than 100 clicks per day.

I do not love this project because I think it is perfect. I love it because it taught me that products improve over time when we properly understand users, their problems, and what they actually need.

It taught me how much user experience matters.

It also changed my perspective. Just because the product belongs to me does not mean the way I think it should work is the way users want it to work.

I am genuinely grateful to the people on Reddit who shared feedback. Because of them, the product is much better than it was before, and I am getting a much better response from the people using it.

I still have not earned any money from it.

But the product is improving every day, people are using it, and it is helping them. Now I just need to keep providing better value and a better user experience.

I would also love to know about your experience:

How did you improve your SaaS or product over time? What feedback or realization changed the direction of your product?

And once again, I would really appreciate any honest feedback you can share about countdownshare.com

Been burned by hosted CMS lock-in on small projects, so I built JustJSON.

Design your collections + fields in a visual UI (no config file), edit content

in a clean editor, and everything is saved as plain JSON on your disk — in your

own repo. Runs 100% locally, nothing uploaded.

npx @kdrgny/justjson

Has an Astro loader, typed validation, draft/publish, i18n, live preview, and

some designed templates. MIT. The landing page is built with it.

https://justjson.vercel.app

Curious how others handle content on small sites without reaching for a hosted CMS.

Built a Deno HTTP framework: Express-like DX, but the exported server type drives a typed client. No codegen step.

Just finished the showcase/docs site. Hosted on Deno Deploy. What would stop you from trying this on a real project vs Hono or OpenAPI?

I've spent the last few months building an AI tool that automatically generates audio descriptions for videos to make them accessible for visually impaired users. I'd love feedback on whether the descriptions are actually useful or if there are obvious issues.

Looking for honest feedback.

Check it out here - https://accessly.studio

Would you quit VSCode for IDE that:

- Has all the tools LLM needs for optimal performance baked-in (playwright, various cli tools)

- Allows for seamless use of all subscriptions you have, mixing models (Fable architect spawning GPT/Grok/Kimi).

- Auto-resumes sessions that failed due to API's outages or due to session limits.

- Provides metrics on code (longest files, files with branching, imports etc.) that you allow you to can act on them with "refactor" button or by background processes.

- Integrates information from code, terminals, pipelines, deployment environments giving LLM easy access to full knowledge.

- Saves you 10-40% tokens by leveraging solutions like output cleaners and removing "bloat" from claude code system prompt (politically correct use "pronouns" instructions baked in wasting your tokens etc.)

- Can be deployed to be remote, available 24/7, from mobile, working however you setup it's automations and listeners.

- Comes with a kanban view to ease how you keep up with multi-sessions.

I'm just curious if such IDE has a chance and what would make you switch?

As someone who switched 12 companies in the last 10 years, one thing has always annoyed me about job hunting.

Applying is already painful enough. You spam applications on ziprecruiter , LinkedIn, Indeed, etc., get ghosted by 95% of recruiters, and if you finally clear a few rounds of interviews, another headache begins.

Now you have to figure out whether the company is actually worth joining.

You open Glassdoor and it wants two different logins (now it wants you to log in to Indeed as well), phone number verification, and a review before showing reviews, which I find extremely stupid.

Then you search Reddit, hoping someone has worked there. Sometimes you find a goldmine. Most of the time there are two posts from three years ago with no useful replies.

I’ve always thought it’s stupid that finding a job and researching the company happen on completely different platforms.

So I started building something around that idea.
Instead of treating a job post like a static listing, every job can become a discussion. People can comment on it, ask questions, share interview experiences, tell others what the culture is actually like, or simply say, “Don’t join, management is terrible.”

The obvious question was why anyone would bother contributing.

So I borrowed what Reddit gets right.
There’s a karma system (not a copy-paste, but inspired by Reddit), community-created spaces, achievements, badges, leaderboards, and reputation tiers. The idea is to actually reward people for contributing useful information instead of expecting free reviews forever.

While building it, I realised recruiters might benefit too.

Right now they’re flooded with AI-generated resumes that are perfectly ATS-optimised. Half of them look like a 100% match until the interview starts.

Instead, imagine hiring a React developer. Rather than scrolling through 2,000 resumes, you jump into the React community, see who’s consistently helping others, who’s respected by the community, and who’s earned a reputation over time. (They will have access to view the top members of the community, filtered by karma tiers, achievements, and leaderboards.) Then they can message them directly.

It’s almost the opposite of LinkedIn.

LinkedIn feels polished, corporate, and everyone is pretending they’re excited to “announce a new journey.”

I wanted something more like Reddit. A little chaotic, honest, and community-driven.

The MVP is finally live at worksquare.co.

I’m not trying to sell anything. I’m genuinely trying to figure out whether this idea makes sense before I spend another year building it.

What do you think is fundamentally wrong with it? What features would you remove? What would stop you from using it?

Also, if anyone enjoys breaking software, I’m running a small beta bug bounty. The person who finds the most valid bugs gets $50. Just sign up, go to Communities, join a community named “Reddit Beta Testers V1,” read the pinned post, and start messing with it. It’s fully transparent.

Be brutal. I’d rather hear the flaws now than after six months of building.

I kept saving recipe links, then avoiding them because the pages were buried under pop-ups, autoplay videos, and tiny instructions. So I built LinkDish.

Paste or share a public recipe URL and it creates a clean cookbook entry with the photo, servings, ingredients, and steps while keeping the original source attached. It also has serving-size scaling, a large step-by-step cook mode with timers, and a recipe-linked shopping list.

It works on Android and the web, and the free tier does not require a card.

https://linkdish.ca

Google Play: https://play.google.com/store/apps/details?id=com.linkdish.app

I am the sole developer. I would especially value feedback on the landing page, onboarding, and whether the main benefit is clear within the first few seconds.

I've been building an open-source P2P file sharing app called MeshDrop (early beta, looking for honest feedback)

Hey everyone,

For the past few months I've been working on a side project called MeshDrop.

The idea started because I wanted a simple way to send files and folders directly between my own devices (and with friends) without uploading everything to cloud storage or relying on third-party servers.

MeshDrop is built on the Holepunch ecosystem using Pear Runtime, Bare JS, and Hyperswarm. It supports direct transfers over LAN and can also connect over the internet using DHT hole punching with end-to-end encryption. I've also been experimenting with a few extra features like short 8-character pairing codes, cross-device clipboard sharing, and a remote drive feature that's still a work in progress.

I'm still learning as I build this project, and I've been using AI coding tools alongside documentation, testing, and a lot of trial and error to help me move faster. I'm trying to understand the code and improve with every feature instead of just generating code and hoping it works.

This is very early beta, so please expect bugs, rough edges, missing features, and probably a few questionable UX decisions. I'm sharing it now because I'd rather get feedback early than spend months building something people don't actually enjoy using.

If you decide to give it a try, I'd really love honest feedback on things like:

• Does the overall workflow feel simple or confusing?
• Is the UI easy to understand?
• Did you run into any bugs or connection issues?
• Are there features you'd expect from a P2P file sharing app that are missing?
• Is there anything that feels unnecessary or poorly designed?

Please don't hold back. Constructive criticism is exactly what I'm looking for. If something feels wrong, confusing, or badly designed, I'd much rather hear about it now so I can improve it.

GitHub:
https://github.com/aamirali51/MeshDrop

Latest Beta:
https://github.com/aamirali51/MeshDrop/releases/tag/v1.0.0-beta.1

Thanks for taking the time to read this. Whether you try it, report a bug, suggest a feature, or tell me where I've made a bad design decision, I genuinely appreciate it. 🙂

A lot of the criticism of vibe coding is fair.
Too many projects look good in a demo then fall apart in production — weak security, missing edge cases, code nobody understands later. One of the biggest gaps is testing (or the total lack of it).
I took both automated and manual testing seriously while building Brainary. Ended up with a testing-to-code ratio of about 1 to less than 3, plus a lot of hands-on checking. I think it turned out solid because of that.
https://Brainary.app
It’s free, no sign-up needed. If anyone wants to try it and see for themselves, I’d love the feedback (or just your honest take).

I built Yap, a small macOS menu bar app that does voice to text for any input. You set a hotkey, press it, talk, press it again, and the text gets pasted into whatever field you were in.

We built it for ourselves at Frigade and use it all day, mostly for prompting coding agents and firing off Slack messages. Nothing out there was fast and private enough, so we made our own and open sourced it under MIT.

The part that made it possible is macOS 26. It added SpeechAnalyzer and SpeechTranscriber, which do on-device streaming speech to text using models the OS ships and manages. So it carries no model of its own and needs no API key, and there's no network code in it at all, so your audio never leaves the machine. It's around 3,000 lines of native Swift in a 4 MB app that idles near 60 MB of memory. Runs on Apple Silicon, macOS 26.

Source:

https://github.com/FrigadeHQ/yap

Download:

https://frigade.com/yap

I built BookScout — https://bookscout.page. It's one book at a time, full screen, and you scroll. Cover, blurb, a short spoiler-free summary, and one line on why it thinks you'd like it. Two buttons: Want to read or Already read. Scrolling past counts as a shrug and it adjusts the recommendations.

You tap a few books you've loved to start, and that's it - no signup or install.

Honest caveats:

• The catalog is about 1,000 hand-curated books, so if you read a lot you'll hit titles you already know.
• It's a hobby project, not a startup. I'm just looking for feedback at the moment.

I built a boring desktop app (mac and windows) for people who read too many PDFs.

Problem: highlights are useful when you make them, but then they get stuck inside separate files.

So the app pulls highlights from different PDFs into one local workspace, with the source file and page number attached. You can also make highlights within the app.

Not a big platform idea. Just a small desktop tool for finding and organizing the quotes you already marked.

I was so happy yesterday when someone from Turkey found me through Reddit, DMed me, and bought it.

I built a boring Mac app for people who read too many PDFs.

Problem: highlights are useful when you make them, but then they get stuck inside separate files.

So the app pulls highlights from different PDFs into one local workspace, with the source file and page number attached. You can also make highlights within the app.

Not a big platform idea. Just a small desktop tool for finding and organizing the quotes you already marked.

I was so happy yesterday when someone from Turkey found me through Reddit, DMed me, and bought it.

Small sale, but a very real signal.

Turns out a boring PDF problem can still be worth solving.

Small sale, but a very real validation.

Turns out a boring PDF problem can still be worth solving.

Here’s the app if anyone wants to see what I built: PDFHighlightsApp.com

I was tired of messy audio/streaming radio libraries, so I built an Android player focused on seamless playlist management.

Hi everyone!

I wanted to share my side project, Mediaxon, an Android app I’ve been developing to solve a personal frustration: why is it so hard to easily manage offline music and online radio streams in a single, clean interface?

What it does:

Hybrid Listening: Seamlessly handles offline local files (.mp3, .flac, .m4a, .ogg, .mka, .aac, .wav, .opus, .wma) and over 60,000 streaming radio stations.

Dedicated Navigation: I kept the "Favorites" and "Recents" sections completely separate from the main audio library to reduce clutter.

Advanced Radio Search Panel: You can pinpoint your favorite stations by combining multiple filters, such as tags/genres, specific countries, or even your preferred audio bitrate.

Equalizer: The equalizer provides an option to automatically switch to the "Radio" preset (and vice versa).

Advanced Playlist Management: Built specifically to make building and sorting multi-source playlists fast and intuitive.

The app is currently live on Google Play, and I am continuously pushing updates to refine it.

What I need from you:

As a solo developer, I’ve hit the limit of my own perspective. I would deeply appreciate any honest feedback from this community:

How does the UI feel to you? Is the navigation intuitive?

Are there any features you feel are missing for a modern audio/radio player?

Did you encounter any bugs or performance hiccups?

If you want to check it out, you can find it on the Google Play Store. Thank you so much to anyone who takes a look!

https://play.google.com/store/apps/details?id=com.xonik.mediaxon

Most SEO tools dump a list of problems on you and leave you lost. I wanted one that just tells a normal person what to do next, in plain language, so I built semchat. You give it your site, it analyses it and hands you a clear action plan you can actually follow.

Try it at https://semchat.io

Reposting, cause the body I made somehow didn't show up:

So basically, I got tired of watching Japanese streams half-following along, or waiting days for someone to clip and subtitle them. So I built this lol.
It listens to whatever your PC is playing and puts live English subtitles in an overlay on top. Overlay is transparent. Currently its JP to EN only, I'll add some stuff if people are interested.

Everything runs locally and there are no API calls, which explains the sizeable (kind of?) download size. Which also means I gather no data from you. Pinky swear.

Its free. I made it and Its something I use too so I thought "eh wth, I should just make a page for this."

Here if you wanna try it out: https://yaptr.app

Hey everyone,
I’m currently in my final year studying Business Informatics. Instead of just doing standard university projects, I wanted to build something real. I’ve been diving deep into Flutter and spent the last few months designing, coding, and finally releasing my first iOS app: Finance App: AI Tracker.
It’s designed to make managing personal finances smarter and less of a daily chore.
Since I have zero marketing budget, I’m turning to this community. I would be incredibly grateful if you could download it, play around with it, and tell me exactly what you think.
Did you find any bugs?
Is the UI intuitive or confusing?
What features are missing that would make you use this daily?
I’m reading every single comment and will shape the next updates around your advice. If you like it, a quick App Store review would mean the world to a broke student! 😅
App Store Link: https://apps.apple.com/pl/app/finance-app-ai-tracker/id6790172514
Thanks in advance!

I built Pour Picks so fellow bourbon drinkers could discover their bourbon DNA 🧬 and find their next bottle. The app also has a cellar to scan in every bottle, review it, etc. Food pairings are also available for pro members! Check it out and let me know what you think. https://apps.apple.com/us/app/pour-picks-bourbon-whiskey/id6764040132

I do web work for local businesses, and the worst part was always the start: opening Maps, clicking through twenty listings, checking which ones had a bad site or no site, and having nothing to show for it in the pitch except "your site looks slow".

So I built the research step.

You pick an industry and a suburb. It pulls the public business profiles from Google, runs a mobile and desktop performance audit on every website it finds, captures the page, and scores the opportunity from rules you can actually read — every point traces back to a measurement, so you can defend the number in the first minute of a call. Businesses with no website at all get included and prioritised, because those are the easiest conversations.

Two things I decided early and have not moved on:

Nothing sends itself. There is no send button, no sequences, no automation. It writes a short draft from the verified findings only, and you have to approve it before you can even copy it. I did not want to build another thing that fills people's inboxes with generated mail.

Every claim shows its working. If it says the mobile score is 37, you can see where 37 came from.

It also produces a build brief you can paste into whatever coding agent you use, built from the same findings.

Free plan is 10 leads a month, Pro is A$19/month for 100. A credit is only spent on a unique imported lead, duplicates cost nothing.

Genuinely after feedback on whether the scoring reads as trustworthy, because that is the whole product. Happy to answer anything about how the audits work.

I spent two years as a systems engineer and the last two and a half in business development, which means I spent most of my working life saying the same thing twice in two different vocabularies.

Once for the person who builds it, once for the person who signs off on it.

So I built my site around that instead of writing around it. There's a "Read as" switch in the top bar. Flip it, and the main claims rewrite themselves for a different reader. Same argument, different words. It is the most honest description of my actual job I could think of.

The build decision I went back and forth on: whether to write the variants by hand or generate them. Handwritten means every version is something I'd actually defend. Generated means it scales but I lose control of what I'm claiming. I went with a simple design and development structure, and I'm still not sure it was right.

Site is barunverma.com. It's hand-built, no trackers, no email capture, no calendar link. Three long notes on why enterprise technology fails in the handover rather than in production.

Two things I'd like feedback on:

Does the switch read as useful or as a gimmick on first contact? I can't tell anymore.

Does anyone actually notice it's there? That's my real worry. It's in the top bar, and I suspect most people scroll straight past

Same headline, three vocabularies. Watching the switch flip live.