RegularScallop372

I’ve been working on a new mobile app and decided to keep the same color palette for every screen to maintain brand consistency. I’m wondering if that’s a common practice or if people usually switch palettes for different sections. Some designers say it keeps the UI cohesive, while others argue it can feel monotonous. What’s the general consensus? Do you see this approach in most apps or do you prefer distinct palettes for different flows? I’d love to hear your thoughts and any examples you’ve seen.

I’m building a small mobile app by myself and I’m debating whether to set up a full design system from the get-go. I know it can help with consistency and speed up future work, but it also feels like a lot of overhead for a one‑person project. Some of you have probably done this—what’s your take? Do you think it’s overkill, or does it actually save time in the long run? I’d love to hear real experiences, not just textbook advice.

So I've been wrestling with a client who wants their app localized for Persian speakers, and holy cow the default Figma layout engine assumes everything is LTR. Like I get that Arabic/Hebrew are RTL, but Persian? Not technically, but the client expects mirrored navigation menus. And here's the kicker — when you nest components with auto-layout, flipping the direction messes up the spacing logic entirely. Has anyone else dealt with this? I'm seeing weird overflow issues in the prototype where the hamburger menu icon is colliding with the logo when mirrored. Feels like the design tools aren't built for this edge case at all.