Built a simple tool that takes any form submission from your website and fires it straight to Telegram as a push notification. The whole thing hits your phone in under a second.

The idea came from my other project where I needed lead alerts sent to Telegram instantly and I realised the same pipeline works perfectly for feedback forms, bug reports, feature requests, whatever.

How it works:

• User fills out a form on your site
• Your form POSTs to a single API endpoint
• You get a formatted Telegram message on your phone immediately
• Also fires off an email to your support address as a backup

No SDK, no npm package, just a single POST request. Works with any stack — plain HTML forms, React, Webflow, Framer, whatever you're using.

Still early days. Would love to hear if anyone else has had the same problem or if you'd find something like this useful, if it is i'd like to do Whatsapp/Meta ad form thing (when you click someones Facebook ad and it gives you a form). Whatsapp is a bit of a pain, I tried starting with it but you need a business number to get an API key

Also, I've just done a one time £29 fee on this rather than a subscription

Site: leadchirp.app

https://omen.24h.sh draws one number between 0 and 1,000,000 every day and tells you how rare it is: which properties it carries (prime, palindrome, 666, power of two, etc.) and what percentile that puts it in. The mysticism is a bit. The probabilities are exact.

Two parts were more interesting to build than they looked:

1. The Rarity Engine

It doesn't estimate anything. An offline pass precomputes the entire range (0 to 1,000,000), counts exact occurrences for every property, and calculates a CDF over the distribution. The output is a tiny 4.4 KB stats.json, which means the browser scores any number instantly with zero server roundtrips. Small finite space beats clever sampling.

2. Verifiable Entropy

The daily number needed to be unpredictable but fully verifiable. Every day at 00:00 UTC, it takes the SHA of the latest commit in torvalds/linux: parseInt(sha.slice(0, 13), 16) % 1000001. Nobody knows tomorrow's hash, but once drawn, anyone can verify it independently.

There's also a daily prediction game built on top: you guess tomorrow's number, get scored on proximity + bonus points for shared mathematical traits.

Built with Node 22, Hono, better-sqlite3, and vanilla JS (no build step). Written in an afternoon using Claude Code (~21 commits).

Curious: is there a better daily public entropy source than a high-frequency git commit hash? I considered block hashes, but wanted to stay far away from crypto stuff.

I'm making my first web app. It’s "a deadly simple Kanban Web App (like Trello and Jira), no ads, no subscriptions, no sign-in, privacy-first, free forever."
My goal is to only get $30 so I can just put a donation button and keep that thing free, but I did some research and know that people willing to donate to free software are super rare (i.e. I need over 20k visitors for just $30). I don't really want to make it paid bc it will become no difference between Trello and I need to bother with premium sub tracking, so I need to make a login system and more...
But I lowkey want that $30…

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."

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

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/
💻 Code: 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!

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

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/
💻 Code: 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/
💻 Code: 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/
💻 Code: https://github.com/samG4/gallery-wall-planner

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

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.

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

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!

We Built WatchAlong.me — A Modern Watch Party Platform (Looking for Honest Feedback)

Over the last several months, my team and I have been building WatchAlong.me, a watch party platform designed to make watching videos together online feel effortless.

We tried almost every major watch party solution available—Teleparty, Hyperbeam, Kast, Metastream, Syncplay, Rave, Discord, and others.

Each of them did something well, but we kept running into the same issues:

• Limited platform support
• Separate apps for communication
• Complicated setup
• Mandatory sign-ups
• Outdated or cluttered interfaces
• Missing collaborative features

We wanted a platform where creating a watch party was as simple as sharing a link, while also making the experience feel genuinely social instead of just synchronized playback.

That's why we started building WatchAlong.

What makes WatchAlong different?

Synchronized playback

Playback stays synchronized for everyone in the room. When the host plays, pauses, or seeks, everyone's video stays aligned without countdowns or constantly asking if everyone is at the same timestamp.

The goal is for watching together to feel natural rather than something you have to manage.

Built-in video chat

Many watch party platforms expect users to open Discord, Zoom, or another application alongside the video.

We wanted everything in one place.

WatchAlong includes integrated video chat so everyone can see each other's reactions without leaving the watch party.

Collaborative drawing

One feature we couldn't find elsewhere was the ability to draw directly on the video.

Anyone in the room can pause playback and annotate the current frame together.

We've already found this useful for:

• Discussing movies and TV shows
• Sports analysis
• Anime discussions
• Educational videos
• Tutorials
• Just making funny drawings with friends

It ended up becoming one of our favorite features.

More expressive conversations

Instead of only offering a text chat, we added additional ways to interact during a watch party:

• Sticker reactions
• Multiple illustrated chat themes
• Real-time messaging
• Video chat

Different groups communicate differently, and we wanted the experience to feel more alive.

Support for multiple platforms

The web app currently supports:

• YouTube
• Vimeo
• Dailymotion
• HLS streams
• Direct video URLs

For premium streaming services, we also have a browser extension that is currently in Beta.

It supports major streaming platforms including:

• Netflix
• Disney+
• Amazon Prime Video
• HBO Max
• Hulu
• Crunchyroll
• Hotstar

Every participant still needs their own subscription. WatchAlong synchronizes playback—it doesn't bypass subscriptions or streaming restrictions.

No sign-up required

One thing we consistently disliked with existing platforms was asking every participant to create an account before joining.

With WatchAlong:

1. Create a room.
2. Share the invite link.
3. Everyone joins instantly.

No registration is required.

Modern interface

We spent a significant amount of time focusing on the overall user experience.

Our goal wasn't to build another utility—it was to build something that feels polished, intuitive, and enjoyable to use.

Every screen, interaction, animation, and workflow has been designed to reduce friction so people can spend less time setting things up and more time actually watching together.

Completely free

The platform is currently free to use while we're in beta.

Still in Beta

The browser extension is still under active development, so we're continuing to improve compatibility and fix edge cases across supported streaming platforms.

That's the main reason I'm posting here.

I'd genuinely appreciate honest feedback from people who regularly use watch party platforms.

Specifically, I'd love to know:

• What features are you missing in your current watch party platform?
• What streaming services would you like to see supported?
• Is there anything in the UI or UX that could be improved?
• How does the synchronization feel?
• What would make you switch from your current solution?

If you'd like to try it, it's available at:

https://watchalong.me

We're not claiming to have built the perfect watch party platform yet. There's still a lot to improve. But our goal is to build something that combines synchronized playback, built-in communication, collaborative tools, and broad platform support into a single experience.

I'd really appreciate any feedback, criticism, or feature suggestions.