It's been three and a half years since we launched ReflectionCloud. We're about to enter our fourth year.

Lately, I've been thinking a lot about where to take this service.

Should we continue as we are? Or should we stop and rebuild from scratch?

Right now, we're moving toward rebuilding.

Why now? What will change?

I wanted to write a bit about that.

Growth and Limitations

We started building ReflectionCloud in 2022.

The priority was to get something out there first. We began with personal reflection, then added goal management, career inventory, and pair-work reflection. Features grew little by little.

For the first year or two, it felt like we were constantly moving forward.

But around the third year, a sense of unease started to creep in.

"I wish I could do more of this" — thoughts like that became more frequent. I wanted to change the design. I wanted to make feature adjustments more quickly. I wanted to add multilingual support.

But these things were becoming increasingly difficult.

Honestly, the question "Is this really okay?" kept circling in my mind.

To Change or Not to Change

Rebuilding a service isn't an easy decision.

Recreating from scratch what we've built over three years takes time. There are people already using it. There are risks.

But continuing as we are also carries risks.

What we can do becomes more limited. What we want to do becomes harder to achieve. When that happens, can this service really deliver what we truly want to deliver?

Thinking about it that way, I started to feel that maybe it's better to change now.

A Matter of Timing

Around the end of 2025, I encountered a new approach to development.

When I saw it, I thought, "Maybe this could help me overcome the limitations I'm feeling now." Looking at the medium to long term, switching now felt like it could make ReflectionCloud a better service.

Timing is a curious thing.

A year ago, I might still have been hesitating. A year from now, it might have been too late.

But now, maybe we can make it happen.

There was a moment when I felt that.

About the Data

When rebuilding, the biggest challenge is data migration.

The reflections you've written, the goals you've set, the career records you've accumulated — how do we move all of that to the new environment?

After looking into it, I found that fully automatic migration isn't possible. For security reasons, password information can't be transferred.

This means users will need to register again with a new password. After that, based on your email address, your past data will be automatically carried over.

At first, I wasn't sure how to feel about this.

But in a way, maybe it's not such a bad thing.

It's an opportunity for a restart. A chance to continue walking together with those who truly use our service.

What's Next

We're hoping to release the new version around April 2026.

Until then, the current ReflectionCloud will continue to work as always. Even after the new ReflectionCloud launches, we plan to run both in parallel for a while.

🔗 https://reflectioncloud.achireth.onl/

We'll share development progress on this blog as we go.

Not just announcements like "This screen is done" or "This feature is working," but also the thought process — "This is where I hesitated," "This is how I decided."

ReflectionCloud is a service that supports reflection.

So, as the people building it, we want to move forward while reflecting ourselves.

That feels like the honest way to do it, at least for me right now.