zealer

Hi HN,

I built FunBox (https://funbox.space) because I was organizing a board game night and got frustrated with existing "online dice" and "random team generator" sites. Most of them are riddled with aggressive ads, require sign-ups, or feel like they were built in 2005.

FunBox is a collection of 8 interactive tools: - 3D Dice Roller & Coin Flip - Scoreboard (track scores for multiple players) - Spin Wheel & Random Picker - Team Generator - Timer & Counter

*The Tech Stack:* - *Framework:* Next.js 16 (App Router) - *Styling:* Tailwind CSS v4 - *State:* Zustand (for complex game states like scoreboard history) - *Animations:* Framer Motion + Canvas Confetti - *Audio:* Howler.js - *PWA:* Fully installable on iOS/Android

I focused heavily on the "feel" of the app—using haptic feedback patterns (via `navigator.vibrate`) and smooth animations (like the inertia on the spin wheel) to make digital tools feel tactile.

I'd love to hear your feedback on the UX or suggestions for other "party tools" I should add! Check it out: https://funbox.space

Hi HN,

I built JigsawPuzzle.pro, a simple web app to play jigsaw puzzles and create custom ones from your own photos.

The key feature is that it's *privacy-first*: - All image processing happens locally in your browser (using Canvas). - Your uploaded photos are never sent to a server. - No signup or registration required.

*Tech Stack:* - *Frontend:* React + Vite - *Canvas Library:* React Konva (for the puzzle mechanics & drag/drop) - *State:* Zustand - *Styling:* Tailwind CSS - *Format Support:* Uses `heic2any` to support HEIC photos from iPhones directly in the browser.

I wanted to create a clean, distraction-free experience without the typical "freemium" bloat found on many puzzle sites. Progress is saved locally via `localforage`.

Would love to hear your feedback on the controls and "snap" feel!

Thanks! By the way, I just launched a Time Capsule feature. Would love to have you try it out!

yes, you r right

That's a valid concern and the classic 'chicken and egg' problem of web-based cryptography. You effectively have to trust the delivery mechanism (the server) every time you load the page. My goal wasn't to replace GPG or Signal for high-stakes whistleblowing, but to lower the friction for ad-hoc sharing. Sometimes you just need to send a password or API key to a coworker, and the alternative is often sending it in plaintext via Slack/Email because setting up PGP is too much friction for the other party. To mitigate the trust issue as much as possible, I've kept the source minimal and readable so it can be easily audited in the 'View Source' or DevTools.