71–80 of 94 posts
Naming layers has been a problem for decades . There are even memes about it. With the advent of AI, we all knew this is a perfect match where AI can help from day one. Happy to see it arrive to Figma now.
CSS has had a similar issue with naming classes, which is one reason for how TailwindCSS’s design. I wonder if we’ll see more AI tools for these kinds of use cases.
Earlier quoted context omitted.
I saw this in a few of my friends' companies. I have asked to everyone how is storing data in Azure is better than using Azure ChatGPT API, and till now I haven't been able to get a good answer.
The answer is likely in the contract your company has with Microsoft.
Earlier quoted context omitted.
Is that control opt-out by default?
Another commenter mentioned that the default is no training for Enterprise and Organization accounts, but for Starter and Professional accounts the default allows training and you need to explicitly opt out.
They have not yet started doing any training on user content and I applaud them for that. (They've only used public community files so far.) However, they are headed that way to support advanced AI features. Quoting Fimga: Two important highlights: First, all admins have control of whether their team’s content data is used for training. Second, participation in AI content training is not required to use Figma or Figm…
It’s opt out for lower plans and opt in for higher plans
[flagged]
Naming layers has been a problem for decades . There are even memes about it. With the advent of AI, we all knew this is a perfect match where AI can help from day one. Happy to see it arrive to Figma now.
Yeah this one is crazy cool, not even a designer, but my figma prototypes are trash to manager after a while, any approximate name is better than my Layer 1231