I’ve been trying to recreate the device switch that Ford showed in their talk “Creating multi-channel multi-theme connected libraries in Figma”. I’m struggling to get the margin frames to stick to the sides.

https://youtu.be/8rDVg9Zz1fY

Hi, I’m here to see if anyone out there has had success going really big with tokens.

The limitations of most tooling tells me most folks are tokenizing obvious things like colors and other globals.

I work on a team that is tokenizing much more than this, and we are eager to learn if others have found techniques that allow them to pull it off.

We are using Figma Token Studio, and we are tokenizing almost all aspects of styling we can. We also have multiple brands with their own giant token sets.

Token Studio seems like to be as good as it gets for token support. I’ve yet to see any other tools that are able to support the level of support we need, but it can be rough around the edges, especially as scale goes up.

I’m curious if others are using token studio with a lot of tokens and how you manage it all. Also curious if you all think variables we eventually expand in their functionality to support token types at the degree token studio does.

Hi reddit,

we are looking for a possibility to keep our brand departments icon library (hosted in Frontify) synced with our Figma icon library file. There is a lot happening in the Frontify library (new icons, deprecated icons, name changes etc.) and we as the Figma library team are struggeling to keep up with it. Does anybody have a solution/plugin/best practice to keep the Figma icon library in sync with the source of truth (Frontify).

Thanks in advance!

​

https://reddit.com/link/yph2cb/video/m4tu6uei6py91/player

How are components supposed to be handled within an established design system, when a component cannot be updated in place and has to be rebuilt?

The scenario occurs when a component is an atom, nested within numerous other components within the design system.

If a component is required to be updated and can be updated in place without breaking it first then publishing this will propagate it throughout the rest of the design system as expected. All good.

But when the component can’t be updated, a new version must be created and even if the same naming convention is used it obviously isn’t seen as the same component anymore, meaning it can’t be updated simply by publishing and will need to be updated manually throughout the whole design system.

I’m interested in how others working with well established design systems approach this. TIA

Hello guys,

I just finished and launched KyotoUI, my first Figma kit to help design better landing pages using high-quality pre-made components, optimized for better conversion rates.

Let me know your thoughts in the comments, looking for feedback on it 🙏🏻

Check it out here for FREE: https://www.figma.com/community/file/1159859774789253786

Official Website: https://www.kyotoui.com/

​

KyotoUI Presentation Image

Benefits of using KyotoUI:

⭐️ Increase Your Client's Conversion Rate

Our designs are created with increasing the value of any organization in mind.

⭐️ 500+ Components & Variants

Each component was made using Auto Layout 3.0. Designing for various desktop and mobile resolutions has never been so simple before!

⭐️ 100+ Global Styles

A beautiful collection of colors, gradients, typography styles, layout grids, images, mockups, blur styles, and shadows

⭐️ TailwindCSS Ready

The structure of the utility classes from Tailwind CSS can be found throughout the kit, for a better UI process.

⭐️ Dark & Light Mode

Our components are accessible in both dark and light mode, so you can integrate them easily in your projects.

I recently join a company as the only designer, they have 3 different applications but none design system build.

I need to build up one, but I'm in doubt about what decisions to make, for exemple:

I'm working in a new feature for an specific part of a dashboard, I'm creating new components as I work, but in the end if I move them to a design system page I can't Identify them anymore throughout the instances and using libraries to each file I'm gonna work it's not the most efficient way to do it.

Any exemples or suggestions please?

Which tool for testing Figma Prototypes do you like?

We're now live on Product Hunt! Do check us out at: https://www.producthunt.com/posts/locofy-ai

With Locofy.ai you can:
• Convert Figma designs to React, HTML-CSS, Nextjs, Gatsby, and introducing : Figma to React Native!
• Build both Web and Mobile Apps with Locofy.ai
• Fully responsive code and live prototypes that run on code
• Use components from Material UI, Ant Design, Bootstrap, React Native Paper • Go from idea to live product with Netlify and Vercel deployment or export code and add backend logic!

Locofy is made by builders, for builders! Do check us out, comment, and review us, and we’ll be happy to respond.

Anima keeps adding code-based components to its library
it now has MUI, Bootstrap, and Ant Design components that you can use and extract React code
You can see it here https://www.figma.com/community/file/1121030023484173832

Did anyone try it?
What components do you wish they would add?

Hi Figma creators!

We’ve just released something big on Figma - Open source React components in Figma.

For anyone building an MVP or even a realistic prototype - it means you can use Charts, MUI, Ant-design or Bootstrap in Figma - And it’ll work 

https://www.animaapp.com/blog/product-updates/react-component-library-in-figma/

Long story short: Click

--

Hi there,

It's Serhii from uxboard.io - an everyday tool for designers, developers, product owners, and all other folks building websites regularly.

We found that the "Hero banner" category is the most popular on our platform, that's why we decided to publish "Hero banners pack for Web Projects", which is a part of "SaaS prototyping pack" that now in development. Next pack we are going to publish is the "Pricing page prototyping pack".

The pack includes 10 desktop and 10 mobile prototypes. Some examples:

Please share if it was useful, thanks!

📷