Okay so, I’ve played around with Dev Mode a bit, and watched/read what was put out over the last couple of days; and I have a question.
What is the workflow supposed to be for a designer making changes?
Let’s walk through an example.
I have an application with a login page. The client has signed this off, we’ve just marked this for “Ready for development” and saved it as a new version inside of Figma. Awesome, now the developers can get to work.
Meanwhile, the client has come back and said they would like to try a new button colour on the login page. That’s fine, let’s try out some new colours.
This presents a problem now though, no?
Any changes I make to that button colour, will be shown to the developers in Dev Mode.
I don’t want to remove the “Ready for development” status for the Login page, as we’re still iterating through concepts, and there’s no need to stop development on the page until we decide on a new button colour.
My expectation on how this would work would be similar to how it works for developers in their workflows.
The designer would be working in a “designer” mode, where I can make as many changes and iterations as I wanted. But the developer wouldn’t see those changes until I published them to a new developer version of the file (this would be similar to how you can select what components you want to update when publishing a shared library - I should be able to select what sections/frames I want to publish to the new developer version).
Currently the way that Dev Mode is implemented, I still have to separate developer and designer frames. We need developers working on pages that have been approved by the client, and we need designers to be able to iterate on those pages with the client, but without the developers seeing those changes until the client agrees to a new version.
Am I missing something here? I didn’t think this would have been an unusual case.