One thing surprised me while building RovaSpace.
One thing surprised me while building RovaSpace.
Almost everyone says remote work is about communication.
I don't think that's the biggest problem anymore.
The real problem is context.
When you're in an office, you naturally know:
• Who's available.
• Who's deep in work.
• Who's collaborating.
• Who's taking a break.
You don't ask for that information.
You simply notice it.
Remote work removed that natural awareness.
So we replaced it with messages like:
"Are you busy?"
"Got a minute?"
"Can we jump on a call?"
Those small interruptions happen dozens of times every week.
That's the problem I'm trying to solve with RovaSpace—not by tracking people, but by making remote teams feel naturally present again.
I'm curious:
What's one thing you miss about working in the same office that Slack or Teams still can't replace?
The context point is spot on — "are you busy?" is the most expensive question in remote work because it interrupts regardless of the answer.
What I miss most about in-person: the casual "hey look at this" moment where someone glances at your screen and immediately spots the thing you've been blind to for an hour. No async tool replicates that.
Building viral-machine.com solo so I don't have the interruption problem — but I definitely have the zero-context-from-teammates problem 😄
The single HTML file approach that runs completely offline is a brilliant way to build ultimate trust. When it comes to personal finance, people are increasingly terrified of data breaches, bank-linking vulnerabilities, and subscription fatigue. Giving them a tool with no account, no cloud, and no subscription is the perfect antidote to modern SaaS bloat.
By keeping everything localized to the user's browser or device, you completely eliminate your own server overhead, which is a massive win for an indie maker.
Since it includes everything from expense tracking to savings goals natively in one file, how are you handling local data persistence? Are you relying on browser
localStorage/IndexedDBfor quick saves, or do you have a clean way for users to export and import their data as a JSON/CSV file so they never lose their history if they clear their browser cache?The risk is presence quietly turning into surveillance. I’d make “available / heads-down / away” explicitly user-set and ephemeral; if managers can inspect a history, the context layer becomes another status-reporting system.
This is something I'm truly passionate about since going fully remote as a software dev in 2019. I liked the idea of something like Gather where you get the visual side (looks like an RPG game) but we never implemented it.
You definitely lose that default awareness of who's doing what, who's out of office or in a meeting and who's focused on work and doesn't want to be interrupted. Remote has a whole different feel for obvious reasons and I like how you pointed out that the problem is context.
I'd say the one thing I miss the most is the social side of the office, the small talk or catching up with coworkers in the kitchen, playing a quick game while taking a break etc. But with that said, the office is also a very distracting, noisy and a disruptive place. Now when I do go in the office once or twice a year I get nothing done but we do collaborate more about epics and higher level upcoming projects. I feel a lot more disconnected and some days I don't say anything to anyone else outside of our one scrum meeting in the morning.
Love hearing about surprises while building. I’m working on Finsight AI, an AI dashboard for SMBs, and I’ve also found unexpected challenges in forecasting features. Curious — what was your biggest surprise so far?
Great