Email for one thing. Chat for another. Docs somewhere else. Tasks in a different app. A CRM you barely check. a dashboard for the numbers nobody looks at until month-end.

You are not working anymore, you are doing tab archaeology, digging through six apps to find the one message that had the answer.

We got tired of it too. So we built Unified Orbis, one workspace where chat, tasks, epics, sprints, kanban boards, docs and calendar actually live together instead of sitting in separate silos pretending to be a stack. Orbis ai sits underneath all of it, seeing the whole picture instead of just whatever app happens to be open.

Hey Product Hunt!

I m Scott, the solo iOS developer behind Retrieve.

Hey PH community

Tomorrow I'm launching Triply.now and I wanted to share the story behind it before the big day.

I'm Raquel, a self-taught solo developer based in the Netherlands. I built Triply entirely alone Flutter, Python/Flask, Claude AI, Supabase, Stripe, Vercel, Render. No co-founder, no funding, no team.

The idea came from my friends and my own travel fails. A friend showed up to a temple in Morocco in the wrong outfit. Another one didn't know tipping in Japan is considered rude. I had the wrong adapter in Switzerland and I once brought my hair dryer to Boston and couldn't use it European voltage, American outlets. Triply would have told me that before I packed. These aren't rare every traveler has been there.

One thing I kept running into while building UploadPack was how much effort creators can invest before they know whether an idea has much evidence behind it.

Research, competitors, positioning, titles, thumbnails it can easily become hours of work before production even starts.

How I automated machine-readable files (JSON-LD & MCP) for site owners for AI compensation

Like a lot of independent publishers, I ve spent years building content sites, only to watch AI crawlers harvest everything completely unchecked while the legal landscape for data licensing remains a total mess.

I realized that the biggest hurdle for normal site owners isn't just wanting fair compensation; it's the technical friction. Major AI labs and applications look for machine-readable discovery files, RSL policies, and structured registry feeds to know if a site is legitimate. But most independent WordPress publishers don't have the time or coding background to manually manage JSON-LD schemas or Model Context Protocol (MCP) endpoints.

Got zero mentions across all four.

Spent the last few days building what's basically the standard GEO playbook now, llms.txt, markdown mirrors of every page, honest comparison content against competitors, the works.

Then actually ran the test instead of assuming it worked: asked all four models "what's the best calorie tracking app" a handful of different ways. My app came up exactly zero times. Not even cited as a

source. Same five competitor names every single time, regardless of engine.

I've been building a workforce/attendance tool for the past few months, and the more I talk to other founders and operators, the more I realize this is a genuinely unsolved problem for a lot of small teams.

The core tension: too much oversight (screenshots, constant check-ins) makes good people feel like suspects and quit. Too little oversight means you find out something's wrong months later, usually during a payroll or client audit.

I ended up building something (Trackly) to sit in the middle, GPS-verified check-ins visible to both employee and manager, no hidden tracking. But I'm genuinely unsure if this is the right model, or if there's a better approach other builders here have found.

A few real questions I'd love this community's take on:

Now: Kayva is live on iOS + Android. Talk to Kessa  she reads your watch, tells you why you feel off, cites the science, and gives you one thing to try tomorrow. Not a score. Not vibes. Citations.

Next: Your health becomes a continuous story  quiet when you re fine, nudges when you drift, a GP-ready brief when you choose to share it. One companion from daily life family care.

I m building a to-do app with a twist: completed tasks are never deleted.

Instead, they stay on the page as a record of your effort and growth.

Think of it as writing a book every tasks completed is one section you wrote.