Published in


Launching our Figma plugin — better copy handoff to developers and translators

After launching our GitHub integration to edit in-app copy earlier this year, we‘re excited to release our Figma plugin in beta today. It takes us a step closer to our long-term goal of building end-to-end content design software from design to code and back. The Figma plugin gives us a new surface to meet our customers where much of the creative content design process is happening. Stay tuned over the coming months as we’re releasing more great features for our new Figma plugin!

Error-free copy handoff

For new features, handing off new copy usually requires devs to click through design mocks and copy one piece of text at a time into their code. Or, even worse, someone has to create product documentation outside Figma and manually extract the copy from Figma (and then worry about keeping the designs and documentation in sync). Which means each copy string has to be copied twice (design to documentation to code). All this can be error-prone and is time-consuming for everyone involved.

Automatically generate localization-ready code

With our new copy-to-code export feature, Strings automatically generates code that developers can use to start coding the UI with. Here is how it works:

  • Once you’ve installed the plugin, you select the frames to export to Strings.
  • In Strings, you can grab the strings code for each platform file type (iOS, Android and JSON for web) and share it with your developers. They save a bunch of steps needing to dig through design documentation to copy text.
  • We automatically generate the string key names based on Figma design file elements. (Developers can always overwrite them if they use a different convention.) The code generated follows best practices for each file type and is ready for localization.
Localization-ready code

Context-rich handover for localization teams

Many localization teams are organizationally separated from the content design process. When they get copy to translate it is often done “blindly” without the visual context of the design file. We think there is a better way. With Strings, localization teams can view new copy next to the designs without needing access to the entire Figma design file. Writers can add specific instructions and context for translators to provide additional context.

Provide context for translators

New free pricing tier

With the launch of the plugin, we also updated our website and adjusted our pricing to provide more flexibility for different team sizes. We also added a free tier!

More to come

Launching our Figma plugin is just the start of expanding how we support the entire content design process. With Figma’s live collaboration environment, much of the content design workflow is now moving into Figma. We see this as an exciting opportunity to enhance Figma with awesome writer-specific functionality.

Stay tuned. More cool features to follow shortly. 🥳




Strings is a content design and UX writing tool that helps software teams save time and build better products

Recommended from Medium

Lenfest Local Lab 2018–2022: A look back at our location-based products that centered on the…

Prototype and test new products and services.

UI Case Study: Generation Change Responsive Website

What is an Empathy Map? — by Regunathan User Experience Designer

Coronavirus Outbreak or Imagination Outbreak?

Our favourite projects of 2020

“Night Flash” — a Fashionable Solution to Stay Safe In The Dark

Improving User Experience by Conducting Usability Testing

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jasper Platz

Jasper Platz

More from Medium

My approach to content design and content strategy

6 content design shortcuts to reclaim your time and alleviate burnout

Giving and Receiving Feedback: 5 hacks for UX writers

UX writing? 5 reasons why your company should have one