You can vibe code this in an afternoon.

Every so often someone looks at Ubikron and says they could vibe code it in an afternoon. With today's tools, they could probably build something that looks like it. I'd encourage them to try.

Then I'd ask them to check back in a week.

Because the hard part was never the screens. The hard part is what happens when you click on a node. What should happen? What should the panel show? What happens to the selection when you switch tabs? Where does a clipping go when you drag it, and what does it remember about where it came from? We spent more time on questions like that than on anything else, watching investigators work and changing the behavior until it got out of their way.

Then there's everything underneath: a server that holds years of captures for a whole team, search that stays fast on a big project, enrichments that keep working when the provider changes their API, an update path that doesn't lose anyone's data.

The test

Here's the test I'd suggest for any tool, ours included. Does it still work in a year? And do you still remember how to use it next week, when you're tired and the case is urgent?

If your afternoon project passes both, I'd honestly like to see it.

Roelof TemminghFounder, Ubikron