Work without the fear of losing it — introducing REFLO’s timeline

In the last post I introduced REFLO as a whole. Today I want to go a little deeper on the feature that sits at the very bottom of REFLO: the timeline. I’ll walk through why we built this one first, how it works today, and how we plan to keep developing it.

A moment almost everyone has had

The working file you were wrestling with late into the night. You accidentally paint over an old layer and hit save. The next morning you open the file and the version you labored over yesterday is simply gone. A client says, “I liked last week’s draft better,” and you have no idea which file that is.

Almost everyone has had a moment like that.

Undo (Ctrl+Z) vanishes the moment you quit and reopen the program. Even in a program with autosave, if the accidental overwrite gets saved too, it does you no good. Cloud storage “version history” exists, but snapshots just pile up at random as things save, so the moment you actually want is hard to recognize. In the end a lot of people copy files “just in case,” stacking similarly named files in a folder and building their own safety net.

That fear is why we built the timeline

When I was sketching REFLO, this was the first problem I wanted to solve. Before flashy comparison screens or a branch feature for new attempts, there was a much more fundamental question.

> “What would it take for the moment you hit save not to be scary?”

No matter how impressive the features, I thought they meant nothing unless the foundation was a belief that “my work is still here, safely, whenever I need it.” So the first thing we made in REFLO, and the thing we spent the most care on, is the timeline. Every other feature is really sitting on top of this.

What the timeline is after

The purpose of the timeline is simple. Even if the user doesn’t think about it at all, just working should naturally stack a history of their own work. And they should be able to look back through that history comfortably whenever they want.

Like save points stacking automatically while you play a game, if REFLO is on and you save as usual inside a protected folder, your work process is recorded quietly without you having to press anything special. Not having to regret “I forgot to save” or “I should have set this version aside” — that’s what the timeline wants to do.

Main timeline features

1. A record that stacks by itself, without you touching it

Whenever REFLO is on and you save a working file inside a protected folder, REFLO quietly records that moment. You don’t have to think separately, “I should save this version.” Work and save the way you always do, and that itself naturally becomes a history of the work.

2. A smart way of grouping that understands the work flow

If every save simply created a new record in a long list, the timeline would quickly become unreadable. So REFLO naturally groups stretches where saves come in close succession into one “work session.” Conversely, if you step away and come back after a fair amount of time (about 45 minutes) to continue, a new session starts from that point. When you open the timeline, you don’t see dozens of individual saves; you see something that looks like the real flow of work — “this morning’s work,” “this afternoon’s work.”

3. Milestones marked separately so they don’t get buried

Separate from the automatic record, when you think, “I really want to set this version aside,” you can pin it or give it a name and leave it as a milestone. Drafts you sent to a client, versions that got approved — those kinds of points. Records you mark this way are excluded from the automatic grouping I mentioned, so they aren’t buried in an automatic session bundle; they show up on the timeline as a distinct landmark.

4. The freedom to go back to any point in the past

You can scroll the timeline as if you were flipping through it, and check any past moment you want right away. You can see with your own eyes, “Ah, it looked like this then,” and if you need to, you can restore the work to that point. Even when you realize late that you went the wrong direction, you don’t have to make it from scratch; you go back to the point you want.

5. The starting point for the other features

The comparison modes I introduced last time (Split, and Pro’s Overlay, Heatmap, and Blink — Flicker in the app) and branches (called tracks in the app, Pro) are features that are only possible because this timeline exists. Because the timeline has been stacking those points, you can pick two of them and compare by eye, and in Pro you can grow a new fork from any one moment. The timeline is the quietest and most important foundation holding up REFLO’s flashier features from behind.

What’s next

I don’t think today’s automatic grouping is perfect. Different people, and different ways of working, may feel differently about “this still counts as the same work session,” so we plan to keep refining the session-splitting criteria with feedback from real users.

Timeline records also stack on the local device first, and if you connect Cloud History they can be kept in the cloud as well. The goal is not to lose the work history you’ve stacked even if the laptop breaks or you change devices.

When collaboration lands, how to put a work history several people make together — not just one person’s — onto the timeline in a natural way will also be an important assignment. We’ll invite a small number of teams to use it together, validate it thoroughly, and then launch it properly.

Closing

The timeline may not be REFLO’s most eye-catching feature. But I think it’s REFLO’s most fundamental promise: the hand that hits save shouldn’t tremble anymore.

In the next post I’ll introduce more of REFLO’s features, one by one, in detail. Thank you for reading.