Skip to main content
Question

Ghost aura apk v2 panel ff Proposal for specific Android overlay export settings

  • November 27, 2025
  • 3 replies
  • 520 views
ibrahimprakasa11

Reference Preview: https://ghost-aura-apk-panel-ff.s3.ap-south-1.amazonaws.com/index.html

Feature Request Overview

I am currently designing a mobile interface overlay (specifically the V2 panel) and I am struggling with the asset generation for the final build. The link above demonstrates the current prototype behavior versus how Figma handles the export. I would like to suggest a feature that allows better handling of "Ghost" style semi-transparent layers when slicing for Android XML.

Project Specifications

  • Name: Ghost Aura UI Project
  • Version: V2 Panel Integration
  • Type: Mobile Overlay / FF Framework

Panel Features & Design Requirements

To ensure this interface works correctly in the final application, the following design elements need to be preserved during the export process:

  • Floating Window Capability: The design relies on a floating icon structure that needs precise coordinate mapping.
  • Aimbot-style Focus Assist (UI Concept): The central crosshair alignment tools in the panel need to maintain vector scalability.
  • ESP Line Rendering: The fine lines used for the visual sensory paths (ESP) often get blurred when exporting to standard PNGs.
  • High Frame Rate Optimization: The assets need to be lightweight to support high refresh rates without lag.

Current Issues with V2

When updating from V1 to the Ghost aura apk v2 panel ff layout, the "Head" and "Body" selection toggles in the design do not maintain their layer states. The "Antenna" visual component also loses its alpha channel transparency.

Suggestion

Could the Figma team add a specific "Android Overlay" preset in the export tab? This would allow designers to define specific regions (like the control panel) that should be exported with 9-patch scaling automatically applied, ensuring the "Ghost" effect remains consistent across different device resolutions.

    3 replies

    Della Garry
    • Della Garry
    • New Participant
    • June 2, 2026

    This is a really detailed breakdown of the issues with V2 panel exports, especially around transparency handling and layer consistency. The “Ghost” style overlay requirement definitely needs more control over alpha channels and 9-patch scaling to work properly across different screen densities.

    When working on long UI/UX or asset-heavy projects like this, it’s also important to take regular breaks since rendering and testing iterations can get quite time-consuming. Some developers I know usually step away for quick refreshment breaks and sometimes even check simple food/menu inspiration sites like daveshotchicknmenu just to quickly decide what to eat without spending too much time away from work.

    A dedicated “Android Overlay” export preset sounds like a solid improvement idea it would save a lot of manual adjustment work for designers working with floating UI systems like this.

    jennymartin806
     

    Thanks for sharing the detailed overview and suggestion.

    I understand the issue you’re facing with the V2 panel export, especially around maintaining semi-transparent “ghost” layers, alpha channels, and consistent scaling when moving from Figma to Android XML assets.

    Your idea of an “Android Overlay” export preset with built-in support for 9-patch scaling, layer-state preservation, and better handling of transparency (especially for floating UI elements and vector-based overlays) is very well thought out. It would definitely help bridge the gap between design intent and implementation for complex mobile UI systems like the one you’re building.

    I’ll make sure this feedback is noted for consideration by the relevant product/design tooling team.

      Della Garry
      • Della Garry
      • New Participant
      • June 10, 2026

      This is a well-thought-out suggestion, especially regarding the preservation of transparency effects and scalable assets during the Android export process. Designers working on complex mobile overlays often face issues with alpha channels, blurred line rendering, and inconsistent scaling across different screen sizes. Having an export preset with built-in 9-patch support and better handling of semi-transparent elements would definitely streamline the workflow and reduce the need for manual adjustments after export.

      Improving asset optimization while maintaining visual consistency is becoming increasingly important as mobile interfaces grow more sophisticated. Small enhancements to the export process can save developers and designers a significant amount of time during implementation and testing.

      On a completely different note, when everyday devices run into problems, users often look for reliable local solutions such as ipad screen repair near me to get their tablets back in working condition quickly. For more helpful tips and resources, check out ipad screen repair near me.

      Terms & ConditionsAccessibility statement