3 ms·
I like the idea. Workflows are going to be the make or break aspect of the product. It can’t be a thing that leads to distractions or additional work. I’ve had
by ungreased0675 2y ago
I like the idea.
Workflows are going to be the make or break aspect of the product. It can’t be a thing that leads to distractions or additional work. I’ve had coworkers who just love to talk, and I hate it when I’m trying to get something done.
As an example, maybe requiring the talk button to be held down might naturally limit conversations to a few minutes. (Just an idea, maybe it doesn’t)
A way to sync voice with screen recordings would be killer for product development or software testing. A quick “hey, this button doesn’t work when I do this” would be so much faster than making a screen recording and attaching it to a new bug report.
- talksik 2y agoLove the insight. You are correct, the "workflow" is the essence. I call this the protocol, and I've spent thousands of hours on this alone. I have different approaches on screen + commz combo that uphold flowy's product principles of keeping it lightweight, and augmenting human conversation. Your idea around this is really interesting; I agree that this is a "killer" feature if done right. Our bet: flowy is what loom users have been reaching for, but haven't been given.