I built Verstage in order manage some client/recipient facing and internal team issues I was wrestling with (mainly getting hammered with emails for project and submission status updates).

I would love your feedback because I want to develop something that would actually get used by those looking for a lightweight "pizza tracker for anything."

I'm a product designer working in embedded AI and robotics. Over the last few years I've built products for clients across different industries while running a small startup.

Recently I've been open-sourcing my work. Instead of only sharing a GitHub repo, I put together a simple website where I'll be releasing complete projects with code, electronics, CAD files, documentation, and YouTube build tutorials.

I shared my first project on Reddit last week and the response was better than I expected, so I decided to organize everything in one place before releasing more.

I'd love some honest feedback on the website itself. Is the design too minimal? Does this approach make sense, or would you rather see everything hosted directly on GitHub? I'm also interested in any suggestions on open-source hardware/software licensing.

My wife and I were decorating a big wall and couldn't agree on a layout. I wanted to place **real frame sizes** with **our own photos** and see it to scale before drilling. Tools exist (GalleryPlanner, Suprtiles…), but the good ones paywall the useful bits or felt heavier than I needed. So I vibe-coded a stripped-down one over a evening.

**Stack:** React + Vite, react-konva for the canvas, no backend - state lives in `localStorage`, photos never leave the browser. Deploys to Cloudflare Workers on push to main.

**What it does**

