Adding Dropbox is just adding another layer of auth, sharing permissions, storage quotas, etc.... ugh
Adding Dropbox is just adding another layer of auth, sharing permissions, storage quotas, etc.... ugh
Instead of the native: Screenshot/recording --> clipboard --> Slack
Now you have Screenshot/recording --> clipboard --> Dropbox capture + permissions/billing --> Slack
Why would Dropbox insert itself into a process that works fine without it and adds no benefit?
It's like instead of copying & pasting a paragraph of text into Slack, you use an extension that makes a GDoc of it and then links to that. But why?
Could you list some examples of software that require you to go through permissions or billing for every usage? Otherwise, this is a made-up concern.
Sure, it's fixable, but again why introduce the complexity when Slack and Jira ALREADY LET YOU PASTE IN RICH MEDIA and handle permissions and sharing internally?
What does Dropbox Capture add that makes it worth the extra hoops? The markup? The embedded avatar? I just fail to see the worth of this product...
I’ve never heard anyone complain about granular permissions for potentially sensitive documents. However, your “issue” is entirely made-up, because you can easily generate an “Everyone” link in gDocs.
> Slack and Jira ALREADY LET YOU PASTE IN RICH MEDIA and handle permissions and sharing internally
Slack & Jira are for different use cases/audiences, and handle significantly less rich media than gDocs can. However, if your company is shoehorning gDocs into situations where you could type into these other tools, that’s a social problem, not a technical one.
> What does Dropbox Capture add that makes it worth the extra hoops?
Given their positioning and competition, I’m going to assume there are very few “hoops” in their UX.
> I just fail to see the worth of this product...
Honestly, from reading the rest of your rant and misplaced anger, I don’t think you’d be able to clearly see product value anyways.