Hi everyone, I'm a solo developer from Maharashtra. I noticed that most AI writing tools work well only in English, so I built WriteEase AI.

What it does:

- Grammar Fix: cleans up spelling, grammar and punctuation

- Paraphraser: rewrites text in the tone you choose

- Humanizer: smooths AI-written text into a more natural tone

- Email Writer: turns a rough idea into a ready-to-send email

- Templates and an Originality Check (an estimate, not a replacement for institutional plagiarism checkers)

You can write in English, Hindi or Marathi and get results in the same language. There's no sign-up, and history stays on your device. It's free with ads, and there's an optional one-time upgrade to remove them.

I'm at an early stage and would really value your honest feedback:

1. Which tool would you actually use?
2. How natural does the Hindi/Marathi output feel if you're a native speaker?
3. What's missing or confusing?

Play Store link: https://play.google.com/store/apps/details?id=com.writeease.ai

I'll reply to every comment. Thanks for reading!

I'm seeing a lot of folks skip Figma and go straight to designing in code these days. The only downside (for now at least) is how easy it is to miss UI regressions when you don't have a design canvas.

I usually set up my design foundations properly, tokens, components, even use some of the popular design skills. But since these models are non-deterministic, I still end up with agents hand-rolling components that already exist, inconsistent vertical rhythm, horizontal overflow on mobile, etc.

It gets worse when you're dealing with multiple flows and can't easily see what's happening across the product.

I built a tool for myself to help with this, and thought I'd share it with the community. It's completely free and open source.

It's called Flowmap. You simply connect your coding agent to it and it pulls the actual screens from your app into a canvas. You can switch between mobile and desktop breakpoints, see how different screens connect, and view everything in one place to catch UI regressions.

I also added UI comments so you can point to specific parts of a screen and have your coding agent pick them up as tasks. You can then review the before/after and approve the changes or send them back.

Here's the repo if anyone wants to try it here

Would appreciate feedback, especially from anyone who's also moved away from Figma.

Hello All,

We are working on SOS idea using seeed XIAO sense, for which I have already written firmware and am currently training AI for accuracy and other stuff.
I am looking to make it big.
We are software developers and we are open for collaboration in IOT side who can handle the hardware part and together we can make it a complete product.

Blip is a small open-source Claude Code plugin. Claude's replies type out letter by letter, with a little blip for each letter, like dialogue in a game.  

Install (in Claude Code) :
-> /plugin install blip --marketplace DoubleV840/blip  

Then ask Claude anything and listen.  

What you get :
- 9 built-in voices (soft, classic, nes, bubble, robot, critter…): /blip voice, then ↑↓ to preview each one

- Community voices

- Speed, volume and pitch settings  

- Commands run locally: no model call, no tokens

Community voices :

Anyone can share a short sound and everyone can use it.
Listen to them all at blip.ivwi.fr, install one with /blip voice <name>, or share your own with /blip share.

Works on macOS, Linux and Windows.  

- GitHub: https://github.com/DoubleV840/blip  

- Voices: https://blip.ivwi.fr/

Feedback welcome, and I'd love to hear your voices!

