Handling product feedback (images, video) first-class

Get Help
1

Hi all,

Our company is re-evaluating our product feedback loop and the pains we have with Clickup.
I am again evaluating whether I can move our company over to Fibery.

I really like the Highlights approach and the vision outlined in the blog posts around it.
I am a huge fan of the idea of Fibery, but I’m blocked by concrete flows that I can’t seem to replicate easily in Fibery.

One flow that we desperately want to retain is doing the in-house product feedback/QA loop done properly in whatever tool we pick.
Meaning, we can do a quick QA with a video recording or image, and mark points in the image/video while being able to connect them tasks in our task management tool (Fibery).

E.g.: Clickup has a flow in which you can attach an image to a entity and then annotate the image fully from within Clickup. The same can be done with Video, which is timestamped. The flow looks pretty much like: MarkUp.io.
You can click on an image and add comments to it and discuss as a team.

My hope/requirement is that this flow can be replicated using Highlights somehow.
I am even willing to go so far as dedicate inhouse frontend team time to realize this.
Ideally it exists natively in Fibery so our team don’t all have to install extensions.

2

Hi, unfortunately Images/Videos annotation functionality is not in plans for foreseeable future. Fibery can transcribe videos into text, but not sure it will be good enough. And for images we have nothing.

Maybe you can use third-party tool and setup integration to Fibery? It seems MarkUp can do it Zapier x MarkUp.io Integration

1 Like
3

Thank you for the quick reply.

I guess I’m hesitant of using a workflow that sits outside the context of my project management tool, losing ability to reference context while writing the feedback, and having subpar UX when a developer/designer tackles the feedback.

To be clear; the “best” workflows then currently possible would be:

Creating feedback:

  • Going into an external tool like MarkUp.io, and create the feedback
  • Create a specific entity that serves as the media target in Fibery
  • Create entities for each annotation on the media target in Fibery

Consuming feedback:

  • Open up MarkUp.io, to have context & UX on annotation interactions.
  • Go through annotations in Fibery to tackle feedback / task management - do not discuss on the external tool.

Following the blog posts and development of Fibery over the years, I am still unsure on how to use Fibery sometimes as a startup doing product development.

I really liked reading How Fibery Uses Fibery in 2024 and I think it gave real value to seeing how to setup Fibery. I’m a firm believer of the thoughts behind Fibery; bi-directional linking and annotating links like Highlights.

However, I’m curious as to what the feedback loop looks like in Fibery?
How do you tackle a design feedback loop such as described above?

Is it done purely in Docs/entities, is the lack of media annotation not an issue?
Or do you use external tools and then load the data into Fibery and consider it a one way sync with the external tool?

4

All functional decisions are discussed in comments for a Feature.
Sometimes small changes about UI also discussed there.
We use Figma, so if we need to collaborate with a designer, we just go to Figma and provide feedback via Figma comments, and we just embed Figma mockup into Fibery, so it is easy to jump to Figma from a feature.