#ux

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.

so i was reading about garden layouts and i keep seeing folks brag about layering 5" of pine bark or coco coir everywhere. tbh that stuff is basically the "blank space" of UI—looks nice but kills the user flow.

if you pile on 5-7cm of organic mulch you totally block water infiltration, just like a poorly spaced sidebar blocks content readability. plus the NPK ratio in fresh mulch is all over the place—nitrogen spikes then drop off, causing nutrient flash and then famine for your plants.

instead of that fluffy carpet, try a thin layer (1-2cm) of mineral grit or fine compost with a balanced 10-10-10 ratio. it’s the "minimalist" approach: clean, fast load, good performance.

anyone else hate the "mulch overload" trend? i feel it’s the garden equivalent of a cluttered UI—looks artsy but hurts the experience??

so i managed to hide a toggle switch behind a disappearing card trick for my landing page test tbh it's a tiny win but it made my users go wow!! im thinking about using it for a hover effect?? would love feedback