#Figma

Figma 1.38’s Prototyping API keeps reinventing the wheel when it comes to micro‑interactions. Do I get what I’m seeing? Yeah.

The new Interactive Canvas just wraps CSS3 transforms in a shiny UI. Instead of improving developer velocity, it hands us a drag‑and‑drop slider that doubles bundler size. I’ve got three devs per project doing a three‑hour nightly dive into hotspot fail‑states while the changelog reads "Dynamic Scaling v2: automatically adjusts for pixel density."

• 30% of our devs now spend a single day polishing hotspot anchors in a fake Shadow‑DOM.
• Auto‑Animate v2.0 still caps out at 48 kb per component. It’s great for a demo slide, not for production.
• "Dynamic Scaling" in the component inspector is still a typo – it only scales groups.

Bottom line: no more static mock‑ups, people. The pattern stays the same: extra abstraction + longer build times. I’m calling off the prototype migration and reverting to static layers in QML. Any one who wants to join the sanity purge?

Installed UX Audit on my MacBook Pro (macOS 13.2). Plugin says it’s only for Windows. Error 0x80070005 pops up. I read the manifest: it references the ‘Design System’ API, which I thought was only in Figma 42.0. That seems off??

• Manifest lists "platforms": ["windows"]
• Error code: 0x80070005
• Figma version: 42.0
• macOS: 13.2

Anyone else hit this? Maybe the compatibility flag is wrong or the API version is misdeclared??

Also, does anyone know if the plugin supports the new macOS Big Sur security model? ...

I just finished redesigning my portfolio site using Sketch 71.1 and I'm blown away by the improvements in the layout tool The new auto-layout features are a game changer. I was able to cut my design time in half. Has anyone else made the switch from Figma 104 to Sketch? I'm curious to know if I'm missing out on anything.

I've been wrestling with Figma's Auto Layout for the past week, and the new iOS 17 UI kit is literally sabotaging my prototypes. Every time I nest a component inside another Auto Layout frame, the constraints snap back to 0px padding and the whole hierarchy shifts like it's on a rollercoaster.

What really grinds my gears is that the official release notes barely mention this, yet the community keeps preaching "just use constraints wisely" as if it's a magic fix. Meanwhile, my handoff specs for the dev team are a mess because the spacing values keep mutating on export.

Here's a quick rundown of the pain points:

• Nested Auto Layout frames lose their custom padding (e.g., 12 px → 0 px) after a single refresh.
• The new iOS 17 UI kit components (UIButton, UIStackView) ignore the "Spacing Between Items" setting in Figma, forcing me to manually adjust each instance.
• When I inspect the generated CSS, the gap property is missing, replaced by a hard‑coded margin that breaks responsive breakpoints.
• The "Inspect" panel now shows a phantom "margin‑auto" on every nested element, which doesn't exist in the actual code.

I keep hearing the same old advice: "Make sure you set the parent frame to "Hug contents" and lock the padding." It works on Android Material, but iOS 17 seems to have its own secret sauce. Anyone else hit this wall? Or is it just my Figma file being cursed? I need a solid workaround, not another vague "try updating your plugin".

TL;DR: Auto Layout + iOS 17 UI kit = broken nesting, missing gaps, and endless handoff headaches. Drop your fixes, workarounds, or at least confirm I'm not the only one losing sleep over this.

I need to get this off my chest… I spent an entire weekend polishing a fan‑app onboarding flow for a new BTS "Permission to Dance" campaign, only to discover the micro‑interaction I built in Figma (Component ID: btn‑lightstick‑v2) completely misbehaves on the Galaxy S23 Edge panel.\n\nWhat happened?\n- I used a gradient token "#FFB6C1 → #FF69B4" to mimic the pastel pink lightstick glow, but I referenced the token from the iOS design system instead of the Android one. The Android token expects a linear‑gradient syntax, so the edge panel renders a solid block of color.\n- My hover state was defined with a CSS variable --hover-scale: 1.08; – a convention I borrowed from a recent SM Entertainment UI kit. Unfortunately, the S23's Edge panel doesn't support CSS variables in its overlay layer, causing the button to freeze at its default size.\n- I also hard‑coded the component's z-index: 9999 to keep it above the background video of the "Dynamite" teaser. On the Edge panel, that pushes the element out of the visible viewport entirely.\n\nI feel like a rookie designer who tried to blend K‑Pop fandom aesthetics with a cross‑platform UI without respecting the platform‑specific token sets. The result is a UI that looks like a misplaced lightstick at a concert – bright, but completely out of sync with the stage.\n\nAny advice on how to properly separate iOS and Android design tokens in Figma, or a quick fix for the Edge panel's lack of CSS variable support? I’m ready to refactor the component hierarchy and maybe even ditch the gradient for a static color on Android. 🙏??\n\nThank you for any guidance – I promise to keep the next iteration less… chaotic.