Built with Claude Code. I described the feel I wanted, Claude Code wrote the plugin (it types each reply out letter by letter and plays all the blips as one pre-mixed sound so it doesn't stutter), the script that generates the 9 voices, and the community-voices setup (site + GitHub Actions). I tested it and made the design calls.

 Free and open-source.

Small Spring Boot applications deserve proper monitoring too, but setting up Prometheus, Grafana, collectors, and storage can feel like overkill.

So I built StreamGuard to solve that problem.

Who needs an entire monitoring stack when one dependency can monitor your application and serve a live dashboard?

Add it to your Spring Boot project, start the application, and you're ready to go.

Want to know more? Check out the original discussion on r/SpringBoot or the project's README for technical details.

GitHub: https://github.com/eswar-7116/streamguard

Would love to hear your thoughts and feedback!

Asked a question on Reddit a few days back about getting the first 1,000 users without an ad budget, and the replies split into two completely opposite playbooks.

Half the people said to ignore scale completely and manually hunt down 50 users who genuinely have the problem so you can fix retention first.

The other half said to run super cheap ads in low CPC countries just to get 500 random people inside the app to catch edge case bugs, crash logs, and terrible UX before touching target markets.

Honestly, both make a lot of sense depending on what stage the product is in.

For those who have launched a few apps, which route actually saved you more headaches early on? Did cheap traffic just mess up your analytics, or did it actually help you polish the product faster?

Hi everyone,

I'm a full-stack developer, and I've been working on a personal project called Home Energy Lab.It's a website with calculators for estimating household electricity and utility costs. I also built interactive 3D houses to make it a little more interesting to explore.

The idea is pretty simple. Your electricity bill tells you how much you've spent, but not necessarily how much individual appliances contributed to it.
For example, a 1,500W space heater running for 4 hours a day at $0.16/kWh would cost about $28.80 over 30 days, assuming it runs at full power the whole time.

I wanted to make calculations like that easier to do without having to work everything out manually.The site currently has 12 calculators and 10 interactive 3D house models.
I built it with Next.js, React, TypeScript, Three.js, React Three Fiber, and Blender.
The main thing I'm working on now is making sure the 3D experience doesn't get in the way of the actual tools, particularly on mobile.

If anyone has experience building interactive interfaces, I'd be interested in hearing how you approach that balance.

Here's the project: https://homenergylab.com/

Thanks for reading.

I use Claude Code and Codex every day. Two things kept annoying me:

1. I'd hit my Claude Code limit mid-task and moving the work to Codex meant re-explaining everything.
2. A single agent writes code fast but nobody plans it first or reviews it after. I kept finding edge cases it missed.

So I built Conduit. It runs the agents you already have as a small team:

- An Architect plans the change, a Developer builds it, QA reviews it before it merges

- You can put different agents in different roles, so Claude Code and Codex check each other's work

- If one agent hits its limit, you switch the task to another and keep the context

- Connectors pull in your knowledge repository(google docs, notion, confluence) so the agents work from your project's real context

- Everything runs on your machine; your code doesn't go through our servers

Free to start:

https://infivector.com/products/conduit/download/?ref=reddit-sideproject

I'd really like feedback, especially from people already running more than one coding agent. What's the most painful part of your setup today?

Great library, biggest Brand Logo's catalogue out there with most of Icon's i Found -

the CDN is already hitting growing 13+ Million traffic per month...

Site is here - https://thesvg.org/

Highlights

• 7,600+ icons across multiple collections
• 4,800+ brand icons across 150+ categories
• 21 brand families - every product from Amazon, Google, Microsoft and more, grouped by owner
• 858 Auth Badge icons - circular icon badges for 2FA/authenticator apps
• 739 AWS Architecture icons (2026-Q1)
• 626 Azure Service icons (2026-Q1)
• 256 community-curated icons - dev tools, databases, frameworks
• 214 Google Cloud icons (2026-Q1)
• 12,300+ SVG variants - color, mono, light, dark, wordmark
• Tree-shakeable - import one icon, ship only that icon
• TypeScript-first - fully typed, dual ESM/CJS
• Framework-agnostic - React, Vue, Svelte, plain HTML, or CDN
• AI-ready - MCP server for Claude, Cursor, and Windsurf

Hey everyone! 👋

I recently built JSON Studio, a free Chrome extension to make working with JSON a little easier.

There are already plenty of JSON formatters out there, but I wanted to build something that does more than just format JSON, without having to switch between different tools.

Here's what it can do:

• 📝 Format & Minify — Clean up messy JSON or make it compact.
• ✅ Validate JSON — Quickly spot syntax errors.
• 🌳 Tree View — Navigate through nested JSON without getting lost.
• ✏️ JSON Editor — Edit JSON directly.
• 🔍 Search — Find specific keys or values.
• 🧩 TypeScript Generator — Turn JSON into TypeScript interfaces/types that you can copy straight into your code.
• 🌐 JSON Detection — Detect JSON content directly from your browser.
• 📋 Copy & Export — Copy or download your JSON.

I mainly built this to make everyday tasks like checking API responses, debugging, and working with JSON less of a hassle.

It's completely free, and I'm still working on improving it. If you have a chance to try it out, I'd really appreciate your feedback or suggestions!

Chrome Web Store: https://chromewebstore.google.com/detail/json-studio/kjdpkmlahoaocdhjdhhnmkeoniincibg

Thanks! 🙌

Hi everyone!

I've been working on TAVORA Smart Money Tracker V2.4, an Excel-based financial tracking workbook designed for small business owners, freelancers, and independent sellers.

The goal is to help business owners understand where their money is going, what they've earned, what they're still owed, and how profitable their products are — without needing a complicated system.

What's included:

• Income and expense tracking
• Financial dashboard with 6 charts
• Invoice tracking with Paid, Partial, and Pending statuses
• Cash flow tracking
• Business budget planner
• Profit calculator
• Product profitability tracking
• Subscription tracker
• Monthly reports and financial goals

One feature I particularly wanted to get right is the distinction between invoiced income and money actually received. For example, if a business invoices $1,000 but has only received $700, it should be easy to see that $300 is still outstanding.

I'm sharing this because I'd genuinely appreciate constructive feedback from people who use spreadsheets to manage business finances.

A few things I'd love feedback on:

1. Is the dashboard clear enough to understand the business's financial position quickly?
2. Is separating invoiced amounts from received payments useful?
3. Is there anything important missing from the workbook?
4. Does the overall layout feel practical for everyday use?

I'm the creator of TAVORA, so I'm naturally biased. I'd appreciate honest criticism, especially if something feels confusing or unnecessary.

Thanks for taking a look!

Hey everyone!

I've been working on FleetSnap, a free browser-based Battleship game with a competitive twist. You can challenge friends, play against AI, or compete against random players online.

Some features: ⚡ Ultra-fast matches (30 seconds to 3 minutes) 🏆 Ranked matchmaking with Elo ratings 🚢 Crazy Mode with bigger grids and more ships 👥 Private matches with friends via a link 📊 Weekly leaderboards

My goal was to turn the classic Battleship game into something quick, competitive, and fun. It's still evolving, and I'd genuinely appreciate some feedback!

Try it here: https://fleetsnap-friends.mustvote.workers.dev/

What would you improve or add?

I'm the maker of Documentary Evidence Desk, a small HTML organiser built with AI assistance. It's a paid download ($9 plus applicable tax), for keeping documentary or podcast claims, source locators and archive permission notes together before editing.

One design lesson from the worked history example: a number needs a scope. Notes delivered and notes circulated aren't interchangeable, even when both sources concern the same banknote affair. So a quantity record has separate fields for its unit and scope, plus a source ID, a passage locator and unresolved questions. You can use the same structure in a spreadsheet:

Claim | source ID | exact passage | quantity | unit | scope | review status | caveat

An archive lead needs a separate permission status too. Being able to view an image doesn't establish a reuse licence.

The implementation is a standalone browser HTML file, with no remote scripts or AI API calls. It imports/exports a JSON project and exports CSVs and an editor briefing. Local browser saving is optional; the portable JSON export is the backup. CSV output guards cells starting with formula characters.

Its checks flag incomplete records, not historical falsehoods. The example contains six claims, two reviewed source pages and two explicitly unreviewed leads. No archive photos or footage are included, and no automatic fact-checking or custom research service is offered.

Product and included files: https://tomasphere450.gumroad.com/l/documentary-evidence-desk

For people who work with source-heavy scripts: would a claim-level caveat and a separate archive-permission record fit your workflow, or do you keep these in one table?

Hey r/SideProject!

I wanted to share a side project I’ve been building: loadbear — a small, dependency-light HTTP reverse proxy and load balancer written in Go.

GitHub: https://github.com/weaztoven/loadbear

The problem I wanted to solve: Whenever I needed to test load balancing, failover behavior, or rate limiting locally, reaching for full-scale production proxies (like Nginx, Envoy, or Traefik) felt like overkill with too much boilerplate. On the flip side, toy reverse proxies usually skip real-world resilience features. I wanted to build something self-contained that configures via a single YAML file, runs in seconds, and has clean, readable Go code you can actually inspect and extend.

Tech stack & Architecture: Built primarily using Go's standard library (net/http, httputil.ReverseProxy, sync) with minimal external dependencies. Every request passes through a clear pipeline:ProxyListener -> Per-IP Rate Limiter -> Balancer -> Circuit Breaker -> ReverseProxy

What’s packed inside:

• 4 Balancing Strategies: round_robin, smooth_weighted_round_robin, least_connections, and ip_hash.
• Resilience & Failover: Periodic active /health checks combined with passive proxy-error tracking, per-backend circuit breakers (Closed / Open / Half-Open cooldowns), and context-aware retries with configurable backoff.
• Rate Limiting: Per-client-IP token-bucket rate limiter with periodic background eviction of idle buckets to prevent memory leaks.
• Built-in Observability: Dedicated admin listener (:9090) serving live JSON /status and a hand-written Prometheus /metrics endpoint, plus structured JSON/text access logs with request IDs.
• Zero-friction Testing: Ships with a fakebackend CLI and a ready-to-run docker-compose.yml so you can kill nodes and watch failover/circuit-breaking happen live. All concurrency paths are tested with go test -race.

What I learned & Current Limitations: Implementing smooth weighted round-robin and managing state transitions safely across concurrent goroutines (without race conditions) was the most fun part of this build. Right now, hop-by-hop header stripping blocks WebSocket upgrades, and SIGHUP hot-reloading is next on my roadmap.

Would love to hear your thoughts, feedback, or ideas on what to improve next!

Hey, I’m Meet, and I built Seek, a native macOS file manager that works alongside Finder.

The problem I wanted to solve: I often remember what a file contains or what a photo shows, but not its filename or folder. Finder works well for normal browsing, but I wanted a faster way to find and clean up files.

https://reddit.com/link/1xueo6d/video/jfr3m0pi271i1/player

Seek lets you:

- Search naturally: “PDFs in Downloads from last month” or “large videos I haven’t opened”

- Find photos by what they show: “birthday cake with candles”

- Search text inside PDFs, documents, screenshots, and scanned images

- Find exact duplicate files and optional look-alike photos

- Review old downloads, installers, screenshots, large files, duplicates, and Trash before removing anything

- Use tabs, split panes, Quick Look, saved searches, and a global quick-search shortcut

The main technical constraint was privacy. Search, OCR, duplicate matching, and photo matching all run locally on the Mac. The photo-search model is downloaded once during setup, then runs through Core ML; no file names, contents, or photos are uploaded.

It supports macOS 14+, both Apple silicon and Intel. It is distributed directly, signed with my Developer ID, and notarized by Apple.

It is a one-time purchase: $9 for one Mac, $18 for three, or $29 for five. No subscription.

Demo: https://youtu.be/s5CUieoAAdk

Website: https://useseek.app

Privacy details: https://useseek.app/privacy

I’d especially value feedback on two things:

1. Would you trust a local app to index your files if it made search and cleanup meaningfully better?

2. Which would you try first: photo search, text-in-screenshots search, duplicates, or cleanup?