46
On-site feedback
under review
Gary Gaspar
Ability to see past feedback directly in widget. This will help avoid duplicates and would create this feeling of "drop a pin comments" feedback on the site
Log In
Alexandre Croizard
we use marker.io to review elearning modules with our clients, so this is a one page application with multiple screen. hope this feature coul work with a single page app
Bradley Rothery
This would be very helpful to avoid scope creep because during rounds of revisions our clients will sometimes forget to make there edits based on the last round. Instead they'll request completely new changes that wasn't in the scope of work.
m
markus
I would also look at other competitors, theirs works in a similar way and could be a good guiding flag. I switched from them because you have a Clickup integration but this is definitely a feature of theirs I miss. so much easier to get a top down, wholistic view on feedback, who has left it, where it was etc. They use a browser based iframe (i think) in their portal which may be a good option? idk, just putting ideas out there.
Tim Lovell
Definitely need this - Just testing Marker.io moving from Bugherd (for the Monday integration), and this would make it much more efficient across our QA-ers. thanks
Gary Gaspar
under review
Christopher Thomas
Is this feature being considered? We moved to Marker.io from Project Huddle and it's a great improvement but this is the one feature we have really missed. In PH, you click on the mistake on the page and everyone sees exactly where the issue is when they are viewing any page. So you can easily see where people have pinned issues and duplicates become a non-issue. With Marker, we've lost so much time with duplicate comments. When we signed up, we were told it's in the works and being considered but it's not showing in the Roadmap. Overall we're really happy with Marker, but this is a real-life, daily, huge issue for us now. I'd love to know where this stands. Thanks!
Gary Gaspar
Christopher Thomas: Thanks for much for your detailed feedback. This is very helpful, more than you know.
As a matter of fact, we're actively working on this problem, but we're hesitating on committing to a specific solution.
The biggest question we have is: Who can see feedback inside the widget?
A) Should we limit it to only Members and Guests?
B) Or should "unknown visitors" be able to see feedback too?
In solution A, it will require members and guests to always log in the widget (although we could tap into existing authentication system if one is available).The cool thing about this solution is that it's more private, and opens more doors for on-site collaboration.
In solution B, it's the easiest way to onboard people as people can just open the widget, report new feedback, and see all feedback, without needing to log into Marker.io.
What do you think?
I'm happy to hop on a quick call if it's easier.
Christopher Thomas
Gary Gaspar: We're happy to schedule a call and give you more specific feedback if that's easier for you. At this point, we'd be happy with either option. To date, we don't have many clients that are using it. We're using it more for internal comments as we build sites. We do hope to include clients more at some point.
But issues come up when we have different people at different stages going to pages to review them. You really have no idea if anyone else has given feedback on mistakes. So if there is a glaring mistake, like a missing link or misspelled word, 2 or three people might waste time commenting on it.
As it stands, you have to manually look through on the Marker admin console (and we also have Asana integrated) and it is cumbersome and time-consuming to see all the feedback for any specific page. So, some type of widget indicator showing there are feedback items on the specific page would be nice to see.
With PH, the commenter adds a pin (like a map marker icon) directly to the problem area on the page. It's on the front end of the site and all users (or any visitor depending on permission settings) can see that icon and immediately know not to comment on the same issue. PH has many downsides, but that feature is really nice and we miss it.
Again, happy to jump on a call if you'd like to discuss in detail. We really appreciate your concern and help!
Gary Gaspar
Christopher Thomas: Got it, super helpful context. We're making good progress here. I'll definitely keep in you in the loop on this project. This is a very important project for us and it will be the foundation of what comes next!
Christopher Thomas
Gary Gaspar: Any update on this? Thanks!
Gary Gaspar
Christopher Thomas: We did a lot of investigating, and we came to the conclusion that we first need to build some new foundations for the widget, before we can do this. So the plan is to ship, in this order:
- Report feedback without a screenshot
- Capture multiple screenshot from the website to add to 1 feedback item
- Capture video screen recording on your website and add to feedback
- Embed feedback into widget (your request)
While still very much strategic for us, we have to build it in this order for many reasons, including technical dependencies.
As for timeline, I'm hoping we can get all these done in the next 4-6 months.
Christopher Thomas
Gary Gaspar: Make sense. Looking forward to all of these improvements. Thanks for the quick response!
Seb van Dijk
Would be a game changer to avoid too much duplicates!
D
Daniel Cowan
This would be a game-changer for my team. I second what Chris LaFay said about it being URL specific.
Chris LaFay
I would also say that the feedback "view" in the widget should be specific to the current URL.
IE. if you're on domain.com/about, the only tasks visible in that tab would be tasks related to the About page.
Gary Gaspar
Chris LaFay: could not agree more! This is something important to us, as it taps into more collaboration, which we love. Thanks for the insights!
Beata Domagala
That will be a huge help.
Load More
→