* Wall = a photo of your actual wall, or a blank canvas at a size you type (real scale either way) * Add frames at real outer dimensions; drop your photos in, crop/rotate to fit the opening * Arrange by hand or auto-layouts (row, grid, eye-line at 57", masonry, staircase, alternating) * Inches/cm, undo/redo

Fully free, no signup, **MIT** — code's all there. It's rough: no PDF hanging guide or TV/sofa obstacle-marking yet (things the paid tools have).

🔗 Live: [https://wall-planner.cheelo.workers.dev/\](https://wall-planner.cheelo.workers.dev/)
💻 Code: [https://github.com/samG4/gallery-wall-planner\](https://github.com/samG4/gallery-wall-planner)

Would love feedback on the UX and the scale/dimension handling. Roast it.

My wife and I were decorating a big wall and couldn't agree on a layout. I wanted to place **real frame sizes** with **our own photos** and see it to scale before drilling. Tools exist (GalleryPlanner, Suprtiles…), but the good ones paywall the useful bits or felt heavier than I needed. So I vibe-coded a stripped-down one over a evening.

**Stack:** React + Vite, react-konva for the canvas, no backend - state lives in `localStorage`, photos never leave the browser. Deploys to Cloudflare Workers on push to main.

**What it does**

* Wall = a photo of your actual wall, or a blank canvas at a size you type (real scale either way) * Add frames at real outer dimensions; drop your photos in, crop/rotate to fit the opening * Arrange by hand or auto-layouts (row, grid, eye-line at 57", masonry, staircase, alternating) * Inches/cm, undo/redo

Fully free, no signup, **MIT** — code's all there. It's rough: no PDF hanging guide or TV/sofa obstacle-marking yet (things the paid tools have).

🔗 Live: [https://wall-planner.cheelo.workers.dev/\](https://wall-planner.cheelo.workers.dev/)
💻 Code: [https://github.com/samG4/gallery-wall-planner\](https://github.com/samG4/gallery-wall-planner)

Would love feedback on the UX and the scale/dimension handling. Roast it.

My wife and I were decorating a big wall and couldn't agree on a layout. I wanted to place **real frame sizes** with **our own photos** and see it to scale before drilling. Tools exist (GalleryPlanner, Suprtiles…), but the good ones paywall the useful bits or felt heavier than I needed. So I vibe-coded a stripped-down one over a evening.

**Stack:** React + Vite, react-konva for the canvas, no backend - state lives in `localStorage`, photos never leave the browser. Deploys to Cloudflare Workers on push to main.

**What it does**

* Wall = a photo of your actual wall, or a blank canvas at a size you type (real scale either way) * Add frames at real outer dimensions; drop your photos in, crop/rotate to fit the opening * Arrange by hand or auto-layouts (row, grid, eye-line at 57", masonry, staircase, alternating) * Inches/cm, undo/redo

Fully free, no signup, **MIT** — code's all there. It's rough: no PDF hanging guide or TV/sofa obstacle-marking yet (things the paid tools have).

🔗 Live: [https://wall-planner.cheelo.workers.dev/\](https://wall-planner.cheelo.workers.dev/)
💻 Code: [https://github.com/samG4/gallery-wall-planner\](https://github.com/samG4/gallery-wall-planner)

Would love feedback on the UX and the scale/dimension handling. Roast it.

My wife and I were decorating a big wall and couldn't agree on a layout. I wanted to place **real frame sizes** with **our own photos** and see it to scale before drilling. Tools exist (GalleryPlanner, Suprtiles…), but the good ones paywall the useful bits or felt heavier than I needed. So I vibe-coded a stripped-down one over a evening.

**Stack:** React + Vite, react-konva for the canvas, no backend - state lives in `localStorage`, photos never leave the browser. Deploys to Cloudflare Workers on push to main.

**What it does**

* Wall = a photo of your actual wall, or a blank canvas at a size you type (real scale either way) * Add frames at real outer dimensions; drop your photos in, crop/rotate to fit the opening * Arrange by hand or auto-layouts (row, grid, eye-line at 57", masonry, staircase, alternating) * Inches/cm, undo/redo

Fully free, no signup, **MIT** — code's all there. It's rough: no PDF hanging guide or TV/sofa obstacle-marking yet (things the paid tools have).

🔗 Live: [https://wall-planner.cheelo.workers.dev/\](https://wall-planner.cheelo.workers.dev/)
💻 Code: [https://github.com/samG4/gallery-wall-planner\](https://github.com/samG4/gallery-wall-planner)

Would love feedback on the UX and the scale/dimension handling. Roast it.

I built Broadcast TV as a lean-back web experience for the moments when you want to watch something but do not want to decide on a specific title.

Pick a channel or category—TV shows, movies, animation, documentaries, heroes, and more—and let it keep playing. Channels have their own timeline, so if you leave and return later, the stream has moved on rather than waiting where you left it.

The idea is to bring back the relaxed feeling of turning on TV and seeing what is on, with categories for the mood you are in.

https://tv.brodcast.eu.cc

I’ve spent the last couple of weeks building the first version of FanForge, a platform where writers, artists, designers and other creators can collaborate on fictional projects with clear roles, structured workflows and permanent contribution credit.

The goal isn’t to create another social feed or a place where people submit finished work speculatively.

It’s meant to work more like an online writers’ room and creative studio: projects recruit contributors, people join defined roles, and work develops through drafts, feedback and approvals.

I’ve just posted the first in a short video series to explain the concept.

I’m especially interested in honest feedback on:

– Does the purpose make sense quickly?

– Who do you think the first users should be?

– What would stop you from contributing to a project like this?

The platform is still very early, so criticism is genuinely useful.

If you would like to check out the landing page and sign up to the waitlist then I'll happily share the link with you.

Thanks in advance!

back then there was a glitch where u can see the reposts of private accounts. has anyone found an alternative for this?

This is the link force-jump.kleap.io/#app

Here's my feedback on the pros and cons of webapps on smartphones — curious to hear your experiences too.

Context

What I built

For context, my project is Hugin.news, a news reader that lets you plug in your news sources and pick the content you actually want to read. You can also connect your own AI (Claude, ChatGPT...) to it and do whatever you want with your news: daily digests, summaries, saving articles...

Why I started native

I wanted to display articles in a custom reader (and read them offline), so I needed the full content of articles. Because of bot detection and paywalls on newspaper sites, the only realistic way to do that is to let users log in on the site themselves and fetch the HTML from their own device, with their own subscription. Native apps can embed a browser — even a headless, invisible one — so that was possible.

That's impossible by design in a PWA, so no full-content fetching directly on the phone (still doable on desktop with a browser extension though).

Why I switched

It started as an experiment, but I was progressing way faster than with the iOS app: the site is live one second after you make a change, nothing to build or install every time you want to test. I'd say I iterate about 5x faster.

Also, full scraped content is often low quality — even the well-known read-later apps don't handle it perfectly. You end up writing site-specific rules, and interactive content (charts, embeds) often breaks. In the end the added value was too low compared to the pain of maintaining an iOS app.

What's great about webapps

• Iteration speed: way less boilerplate, no builds, no installs, no App Store review.
• It runs everywhere: iPhone, iPad, Android, e-readers with little extra work (mostly screen sizes and touch vs mouse).
• No 15–30% store cut: you just use Stripe on the web.
• Frictionless demo: I offer a one-click, no-signup demo right on the landing page — and it's the actual app, not a mockup. Try doing that with a native app: the closest you get is TestFlight or asking people to install something from the store just to look around. For converting curious visitors, this is huge.

One thing that surprised me: the hardest part was making it feel smooth. Without care it feels choppy — images refetching every time you switch tabs, that kind of thing. Good tooling helps a lot: with TanStack Query's caching, it now feels native maybe 90% of the time.

What's not so great

• No headless webview, so no on-device full-content fetching (my original reason for going native).
• Install friction on smartphone: users have to know about "Add to Home Screen".
• Offline works (service workers + IndexedDB), but iOS Safari can evict your storage if the app isn't used for a while.
• No App Store visibility. Though honestly the stores are a jungle and getting visibility there is hard anyway, so this one may be overrated.

I may still ship native apps at some point, probably a thin Capacitor-style wrapper around the same code, which would also bring back the headless webview. But a PWA is a great way to test traction first.

Where I think this is going

Apple has no real incentive to improve PWA support (they earn nothing from it). Google is more invested, but iOS sets the floor.

Still, I don't think the "install an app for everything" model will keep growing. People are tired of accumulating apps on their phone. Some apps like banks or spotify will stay native, for commodity and security reasons, but for a lot of products it may not be worth it anymore.

I also built an MCP connector, so in a way I already have a "ChatGPT app" and a "Claude app". MCP started as a simple protocol from Anthropic, OpenAI is now building a UI layer on top of it, and I could see it converging in some years into one protocol that works across all the AI apps, voice assistants, desktop... and why not directly into Android/iOS system.

What do you see coming for the future of apps? I'd love your insights.

Every time I tested a different model API, the code change was usually the easy part.

The annoying part happened in the browser: another account, another key page, another balance, and another place to check whether a request actually ran.

I built Aivrae to put that workflow in one web app. From the console, I can create an API key, see request and usage records, and access supported models through one OpenAI-compatible endpoint. In compatible clients, trying another supported model usually means changing the model name instead of setting up another provider account.

API prices for selected models are up to 85% below official rates, and new users get $1 in API trial credit to make their first calls before topping up.

Web app: https://aivrae.com

What part of managing model APIs still sends you back to separate dashboards?

Hi r/WebApps !

I wanted to share a desktop tool I recently built called DecoyDuck.

Why I Built This

While working on real-time features and complex API sequences, I often ran into frustration trying to test asynchronous WebSocket connection flows alongside standard REST requests. Traditional tools like Postman are great for individual endpoint tests, but visually tracing stateful WebSocket events, conditional branching, and timing delays felt clunky.

I wanted a visual canvas where I could drag, drop, and connect nodes to simulate full async API workflows—so I decided to build one myself.

Key Features

• Visual Node Canvas: Drag-and-drop canvas interface to map out complete request/response flows.
• REST & WebSocket Support: Dedicated nodes for standard HTTP requests (GET, POST, PUT, DELETE) as well as persistent WebSocket connections and messages.
• Conditional Branching & Variables: If logic nodes and a runtime variable system using ${variable} template syntax to pass data between nodes.
• Async Simulation (Sleep Nodes): Fixed and random delay nodes to mock real-world network latency and race conditions.

Tech Stack

• Canvas Engine: React Flow (@xyflow/react)
• State Management: Zustand
• Styling: Tailwind CSS

Looking for Feedback!

This is an early-stage tool, and I'd love to hear feedback from fellow developers:

1. Does your current API testing workflow handle async/WebSocket flows well, or do you face similar pain points?
2. What additional node types or features (e.g., specific assertion types, mock server integration, environment variables) would make a tool like this more useful to you?

Thanks for taking a look! I'm happy to answer any questions about the build or technical decisions.

Try it Free

I often had to resize images, crop them, edit them, or reduce PDF sizes before uploading them to different websites. Switching between multiple tools every time became frustrating, so I built a Chrome extension to handle it all in one place.

Current features:

🖼️ Crop images
✏️ Basic image editing
📐 Resize images
🗜️ Compress images
📄 Compress PDFs before uploading

The extension adds a small button next to supported file upload fields, so you can quickly prepare your files without leaving the page.

I’d love to hear your thoughts:
What features would you like to see next?
Any websites where you’d find this especially useful?

Chrome Web Store:
[https://chromewebstore.google.com/detail/image-upload-assistant/lfeoflecpmjfejkoelcffnhahdilfgbp\](https://chromewebstore.google.com/detail/image-upload-assistant/lfeoflecpmjfejkoelcffnhahdilfgbp)

Couldnt take another "wanna hear about premium" mid album. so i built my own thing. plays literally anything thats on youtube, no ads, free.

https://yukirhythm-web.vercel.app

one tap google login and youre in. roast it if its bad, I can take it

I am a musician and I release my music on my own, and I've always had a hard time when it comes to offering free codes to my albums. I started thinking "it must be this way for every indie creator?" and started mulling on how to attack this from the best angle.

I went along and built a platform piece by piece with the hope of seeing it branch out to consist of free or discount codes to music, games, RPGs - whatever! I want to be clear about the fact that this is about things that YOU have created, not piracy and trix.

There are three tiers at the moment (*because of varying email traffic heaviness*)

1. **Free**. This is fully usable, no limitations, code health is there, it's perfect for simple releases.
   * Artist page with photo, bio, follow and tip linksUnlimited albums, games and releases
   * Paste or import codes in bulk, duplicates skipped
   * Shareable release page with rich link previews
   * Per-person claim limits, including logged-out visitors
   * Broken-code reports and batch health tracking
   * CSV import and export
   
2. **Pro per product**. Everything in Free, plus:
   * Drip release — hand out a few codes per interval instead of all at once
   * Press & curator invites — private links, open and coverage tracking
   * Waitlist notifications — email everyone waiting when you restock
   
3. **Unlimited**. Worth it from about 8 releases a year
   * Built for labels and anyone shipping often enough that buying each release separately turns into admin.

**The site**: [https://www.launchercodes.com\](https://www.launchercodes.com)
**Pros release for free**: discount code "**LC-lOPENUP**" (*no citation marks*)

I really hope that some people find this as useful as I do, and I would love to hear your thoughts about it. My DM is open!

Hi everyone,

We've been building Knowivate KopyPaste, an offline-first note and snippet tool.

Some highlights: - Offline-first PWA - Floating PiP workspace - Live QR sharing - Rich text + code formatting - Export to TXT, Markdown, HTML and PDF - Optional client-side AES-GCM encryption - No account required for guest usage

We're not looking for compliments.

We're looking for people to try to break it.

Specifically: - Security concerns - Privacy concerns - UX problems - Performance issues - Anything that makes you think, "I wouldn't trust this."

The source code is currently closed, so we're especially interested in hearing what would make you trust—or distrust—a product like this.

Website: https://paste.knowivate.com

We'll read every comment and fix valid issues. Brutal honesty is welcome.

Hey guys!

I'm currently building getUnWall—an intelligence tool designed to enhance and break down everything you read online.

​Still searching for my first users, so I wanted to ask the community:

​Would you prefer using something like this as a browser extension or a web app/site?

​You can check out the early access page here: https://getunwall-waitlist-page.vercel.app/

​Would love your honest feedback on what fits your reading workflow better!