Ever sent a design draft or a staging link, only to get a cryptic message three days later saying "the thingy on the right looks weird"? Yeah, we've all been there, and it absolutely sucks.
TL;DR: What the hell is Iris?
Created by a frustrated designer named Axel who probably got tired of raw Dropbox links and vague complaints, Iris is a new client delivery platform trying to fix this broken loop.
- Cinematic Show-off: Instead of a generic cloud folder, you send your work (slides, docs, galleries) as a slick, full-screen cinematic experience.
- Pinned Feedback: This is the killer feature. Clients drop a pin exactly where they have an issue. No more guessing games or deciphering "the third button from the left under the header."
- Stealthy Analytics: Once you send the link, you see exactly how long they stayed on a slide, what caught their eye, and what they ruthlessly skipped.
- Zero Friction: No client login required. Just send the link and they're in. Honestly, it beats spinning up a cloud vps just to host your custom portfolio site for every client.
What the Product Hunt Crowd is Saying
Looking at the community reaction, devs and creatives are generally hyping it up, but not without some classic nitpicking:
- The "Thank God" Faction: Most users (like Juelz and Mykola) agree that the view tracking is god-tier. The crippling anxiety of "did they even open my link?" is arguably worse than getting bad feedback. Plus, the tracking is completely automatic—clients don't even know they're generating analytics.
- The "Version Control" Nerds: Someone immediately asked about before/after comparisons. The founder confirmed version history is built-in. This is essential for when clients inevitably change their minds and say, "actually, let's go back to version 1."
- The QA Snipers: One user casually dropped in, found a UI glitch where comments move around randomly on different screens, and reported it. The Iris team is currently sweating and hotfixing it as we speak.
- The UX Purists: A few asked if boomer clients can figure it out without a manual. Turns out, it's virtually foolproof: click link, type name, point, and complain. That's the whole interaction.
The Takeaway for us Code Monkeys
There are a few solid lessons we can steal from Iris's playbook when building our own tools:
- Never trust a user's ability to describe a problem: Whether it's a bug report or a design tweak, give them a tool to point exactly at the issue. Eliminate ambiguity.
- Friction kills adoption: "No login required" is a massive conversion booster. Making a client sign up just to view a demo is the fastest way to get ghosted.
- Behavioral data doesn't lie: What users do is way more important than what they say. Build tracking into your MVPs from day one so you know where they spend time and where they bounce.
Source: Product Hunt
