Workflow: Mobile Optimization

For mobile projects, Memory and Build Size are critical. Nexus Graph helps you strictly enforce rules that prevent bloat.

Use the Mobile Safe preset in the Rule Engine.

1. Ban “Resources”

The Resources folder is often misused, leading to startup memory bloat.

  • Rule: .*Resources.* -> .* (Forbidden)
  • Why: Assets in Resources are indexed at startup. Use Addressables instead.

2. Prevent Heavy Assets in Prefabs

You can define rules based on asset types or naming conventions (custom implementation required for strict size checks, but architectural separation helps).

  • Ensure “Gameplay” prefabs don’t reference “Cinematic” high-res textures.

3. Usage Heatmap

Use the Heatmap view to find “Hot Assets”.

  • Yellow Nodes: These are referenced by MANY things.
  • Risk: If a “Common UI Button” references a “4K Atlas”, every UI screen will pull that 4K Atlas into memory.
  • Fix: Break the dependency or use sprites slicing/Addressables.
This site uses Just the Docs, a documentation theme for Jekyll.