Keep the original, and still try another path — introducing REFLO’s branches

So far I’ve introduced REFLO’s timeline, comparison modes, and cross-format support, one after another. Today I want to talk about the last piece that completes those three: branches.

A moment almost everyone has had

You’re in the middle of a draft. The direction isn’t bad, but you suddenly think, “What if I made this in a completely different color tone?” You want to try it, but you hesitate. What if I touch this version and can’t get back to how it was?

So what you end up doing is copying the file and naming it something like “_experiment.” A familiar pattern. The “final_really_final” problem from the first post repeats itself here. On top of that, the copied file becomes a brand-new, separate file, completely cut off from REFLO’s timeline. None of the history you’ve stacked so far, and none of the comparison features, carry over to this new file.

It’s the same when a client asks, “I’d like to see drafts in two directions.” You need to grow in different directions from one starting point, but every time you duplicate the file and manage it separately, you start to lose track of which version forked from which.

That hesitation is why we built branches

Even after we’d protected the record with the timeline, made change visible with comparison modes, and protected every file regardless of format with cross-format support, one problem was still unsolved. Creative work doesn’t always flow in a single direction.

Sometimes you have to split from one point into several directions. And the moment you split, you were stepping outside every safety net REFLO had built so far.

> Couldn’t you try something completely different without touching the original?

That’s the question where branches started. You shouldn’t have to leave REFLO in order to experiment.

What branches are after

The goal is simple. Leave the original as it is, and from any point on the timeline, make a new fork and experiment freely. And keep that experiment from becoming a separate file outside REFLO — it should still be recorded and protected the same way inside REFLO. Making experiments that are okay to fail: that’s what branches are trying to do.

What branches look like

Branches (called tracks in the app) are available in Pro.

1. A new fork from any point on the timeline

You don’t have to start a new attempt only from the latest version. On the timeline from the last post, you can grow a branch from any moment you want. If you think, “I want to go a different direction from this version last week,” you start right there.

2. The original stays put; the experiment is fully separate

Making a branch doesn’t affect the original workstream (the main line) at all. Whatever you change or try on the new fork, the original stays right where it is. That’s why you can take a bold swing without worrying.

3. The experiment is protected as the same piece of work

This is where it differs from copying a file. An experiment that forks as a branch stays a fork track inside the same file, so it’s recorded automatically and you can leave milestones. You don’t end up with “it was just a throwaway experiment file, so the history is thin.”

4. Compare several directions side by side

You can pick versions from several branches that split from the same point and look at them side by side with the comparison I introduced last time. For design and image files that’s Split, Overlay, Heatmap, and Blink (Flicker in the app); for documents like Word, Excel, and PowerPoint, text comparison shows the difference. Instead of judging “which direction is better?” by feel, you can decide by seeing it.

5. If you like it, bring it over and continue; if not, just leave it

If you like the direction you tried, you can bring that save into the current flow and keep working. If you don’t, you can leave the branch as it is or clean it up. Either way, the original was safe from start to finish, so you can decide without pressure.

What’s next

The path to bring the side you like into the current flow and continue is already open, but automatically “merging” two forks line by line the way code does is still an area with a lot of unsolved work. Images and design files aren’t something you can merge that mechanically. Which of two directions to keep as final still needs a person’s judgment, so we keep thinking about how REFLO can make that judgment as easy as possible.

And when collaboration lands, I think branches can naturally expand into a space where teammates try different directions at the same time. Questions like who owns which branch, and whether each other’s work collides, we’ll validate carefully with a small number of invited teams, then polish for a proper release.

Closing

I think branches are the feature that creates the feeling that “it’s okay to fail.” Because you know the original is safe, you can actually try something new more boldly. That’s why branches are in REFLO.

In the next post I’ll continue introducing another REFLO feature. Thank you for reading.