Não consigo abrir meu protótipo no celular

Hey ​@Pedro Felipe, thanks for reaching out! At the moment, we don’t have official support in Portuguese, so I’ll continue in English. Please let me know if anything is unclear and I’ll be happy to clarify.

You'll see a message that the frame you are trying to open is too large or that your prototype can't be opened on mobile when loading this screen of your prototype, including connections and variant sets used in interactive components, uses more available memory than is available on your phone. You can read about how to Reduce memory usage in files and most of the suggestions there also apply to prototype loading on mobile.

Figma is a browser-based app, which means it's subjected to a 2GB available memory limit that applies to each browser tab, including those in our mobile app, or mobile browser. When loading or editing Figma files nears or exceeds this memory limit, it can cause performance issues like long load times or crashes, especially in a mobile browser, which generally has an even smaller available memory (the specifics depend on the phone model and OS version).
 
The engineers are keen to check out any example files where users are unexpectedly seeing this error without any significant or recent file changes so they can investigate the possibility of a recent change to loading behavior.
 
If you're happy for them to take a look at your file, can you  reach out to our support team via this support hub, share a file and add support-share@figma.com as an Editor to this file and any related libraries (this won't affect your billing at all). 

If you'd prefer to troubleshoot your file without sharing it with the team, to find what's using the memory, we suggest creating a separate prototype of just the frame that's crashing and testing the following to see if they help stabilize loading:
 

1. Checking the impact of interactive components with variants Because the presentation view currently loads all variants in a set, not just those used in a specific transition, using large variants sets for interactive components uses a lot of available memory. We'd suggest creating a set with only the states needed for a specific transition or disabling interactive components as needed.
2. Removing hidden layers: Loading and then hiding many layers, especially in components or with images stored in them, can cause a high use of available memory on loading.
3. Removing stacked masks and effects like shadows and blurs also take a lot of memory to load.
4. Downsizing large images: You can check the size you've added an image to a File at by temporarily toggling the Image Fill settings to 'Tile 100%'. If the preview you see is much larger than the Frame it's filling, we'd suggest toggling this setting back, and then exporting the Frame and replacing the Fill with that export. You can also optimise image size in bulk using a plugin.

If you find that any of these help ‌stabilize loading, you can then decide if it's best to remove them from your main file or to set up a streamlined version of the file for mobile viewing.

Hope this helps and let me know if you have any further questions! 

Thank you very much for the support, Gayani_S!
I am currently trying to get in touch with Figma Support so they can review my file and analyze the issue. I am awaiting their response.

In the meantime, I am applying all the recommended measures mentioned above, and I have already noticed that replacing the Smart Animate option with Dissolve has improved the transition speed. However, there are still other screens that I am unable to open. I believe this may be related to hidden shapes that make up the background. Could you advise on how I might optimize this?

Additionally, I would like to ask whether Figma’s newer visual effects, such as Liquid Glass, also require a significant amount of processing power.

Note: English is not my native language. Please feel free to let me know if anything I wrote needs clarification.

Thank you for the update and no worries at all, your English is very clear! 

I’ve checked your support ticket (#1673730) and shared your follow-up questions with our Technical Quality team, so they have full context while reviewing the file. I can also see that they’ve now responded to you. Please let me know if their reply helps clarify things, or if anything is still unclear.

As for Liquid Glass and other newer visual effects, yes, those are heavy effects. Minimising its use is likely to improve performance.

Let me know if there is anything else I can help out with!