Dev Log

AI moves so fast that some features feel old before they ship. I’m exploring what’s new, but I don’t want RightPlace to chase every trend.

I believe RightPlace can become more than WordPress management or one AI feature. One use I keep thinking about is helping teams keep working when their internet isn’t reliable. The business model I’m exploring is how people who already have a RightPlace license can use it to make more money.

For now, sync is the most important capability RightPlace needs as a product. We’re making progress, but it touches important data, and it has to be dependable. So I’m testing carefully before calling it ready. Thanks for sticking with me while I get it right.

Sync is the most important feature RightPlace needs to become a complete product. Until it works reliably, we cannot move forward. That is why this work matters so much.

We can now sync a database between test machines, recover after an interrupted install, and see what happened in our local Monitor. Our Canvas test lets us make changes across several machines and choose how to resolve a conflict.

Local testing recorded 2,781 sync attempts in 24 hours. In a separate relay test, 100 connected clients ended up with the same data after 20 updates.

0Sync Monitor during local testing.

There is still a lot to do, especially making sync efficient with much larger databases. We are not there yet, but seeing it work and having numbers to improve is encouraging.

We have settled on a new kind of syncing mechanism, one we have not seen tried before. As far as we can tell, there is no open-source project doing it this way.

One thing I love about AI is that difficult things are still difficult. AI has not made a problem like this easy, but it is helping people take on ideas that once felt out of reach. It is encouraging to see what people can now attempt.

Some people ask why they should buy software if they can create it overnight. But you cannot DIY this kind of software overnight. Even with the most capable and expensive models, it still takes months of engineering, iteration, effort, and energy to build something like this. Maybe in ten years that will change. For now, AI has not turned this into a weekend project, and honestly, I find that encouraging.

We have been trying two different approaches to syncing over the last six months.

The first one worked to some extent, but not well enough. The second one was much less stable. We are now working through a third approach.

Sync is one of those foundations we cannot work around. If it is not reliable, the product has a fundamental problem, so we cannot keep moving forward until we get it working properly. That is also why there have not been many visible product updates recently. Right now, the work is concentrated on making sync stable enough to build on.

Even with all the AI helping us, there are still some things that cannot be done easily. Sync appears to be one of them.

We have been working through the architecture for syncing in RightPlace.

Sync touches everything: core data, Applet databases, project files, the sync service, and the secure transport between devices. The interesting part is not making one lane work in isolation. It is making the boundaries clear enough that each lane can recover, stay observable, and keep moving without stepping on the others.

We are taking the time to validate the actual flows and keep the model honest as the product grows. More soon.