Building a better model page

Honestly, when we launched the model detail page last November, I was not proud of it. It had the basics. Name, description, who made it, what machine it runs on. But if a developer came to it wanting to actually understand a model, we were not really helping.

I knew what I wanted it to be. If you have used any of the better platforms in this space, you know what a good model page feels like. You land on it, read about the model, run it right there in the browser, and see how it has changed over time. We needed to build that on WriftAI.

It took us seven months to get here. Today the playground and version history are live.

What that first version taught us

The feedback was consistent. The page was useful but it did not help developers actually try a model. To really test something, you had to start writing code before you could see if it even worked. That is a lot to ask of someone who is still just looking around.

The other thing was versions. Teams needed to know what had changed before deciding to move to a newer one. The information was there but it was hard to find, and the way it was shown did not help you decide.

Those were the two things I most wanted to fix.

The playground

The playground lets you run a model right from its page. It shows you a form, you fill it in, and the result shows up right there. No code, no setup. One thing I was clear about from the start: the result had to appear on the same page, not open somewhere else. When you are still making up your mind about a model, losing where you were just puts you off.

The first time I used it properly I thought: this is what the page should have been from the start. Trying a model finally felt like something quick you could do before deciding if it was even worth your time. You are not committing to anything. You just run it and see.

That sounds simple but it actually changes a lot. Developers trying out models go through many of them. Anything that makes that faster changes which ones they end up using.

Version history

Every version of a model now has its own page with a date and whatever notes the author has written. You can see the full history in one place.

For teams who use models in production, this matters. If the model you are using gets a new version, you need to know what changed before you decide whether to move to it. Before today you had to go looking for that yourself. Now it is just a page you open.

I wanted this right on the page and not hidden away. Seeing it laid out properly makes things much clearer. We show the newest version first, so the first thing you see is always what changed most recently. Each version also gets its own link. If you want to share a specific version with your team, you just send it.

What is still missing

We are still working on letting users send files directly to a model from the browser. Some models need an image, a voice recording, or a document to work with. That is still coming. There are other things on the list too. We will get to them.

The goal I have always had for this page is simple. A developer should be able to land on it and leave knowing everything they need before they start. What the model does, what it needs from you, what versions exist, what changed between them, and whether it actually works for what they have in mind. We are closer to that today. We are not there yet.