We also wanted to thank YOU for supporting us all these years. Some of you have been with us from the start, and that means a lot to us. We will always be grateful for that. All the best to all of you. 💜.

We wanted to take a moment to thank the whole team for the amazing work they've done over the years. We've been lucky to work with talented, passionate, and kind people. We've always tried to do our best, and that's what matters most.

It was also a pleasure to contribute to the market's evolution in any way we could, whether through the @DesignTokens or at all those conferences (@Clarity_conf + @intodsconf). Meeting all these people who work every day to elevate the design systems market is amazing. 🫶.

What will happen to Specify? The product will be sunset on November 15th. We're considering contributing it to the market as open-source if it makes sense. If you're interested in this idea, feel free to send us a message.

We'll keep an eye on market trends and tools, and we wish all the best to those working in this direction. Whether it's @figma, @zeroheight, @supernova_io, @TokensStudio, or @KnapsackCloud (just to name a few), there are already some great players out there.

Of course, this is a big disappointment for the whole team. Even after all these years navigating a constantly changing market, we had strong beliefs. We thought—and still think—that there's still a lot to do to improve the daily interactions between designers and developers.

We have some sad news: we're going to sunset Specify. It breaks our hearts because we put so much energy and passion into helping the design and front-end teams work better together. But eventually, we haven't found our product-market fit.

Last but not least, we also have deployed several improvements. Head toward our changelog to learn more!.

UI improvements. We also spent some time to refresh parts of the UI within your repositories. Previews, buttons, iconography, search and more. Will you spot them all?

SDK 1.0 release. Following early April SDK improvements we decided to release the 1.0 version officially thanks to your valuable feedback! It's a huge milestone for us and we can't wait to show you what we are cooking next.

PDF compatibility for vectors. Mobile engineers we heard you! Specify is now compatible with PDF format for your vectors from Figma to your code base.

Import your font files. Once you have synchronized your text styles in your repository you are now able to upload your font files manually and extract them through available destinations using our parsers technology.

Changelog alert ✨. Following the past releases, we enhanced the way Specify handles assets from Figma to your code base. And as always, a lot of improvements have been shipped along the way:. 📖 Font files import.📂 PDF for vectors.🐙 SDK 1.0.⚙️ UI and performance improvements

Last but not least, we have shipped many other improvements and new features that improve your experience. Head toward our changelog to learn more 👇.

New parsers. Specify is dedicated to provide all the tools needed to generate the output needed by your company standards. We have released a lot of them lately, focused on the generation of text-styles and the usage of fonts.

A brand new documentation. Every good tools come with a useful documentation. Alongside the release of the new version of the SDK, we published a new version of the doc to provide all the information needed to enjoy the full power of it.

A more powerful SDK. We spent the last couple of months improving the SDK by adding more features, flexibility and ease of use. You have full control on the manipulation of your design token graph by generating a custom output that fits your company standards.

Update time ⚡. This update is focused on the developer experience alongside few improvements of the overall experience. On the menu:. 🔮 A new version of the SDK.📖 A brand new documentation.⚙️ A tone of new parsers.✨ And more…

Last but not least, we have deployed several bug fixes and improvements. Head toward our changelog to see the details!.

We also have updated the way we handle aliases across several shared Figma libraries for your variables and styles. Previously we only retrieved the raw values, now we provide the option to have the aliases linked when you synchronize your sources.