← Back to blog

2026-04-18 · 3 min read · TruBlue

A Feature Starts With a Question

Most features in Chastity Tracker are not on a roadmap. They show up in a chat, as a side comment, and then turn into something nobody had quite phrased before. The new device management is a good example of how that happens in practice – and of why the more interesting half of a feature is often not in the original request, but in the follow-up question that comes back.

The request

Someone wrote that it would be nice to see, inside the tracker, which chastity device they had worn and for how long. With an option, when locking up, to pick which device was being put on. That was the whole request – one sentence, a clear function, an obvious idea. It would have been easy to drop in a small text field and move on.

The follow-up

Instead, a question came back. Should this be a free-form text field at lockup, where you type a name every time? Or a proper inventory, with photos, purchase price, notes – an actual record of devices that gets maintained over time? And, maybe more importantly: who is responsible for it? The keyholder, who sets the requirements? Or the sub, who physically owns the device?

That last question decided the architecture, not the first one. The answer was clear: the sub maintains their own inventory. They know what is in the drawer, which device is comfortable, which one starts to pinch after three days. Almost everything else follows from that – its own resource in the data model, its own view, write access for the sub, read access for the keyholder. A text field would have been cheaper, but wrong.

The refinement

Then, in the same conversation, came an extension I had not expected. If the keyholder can see which devices are available anyway – why not let them specify, as part of a lockup requirement, which one should be worn? That turns "please lock up" into "please lock up with the blue one", and any deviation gets logged cleanly against the penalty book. The idea came from the user, not from me. It roughly doubled what the feature can do without adding much complexity, because the data model was already in place.

What is there now

Device management is part of the tracker as of this release: a dedicated area where the sub maintains their devices – with photo, notes, an optional purchase price. Wear time is tracked per device. For lockup requirements, the keyholder can specify a particular device, and the penalty book picks up any mismatch automatically. A short overview of all functions lives on the features page.

Think along

If you notice something similar – a gap in everyday use, something that feels clumsy, an idea you have not quite worked out – write to me. The feedback link in the footer goes straight to me. Half of what is in the tracker today started that way. Sometimes the most useful reply is another question, and sometimes the best idea only shows up while you are explaining the first one.