It would also be great if not only the owner, but every viewer/editor of the file could see annotations and measurements in Design mode without needing Dev mode like now.

I totally agree with ​@Nellya . Why can’t a viewer see these things? 

I was so excited to see this feature, but it added nothing for my Product Owners. The annotations have to basically be duplicated with our own custom built annotations so the Product Owners can build out tickets. So yes, it improves the annotations for devs and designers, but the rest of the team is left out.

I like this feature a LOT for documentation purposed!

REQUEST: I do want to be able to drag the annotations to organize them within the vertical columns so that the order is more inline with the content and easier for the developers to follow.

I was also super happy when I saw the annotation feature. But my happiness lasted only three days. The button to create annotations simply disappeared. The ones I made are still there, thankfully, but I'm afraid of losing them too...

Probably Annotation and Measurement tools were removed from the free Starter teams and only available in paid plans now

It could be better if we can toggle the visibility of each annotation. Like something: I can see where it has some annotation but this only shows up when I pass mouse over. To clear our documentation

Agree with Michel A.  I do love the new annotations especially with the custom tags, however I liked the interactivity of them in dev mode previously.  We often utilize these for dev and behavior notes, but with them either always on or always off, you have to really space out your annotations so it doesn’t cover other content.  If there was a way to implement something like before where you just see a summary of the # of annotations attached to the frame and when you click on that frame the notes show, that would be a great in between from the previous dev only annotations.

Love the annotation feature….very useful and helpful…
Would be nice if I could place them where it makes sense and it not just snapping to the middle of a frame or the side...sometimes it obscures screen flow lines.

Also, if I fail to match the target element, I'd like to reassign the annotation to another element.

very slapdash at the moment, great idea and nothing i cant build myself (i already built design annotation components to add to designs anyway and theyre better than the new figma ones) but its a start I’m sure they’ll improve over time, e.g. needs:

• reassignment
• change positioning
• change visibility
• link to data etc

Have to disagree with  ​@Nellya here. 
What’s the purpose of dev-mode if all the features are shown in design-mode?

I feel it’s better to keep them separate and show based on roles. Annotations and Measurements are meant for developing, so they are better suited to be shown in dev-mode. 
Showing them in design mode will just make the UI that much more cluttery. 
And to make it worse, hiding annotations/measurements in design-mode also hides in dev-mode! A big blunder, if you ask me. Hiding in design mode should not hide in dev-mode. 

It could be better if we can toggle the visibility of each annotation. Like something: I can see where it has some annotation but this only shows up when I pass mouse over. To clear our documentation

 

I like the previous annotation interaction better, now it covers other information and it’s annoying. it should be based on your zoom level/ click to see the whole annotation or just a sign that there is an annotation in that place to optimise the use of real estate.

Love the feature.  Hate how it was rolled out. Viewers must be able to see annotations. If this isn't a bug, then it's an extremely short-sighted decision, possibly a misguided attempt at monetization.

As someone working for a SaaS company, most of my viewers are internal stakeholders—sales teams, product managers, and executives—none of whom are developers. Expecting them to become developers just to fully understand a project is absurd. And for those working with external clients, this issue is even more frustrating. Under the current setup, you'd have to grant a client developer access just so they can see project annotations, which makes no sense.

While component-based annotations and comments provide a workaround, they are a poor substitute. This approach is frustrating, but at least it doesn’t result in additional charges just to let people see how something is supposed to function. Restricting annotation creation to full and developer subscriptions is understandable, but limiting visibility for viewers? That’s a serious misstep that results in a frustrating and inefficient experience for Figma users.

In which plans can annotations be viewed? Our team members with 'can view' access can't see my annotations, only the colored numbers.

You need a full or a dev seat in any paid plan to see them

This feature would be a game changer if everyone including those who are view access only, we have so many people who need to be able to view annotations but this feature is essentially unusable now since the entire team needs to be able to view them, not just designers and devs.

It has made my life so much easier. I was using a plugin earlier for putting sticky notes everywhere for developers now this has become easier.

It is absolutely absurd that user’s without a full or eng seat can’t see annotations. I have PM users who just view files (or have figjam seats) and the annotations are useful for them as well. Feels like a money-grab by Figma. Very disappointing 

I love the new annotation feature. Few points of interest to flag from my experience with them.
 

• In full screen mode it would be nice if they persisted without having to tap on (y) so they can be used in conjunction with move tool (v).
• Upon copied a component an annotation is connected to, don’t copy annotiation
  • I use annotation when creating not just for dev handover and this becomes annoying very quickly
• It would be great if we also have an annotation tool for flow direction. A line to connect a button click to the next screen.
  • One that it’s as stringy as the prototype lines.  
• Choose if the annotation appears top, bottom, left, right of component it is attached to