Same question

@Jenia Your frustration is felt, and heard. I’m noticing that this rollout has been especially confusing. Before you make any changes, Tom, on our advocacy team made this video to help explain how you get at code and properties that you’d normally see in the inspect panel, which is now called “Properties” —

Video on Twitter:

I hope this clears up some of the confusion. We’re bringing all of this feedback to the team and hoping we can make some actionable changes to make this clearer. Please reach out and let me know if you have any other questions.

@Rogie_King This is a massive downgrade to functionality we had BEFORE dev mode was ever introduced.

When Figma announced Dev mode, the spirit of the conversation was that we would continue to have these features that were always available once Dev mode came out of Beta. This is a huge rug pull.

David, totally understood this nature of the “downgraded” experience — in your opinion, what are the changes to the experience that feel most negatively impactful?

At least going back to 2020, we had the ability to quickly reference properties directly in Figma. With minimal effort we could visualize, copy, and paste exactly the things we needed.

The recommended approach now is to copy from a context menu that copies code for all child objects of a selection, paste it somewhere else, and then manually find the things we need from a huge paste.

This is way more time intensive than it used to be. I just tried it on a really simple selection and it copied over 700 lines to my clipboard, but I don’t get to see what’s being copied until I paste it somewhere else.

We used to have such an easy way to grab props, and content by toggling between a “<>” code and content view right in inspect.

Please bring this back.

Thanks for sharing this. I was feeling a little gaslighted when people said only the code part was changed because I was sure there were more details than the code part comparing the old “Inspect” to the new “Properties” tab. For non-designers it’s much easier to understand the frame sizing with the image instead of description as well.

Hey all!

tl;dr: Professional Plan does not offer Dev-only seats. Currently, Devs automatically have Design edit rights when they got upgraded for Dev-Mode. This clearly needs some rework! Please remove automatic edit rights from Dev-Mode seats.

Currently we are running on a Professional plan with a small team (2 designers 2 devs).

Today, as the team owner I upgraded our Devs so they can continue using Dev-Mode.

However the upgrade just allows me to set their “Design seat” roles to “Full”.

Since they do not need (and want) edit rights and just want to use Dev-Mode I tried setting them to “Viewer-restricted”.

I assumed this would remove their edit rights and keep the access for Dev-Mode since we have enough seats in our plan. Unfortunately, this does not work. It completely removes access for Dev-Mode.

Figma, please look into this and improve the team management experience and separate the edit rights from viewer-based rights such as viewing files and using Dev-Mode.

The easiest solution would be to simply add Developer seats like in higher tier plans.

Alternatively add a new third role that combines “Viewer-restricted” with enabled Dev-Mode. Design/Edit rights should be opt-in for Developers and manageable since they do not need or want them anyway.

Howdy @Tom_Lowry @Rogie_King ! Curious if there’s any further response on this. Thanks! 🙂

Agree, very annoying and uneccerseraly expensive for small teams who dont need large subscription plans.

Hey Joseph, no word yet, just busy taking all of your feedback and bringing it to the team. Thanks for your patience!

David, appreciate you sharing specifics with me on what is making this a downgraded experience. Super helpful to bring feedback to the team. Working on that now! Let me know if there’s any other things you have feedback on.

With that and the box model view I think there would be less complaints 🙏

Appreciate the work you all are doing to support the Figma community. Regardless of what decisions come on this, grateful for your role in giving Figma users a voice and seat at the table. 🙂 Best!

Appreciate your responses! Looking deeper into it, I see that we have more options now. At the beginning that felt painful.

+1.

Posting my experience to share more cases about the same issue:

I’m the one designer on a 5 person team, rest of the team is developers.

We’ve all agreed having edit-rights makes no sense as it is easy for developers to edit things by mistake, but Dev Mode is tied to “Full file access” which means the development team has to get edit rights in Design mode to use Dev Mode… Which hardly makes sense.

This has created an additional design task: I tend to check our relevant files’ history logs for changes every morning and afternoon to make sure things are still where they are supposed to be.

To be honest, It’s taking so much time and peace of mind away that I’m considering just turning the seats back to “View only” and leave annotations as comments, as I was doing before.

+1 our developers do not need or want full edit access. Figma please solve this!!

Figma - CAN YOU PLEASE give the ability to disable Edit access for Developers using Dev Mode on the Professional Pricing Tier - This is causing major problems with erroneous changes to design files. My team is seriously looking at alternatives like PenPot.

+1 on this! please add dev mode seats to professional plan. I am currently struggling with this since i work as a freelance and i work with various developer right now. I can’t give my own Figma acc just for them to use the dev mode feature!!!

• 1
  
  How can Figma approve this new feature without thinking about consequences, lmao

+1! Please add only dev seats to the professional plan. Full access for dev mode creates too much chaos and unnecessary stress on designers and devs.

Really stupid idea to have dev mode on a design seat with full access and like the rest of the comments here an unnecessary additional price to an already expensive subscription. I work in a small team and there’s no way any of the developers need this kind of access to the design.

We are having the same problem here, for now we gave editors seat for developers, but this is not scalable for small companies. I thing a dev-seat should be created, not as expensive as editor seat, of course.

How long will we need to wait for this to be fixed? The funny thing it says an extra $12/seat for dev-mode but then charges $15 as a regular designer seat

15$ apply if you add the seat on a monthly basis instead of annual.

+1 costs are one thing, but giving developers edition rights make me a little concerned. The chances of making changes by mistake are quite high.