We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Find solutions, get advice, help others.
Hey dev community, I'm running into a tough architectural challenge with an Android app I’m developing, and I’d really appreciate some high-level feedback. The app, tentatively titled **Electric Sheep1.0**, aims to deliver dynamic live wallpapers featuring procedurally generated fractals combined with lightweight interactive elements. The main engine the **Electric Sheep 1.0 fractal render loop** is supposed to continuously generate evolving fractal visuals, inspired by distributed rendering concepts like the original Electric Sheep project. On paper, the **Electric Sheep 1.0 fractal render loop** should be solid. But in practice, scaling beyond a certain complexity leads to major performance issues high memory usage and crashes, especially on mid-range Android devices. It seems the fractal generation and syncing operations overwhelm the client-side environment. My question is more about architecture than a specific bug: Is client-side distributed fractal rendering at this complexity e
Hey dev community, I'm hitting a serious architectural wall with an Android app I'm working on, and I would really appreciate some high-level insights. The goal is to create an interactive live wallpaper app that blends procedural visuals with lightweight gaming elements. The core feature, which I’ve tentatively named the **Electric Sheep 1.0 fractal render loop**, is designed to generate and display evolving fractal animations in real time. It uses a distributed computing approach where users' devices contribute to rendering the fractals (inspired by the original Electric Sheep project). Theoretically, this **Electric Sheep 1.0 fractal render loop** logic should work efficiently. However, once I scale beyond a certain number of visual nodes or complexity, the app starts consuming too much memory and eventually crashes on mid-range devices. It appears that the dynamic generation and syncing of fractal patterns exceed what’s manageable client-side. My question is more architectural than
Hello, I created a figma account years ago at a hackaton, and joined an impromptu team. Fast forward 3 years and I created a new figma design. Unbeknownst to me, I was still part of this team. Two days ago, I removed myself from the team so I could start a new team and share the file with someone else. However, when I went to share the file and move it, it said I didn’t own the file that I created and that I couldn’t move it from another user’s drafts. How do I resolve this? I opened a support ticket, but they haven’t been much help.
Hi guys I am trying to group the component and click on variants I am unable to see variants in the rightside tab, on design section can anyone help me out
Experiencing lag and delays in the MAKE chat on the Figma site when expanding conversations is a common frustration, especially as the text volume increases. The issue seems to worsen over time, specifically when typing into the input field, where the system momentarily freezes before displaying the typed text. Has anyone encountered a similar problem or found a solution to address this performance issue?
I want to make a prototype where something changes when user scrolls content. I want to keyboard collapse when user starts scrolling content, but it’s impossible to do with drag action. Or it feels unnatural Or am I missing a way to do it with existing tools?
Hello, Are there more information about the rate limits? Can I read my current rate limit usage from the header during a e.g. curl request? this seems not to work for file api or versions api like chatGPT suggests response: HTTP/2 200 content-type: application/json; charset=utf-8 date: Thu, 19 Jun 2025 16:52:54 GMT x-content-type-options: nosniff x-figma-rest-api-request-id: <requestID> access-control-allow-origin: * access-control-allow-headers: Content-Type, X-Figma-Token, Authorization cache-control: no-cache, no-store vary: X-Figma-Token,Authorization,Accept-Encoding x-cache: Miss from cloudfront via: 1.1 da5c11b2a013db4b3aea71948d5cedb2.cloudfront.net (CloudFront) x-amz-cf-pop: TXL50-P2 alt-svc: h3=":443"; ma=86400 x-amz-cf-id: <some-hash> strict-transport-security: max-age=31536000; includeSubDomains; preload server-timing: cdn-upstream-layer;desc="EDGE",cdn-upstream-dns;dur=0,cdn-upstream-connect;dur=142,cdn-upstream-fbl;dur=1064,cdn-cache-miss,cdn-pop;desc="TXL50-P2",cdn-rid;de
I'm encountering an issue with the Variables API endpoint when attempting to export local variables. The endpoint returns all remote variables from shared files, making it impossible to export only local variables. Current Behavior: The endpoint returns all remote variables from shared files Unable to filter or export only local variables Receiving a 400 error with "Request too large" message Error Response: { "status": 400, "error": true, "message": "Request too large. If applicable, filter by query params." } Technical Details: The error message suggests using query parameters for filtering However, the endpoint documentation doesn't list any available query parameters The endpoint lacks pagination capabilities This limitation makes the endpoint essentially unusable for files with many variables Expected Behavior: Ability to export only local variables Support for filtering variables (local vs. remote) Pagination support for large variable sets Impact: This issue significantly impact
Hi guys,Any idea how I can wrap in Auto Layout? There used to be an option, but it beats me how it works after they changed the UI3 again. I am literally baffled, it used to be simple and straight forward. edit: found it, it only shows up when applicable. Which is pretty counter intuitive imo, that’s why Active/Inactive states exist :)
Just published my site using Figma Make. Using the provided URL, the browser shows a blank screen. How can I fix this?
Hello everyone, I’ve run into an issue in Figma prototypes: whenever a component has a Background Blur effect, Smart Animate stops working correctly. I’m looking for any known workarounds or explanations. Scenario A Frame/Component includes: A semi-transparent fill (e.g. white at 20% opacity) Background Blur effect (Radius: 20px) I use Smart Animate to transition this component between different states (variants, interactive component states, or separate frames). Observed Behavior Without blur (same component with only an opaque fill and no blur), all Smart Animate transitions run smoothly. With blur applied, Smart Animate transitions: Jump instantly without interpolation, Or fail to animate entirely. Questions Are there any known Figma limitations or bugs when using Smart Animate on layers with Background Blur? How can I achieve smooth Smart Animate transitions on blurred components without relying on masks or overlays? Could there be a prototype setting or component hierarchy detail
In the right panel of Figma Design, when opening the Variables dropdown menu or applying variables for any numeric input (Corner radius, Gap, Padding...). Next to each token, there is a new thumbnail representing a number value “1234”. It’s disturbing the reading of my variables. How can I go switch to the previous dropdown design ? Thank you
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
