Red Dragon is a mobile-first HUD builder and sensitivity tuning tool for Free Fire players in India. It upgrades the existing Red Dragon product with a complete device HUD builder: device detection, manual exact-model selection, 2- to 5-finger HUD layouts with custom fire button size and joystick/scope/jump positions, a visual HUD preview, save/copy/export of configurations, device-specific recommended sensitivity profiles across six sensitivity channels editable from 0 to 200, a training-mode adjustment guide, and VIP access at Weekly ₹99, Monthly ₹299 and Lifetime ₹1,099.
The product is delivered as a working interface backed by a real database, with user accounts and a secure admin dashboard. All devices, HUD layouts and sensitivity profiles are included in the existing VIP memberships; no extra charge applies to individual phone models. Red Dragon never claims exact model detection when detection is unavailable, never claims configurations were tested on devices unless they actually were, and never modifies Free Fire game files.
The audience is Free Fire players on the full spread of supported hardware — all iPhone models, Samsung Galaxy, Vivo, Oppo, Realme, Redmi, Poco, OnePlus, Motorola, Google Pixel, iPad, Samsung tablets and other Android tablets — who want precise, trustworthy control over their on-screen layout and aim sensitivity, plus the administrators who operate the membership and content behind it.
Red Dragon is a three-service application. A React frontend delivers the public entry, identity surfaces, the device setup, HUD builder, sensitivity workspace, VIP plans and the admin surfaces. A shared FastAPI backend serves all application APIs and domain modules. MariaDB holds application-owned persistent data: accounts, device selections, saved HUD configurations, sensitivity profiles, VIP membership records and admin-managed content.
Two active human personas use the product: the VIP Member (HUD and sensitivity user), who selects an exact phone model, builds and previews 2- to 5-finger HUD layouts, tunes six sensitivity channels, saves/copies/exports configurations and holds a VIP membership; and the Admin, who signs in to a secure dashboard and manages user accounts and VIP membership plans and reviews the device, HUD and sensitivity content the product publishes.
Access is application-owned. Anonymous visitors reach the Landing page and the Sign Up, Login and Admin Login surfaces. Device Setup, HUD Builder, Sensitivity, VIP Plans and Admin Dashboard are protected and require an established identity; the Admin Dashboard is restricted to the Admin role. Identity establishment never happens inside a protected destination.
The product is a planning and configuration tool only. It reads browser-reported screen metrics and user-selected models; it does not read, patch, inject into, or otherwise modify Free Fire game files, and it does not assert that any configuration has been validated on hardware unless a real test record exists.
Removed from scope
Red Dragon is delivered as a first-party web application with its own accounts and database. Everything the VIP Member does — choosing a device, building a HUD, tuning sensitivity, saving, copying, exporting, and viewing VIP plans — happens inside Red Dragon's own interface and is persisted to Red Dragon's own database. Nothing is delegated to a game client, a third-party overlay, or a provider surface.
Device detection is honest by construction. The product reads what the browser can report — screen width, screen height, device pixel ratio and screen orientation — and presents those readings as measured values. It never presents a browser-reported or guessed string as an exact phone model. The exact model is always the one the user selects manually, and the interface labels it as user-selected.
Testing claims are bounded by evidence. A configuration carries a testing status; the product only displays a tested claim when a corresponding test record exists. Otherwise the configuration is shown as untested, and the interface says so plainly.
The VIP boundary is a single membership gate. All devices, all HUD layouts and all sensitivity profiles are included in every VIP tier; there is no per-model purchase, no per-layout purchase and no per-profile purchase anywhere in the product.
Current scope covers the nine accepted destinations and the behaviors described in this document. Nothing in this document is deferred to a future horizon; the requirement thread contains no future-only commitments.
FR-1 — Supported device families. As a VIP Member, I should be able to use Red Dragon on any of the supported device families — all iPhone models, Samsung Galaxy, Vivo, Oppo, Realme, Redmi, Poco, OnePlus, Motorola, Google Pixel, iPad, Samsung tablets and other Android tablets — so that no supported device is excluded. Provenance: explicit. Lifecycle: the member opens the product on any supported device; the interface renders and the device catalog offers the matching family. Observable acceptance: every listed family is present in the device catalog and reachable through model selection. Failure/recovery: an unrecognized family still allows manual model selection from the catalog. Continuation: the member proceeds to Device Setup.
FR-2 — Screen metric detection. As a VIP Member, I should see my detected screen width, screen height, device pixel ratio and screen orientation so that my HUD and sensitivity work is grounded in my actual screen. Provenance: explicit. Lifecycle: the member opens Device Setup; the product reads the four metrics from the browser and displays each as a measured reading. Observable acceptance: all four values are shown and labeled as detected. Failure/recovery: any metric the browser withholds is shown as "unavailable" and never fabricated. Continuation: the member confirms the device.
FR-3 — Manual exact model selection. As a VIP Member, I should manually select my exact phone model so that my configuration is tied to the right device. Provenance: explicit. Lifecycle: the member searches the catalog and selects a model; the selection is labeled as user-selected and persisted to the account. Observable acceptance: the selected model appears on Device Setup and is referenced by saved HUD and sensitivity records. Failure/recovery: if the catalog fails to load, a retry is offered and the rest of the page stays usable. Continuation: the member proceeds to HUD Builder.
FR-4 — No false model-detection claim. As a VIP Member, I should never be told the product detected my exact model when it did not, so that I can trust what the interface reports. Provenance: explicit. Lifecycle: whenever the product displays device information, detected metrics are labeled as detected and the exact model is labeled as user-selected. Observable acceptance: no surface presents a browser-reported or guessed string as an exact model. Failure/recovery: when detection is unavailable, the interface says so. Continuation: the member selects the model manually.
FR-5 — Finger-count HUD layouts. As a VIP Member, I should build 2-finger, 3-finger, 4-finger and 5-finger HUD layouts so that my layout matches how I play. Provenance: explicit. Lifecycle: the member selects a finger count in HUD Builder; the preview stage updates to that layout. Observable acceptance: all four finger counts are selectable and each produces a distinct preview. Failure/recovery: switching finger count preserves the member's other control settings where they still apply. Continuation: the member adjusts controls and saves.
FR-6 — Custom fire button size. As a VIP Member, I should set a custom fire button size so that the fire control fits my grip. Provenance: explicit. Lifecycle: the member adjusts fire button size; the preview reflects the new size immediately. Observable acceptance: the size change is visible in the preview and persisted on save. Failure/recovery: an out-of-range size is rejected at input with the bound shown. Continuation: the member saves the configuration.
FR-7 — Custom joystick position. As a VIP Member, I should set a custom joystick position so that movement control sits where my thumb rests. Provenance: explicit. Lifecycle: the member moves the joystick in the preview; the new position is reflected and persisted on save. Observable acceptance: the joystick position is visible in the preview and stored on the configuration. Failure/recovery: a position outside the preview bounds is clamped to the nearest valid position with the clamp shown. Continuation: the member saves.
FR-8 — Custom scope and jump positions. As a VIP Member, I should set custom scope and jump button positions so that both controls sit within reach. Provenance: explicit. Lifecycle: the member moves the scope and jump controls in the preview; both positions are reflected and persisted on save. Observable acceptance: both positions are visible in the preview and stored on the configuration. Failure/recovery: a position outside the preview bounds is clamped to the nearest valid position with the clamp shown. Continuation: the member saves.
FR-9 — Visual HUD preview. As a VIP Member, I should see a visual HUD preview so that I can judge the layout before saving it. Provenance: explicit. Lifecycle: the preview stage renders the current layout inside a phone bezel frame matching the selected device's aspect ratio and updates on every control change. Observable acceptance: the preview reflects finger count, fire button size and joystick, scope and jump positions. Failure/recovery: if the device aspect ratio is unknown, a default frame is used and labeled as a default. Continuation: the member saves, copies or exports.
FR-10 — Save HUD configurations. As a VIP Member, I should save HUD configurations so that I can return to them later. Provenance: explicit. Lifecycle: the member names and saves the current layout; the configuration is persisted to the account and appears in the saved list. Observable acceptance: the saved configuration reloads with identical values. Failure/recovery: a failed save preserves the in-progress layout and offers retry. Continuation: the member loads, copies or exports the saved configuration.
FR-11 — Copy HUD configurations. As a VIP Member, I should copy a HUD configuration so that I can create a variation without rebuilding from scratch. Provenance: explicit. Lifecycle: the member copies a saved configuration; a new editable configuration is created with the same values and a distinct name. Observable acceptance: the copy appears as a separate saved entry and edits to it do not alter the original. Failure/recovery: a failed copy leaves the original untouched and offers retry. Continuation: the member edits and saves the copy.
FR-12 — Export HUD configuration as image. As a VIP Member, I should export a HUD configuration as an image so that I can keep or share a visual reference. Provenance: explicit. Lifecycle: the member triggers export on a configuration; the product produces a downloadable image of the layout. Observable acceptance: the downloaded image depicts the configuration's finger count, fire button size and control positions. Failure/recovery: a failed export offers retry without losing the layout. Continuation: the member continues editing or returns to the saved list.
FR-13 — Device-specific recommended sensitivity profiles. As a VIP Member, I should see a recommended sensitivity profile for my selected device so that I have a credible starting point. Provenance: explicit. Lifecycle: after device selection, the Sensitivity page shows the recommended profile for that device alongside the member's current values. Observable acceptance: the recommended profile is specific to the selected device model and can be applied as a starting point. Failure/recovery: when no recommended profile exists for the selected device, the panel says so and manual editing remains available. Continuation: the member tunes values and saves.
FR-14 — Six sensitivity channels. As a VIP Member, I should tune General, Red Dot, 2X Scope, 4X Scope, Sniper Scope and Free Look sensitivity so that each aiming context is set independently. Provenance: explicit. Lifecycle: the member edits each of the six channels; each value is independent and persisted on save. Observable acceptance: all six channels are present and independently editable. Failure/recovery: a failed save preserves edited values and offers retry. Continuation: the member saves the profile.
FR-15 — Sensitivity range 0 to 200. As a VIP Member, I should edit each sensitivity value from 0 to 200 so that I can reach both extremes. Provenance: explicit. Lifecycle: each channel accepts integer values from 0 through 200 inclusive; the ruled scale under each channel shows the 0–200 range. Observable acceptance: 0 and 200 are both accepted; values outside the range are rejected at input with the bound shown. Failure/recovery: rejection keeps the last valid value. Continuation: the member saves.
FR-16 — Training-mode adjustment guide. As a VIP Member, I should follow a training-mode adjustment guide so that I know how to refine my sensitivity in practice. Provenance: explicit. Lifecycle: the member opens the guide from Sensitivity and reads the adjustment steps for the six channels. Observable acceptance: the guide is reachable from Sensitivity and covers adjustment of the six channels. Failure/recovery: if the guide fails to load, a retry is offered and the value table stays usable. Continuation: the member returns to the value table and adjusts values.
FR-17 — VIP plans and pricing. As a VIP Member, I should see and select Weekly ₹99, Monthly ₹299 or Lifetime ₹1,099 so that I can hold a membership. Provenance: explicit. Lifecycle: the member opens VIP Plans, compares the three plans and selects one; the membership is recorded on the account with its period. Observable acceptance: the three plans show exactly ₹99 weekly, ₹299 monthly and ₹1,099 lifetime. Failure/recovery: a failed selection preserves the chosen plan and offers retry. Continuation: the member's membership status updates and the member returns to HUD Builder or Sensitivity.
FR-18 — Full inclusion in VIP memberships. As a VIP Member, I should get all devices, HUD layouts and sensitivity profiles within my VIP membership so that I never hit a per-item paywall. Provenance: explicit. Lifecycle: any VIP member reaches every device model, every HUD layout and every sensitivity profile without an additional purchase step. Observable acceptance: no surface offers a per-model, per-layout or per-profile purchase. Failure/recovery: not applicable. Continuation: the member uses any device, layout or profile.
FR-19 — No extra charge per phone model. As a VIP Member, I should never be charged extra for an individual phone model so that switching devices costs nothing. Provenance: explicit. Lifecycle: selecting any device model never introduces a price or a purchase step. Observable acceptance: VIP Plans states the inclusion and no per-model price exists anywhere in the product. Failure/recovery: not applicable. Continuation: the member selects another model freely.
FR-20 — Working interface with a real database. As a VIP Member, I should have my accounts, device selections, HUD configurations, sensitivity profiles and membership persisted in a real database so that my work survives sessions. Provenance: explicit. Lifecycle: every save writes to MariaDB and every load reads from it. Observable acceptance: saved records reload identically after sign-out and sign-in. Failure/recovery: a database write failure surfaces a specific error and offers retry without discarding the member's in-progress work. Continuation: the member retries or continues editing.
FR-21 — User accounts. As a VIP Member, I should create an account and sign in so that my configurations are bound to me. Provenance: explicit (accounts); required_inference (the sign-up and sign-in steps that make it executable). Lifecycle: an anonymous visitor creates an account on Sign Up or signs in on Login; a session is established and protected destinations become reachable. Observable acceptance: after sign-up or sign-in the member reaches Device Setup; after sign-out protected destinations require sign-in again. Failure/recovery: invalid credentials or a duplicate account show a specific message and allow retry. Continuation: the member proceeds to Device Setup.
FR-22 — Secure admin dashboard. As an Admin, I should sign in to a secure dashboard and manage user accounts and VIP memberships so that the product is operated correctly. Provenance: explicit (dashboard); required_inference (the admin sign-in that makes it executable). Lifecycle: the Admin signs in on Admin Login, reaches Admin Dashboard, reviews accounts, memberships, device catalog entries and published content with testing status, and updates account status or membership records. Observable acceptance: updates persist and are reflected on the affected row; a non-admin session cannot reach Admin Dashboard. Failure/recovery: a failed update preserves the attempted change and offers retry; an unauthorized session returns to Admin Login with a clear message. Continuation: the Admin continues reviewing or signs out.
FR-23 — No false device-testing claims. As a VIP Member, I should never be told a configuration was tested on a device unless it actually was, so that I can judge what I am applying. Provenance: explicit. Lifecycle: every HUD configuration and sensitivity profile carries a testing status derived from a real test record; the interface displays "tested" only when such a record exists and otherwise displays "untested". Observable acceptance: no surface shows a tested claim without a corresponding test record. Failure/recovery: if testing status cannot be resolved, the item is shown as untested. Continuation: the member decides whether to apply the configuration.
FR-24 — No modification of Free Fire game files. As a VIP Member, I should be able to use Red Dragon without it modifying Free Fire game files so that my game installation stays untouched. Provenance: explicit. Lifecycle: Red Dragon only reads browser-reported metrics and user input and writes to its own database; it performs no read, patch, injection or write against Free Fire game files. Observable acceptance: the product contains no game-file access path, and the Landing page states the boundary. Failure/recovery: not applicable. Continuation: the member uses the product normally.
Product context. A Free Fire player in India on one of the supported device families — an iPhone, a Samsung Galaxy, a Vivo, Oppo, Realme, Redmi, Poco, OnePlus, Motorola or Google Pixel phone, an iPad, a Samsung tablet or another Android tablet. The member plays on a specific physical device whose screen geometry matters, and wants a layout and sensitivity setup that fits that device and that grip.
Primary goal. Produce a HUD layout and a sensitivity profile that match the member's own phone and hand, keep them, and be able to reproduce or share them.
Distinct accepted responsibilities. Select the exact phone model manually and confirm the detected screen width, height, pixel ratio and orientation. Choose a 2-, 3-, 4- or 5-finger layout. Set the fire button size and the joystick, scope and jump positions. Judge the result in the visual preview. Save, copy and export configurations as images. Tune six sensitivity channels — General, Red Dot, 2X Scope, 4X Scope, Sniper Scope and Free Look — each from 0 to 200, starting from the device-recommended profile. Follow the training-mode adjustment guide. Hold a VIP membership at Weekly ₹99, Monthly ₹299 or Lifetime ₹1,099.
Relevant inputs and decisions. Which exact model to select; which finger count matches the grip; how large the fire button should be; where the joystick, scope and jump controls belong; whether to start from the recommended profile or from current values; how far to push each sensitivity channel; which VIP plan to hold.
Interactions with other accepted participants. The member's saved configurations, sensitivity profiles and membership are visible to the Admin for review and account management. The member never interacts with the Admin directly; the Admin's actions affect account status and membership records that the member then experiences.
Observable success. The member's saved configuration reloads with identical values, the exported image depicts the layout, the six sensitivity values persist within 0–200, the membership status reflects the chosen plan, and every device, layout and profile is reachable without an additional purchase.
What makes this role distinct. The member's work is measurement and tuning on a specific physical device. Every decision is grounded in that device's screen geometry and the member's own hands, and the value of the product is that the result is reproducible and honestly labeled — never that it was validated on hardware the product has not actually tested.
Product context. The operator of Red Dragon. The Admin is responsible for the accounts and memberships behind the product and for the honesty of the content the product publishes.
Primary goal. Keep user accounts and VIP memberships correct, and keep published device, HUD and sensitivity content accurately labeled.
Distinct accepted responsibilities. Sign in on the dedicated Admin Login surface. Review user accounts and their status. Review and update VIP membership records — plan, period and status. Review device model catalog entries. Review published HUD and sensitivity content together with each item's testing status. Confirm that no item is labeled tested without a test record.
Relevant inputs and decisions. Which account status to set; which membership plan or period to correct; whether a catalog entry is accurate; whether a published item's testing status matches its evidence.
Interactions with other accepted participants. The Admin's updates change what VIP Members experience — an account status change or a membership correction is felt by the member on their next visit. The Admin does not build HUD layouts or tune sensitivity on the member's behalf.
Observable success. Updates persist and appear on the affected row, membership records match the three accepted plans, and no published item shows a tested claim without a test record.
What makes this role distinct. The Admin's work is custodial and evidentiary rather than creative. The Admin does not design layouts or choose sensitivity values; the Admin ensures that the records behind those choices are correct and that the product's claims stay within what has actually been verified.
The visual system follows the MARQ by Garmin precision-instrument muse: dark titanium surfaces, dial data, ruled rows and champagne gold marking the brand. The product must never read as a playful game toy or as a generic indigo/blue-on-white SaaS template.
Mode. Dark mode only.
Colour tokens (exact hex, by role).
#14171A#1E2327#EDE8DF#C8A96A#2FD3C0#8C9196Graphite ground covers roughly 80 percent of any surface; champagne gold marks the brand and headings; teal marks live values and actions; muted grey holds labels and rules.
Typography.
clamp(40px, 8vw, 96px) from mobile to desktop.Shape language. Circular gauge rings and ruled data rows. Thin 1px gold hairlines. Sharp corners on panels — no rounded pill buttons. One 2px teal edge on active controls.
Spacing rhythm. Compact controls on an 8-pt grid.
Layout. Edge-to-edge dark hero with a dial cluster. A ruled value table for sensitivity. The HUD preview sits in a phone bezel frame.
Imagery style. Macro material textures in graphite and titanium; topographic line fields behind the hero; a phone frame render as the HUD preview stage.
Readability rule. Headlines, wordmarks, labels, numbers, cards' text and controls stay entirely inside the viewport and their container at 375px, 768px and 1280px, wrapping or scaling to fit, with no other element covering them. Imagery and decoration may bleed, crop or overlap; readable text and controls may not.
The public entry is a full-bleed graphite ground. On the left, a large condensed headline in champagne gold — "Build your HUD like an instrument" — sits over ruled lines, with the subline "Set your fingers, fire size and sensitivity on your own phone. Save it and copy it." beneath it. On the right, a circular gauge cluster shows the visitor's live detected screen width, height, device pixel ratio and orientation as dial readings, with teal marking the active dial. A teal CTA bar reading "Open the builder" sits under the gauge, left-aligned rather than centred. Topographic line fields run behind the hero at low contrast, and a phone frame render anchors the lower edge as the HUD preview stage.
The concept recomposes only accepted content: the detected metrics, the product name, the hero copy, the CTA and the device and VIP summaries. It introduces no new behavior or destination.
Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat
Landing Hero Motion Brief
prefers-reduced-motion, the needles and numerals render directly at their measured values with no sweep and no counting; the layout is unchanged and every reading and control remains fully readable.prefers-reduced-motion, the interface must present a usable static arrangement with all readings and controls fully readable. Provenance: explicit (user design constraints). Rationale: the design constraints require a usable static arrangement under reduced motion.docker-compose.yml with the three services — backend (FastAPI), database (MariaDB) and frontend (React). No additional infrastructure is required for the accepted workflows.
Set your fingers, fire size and sensitivity on your own phone. Save it and copy it.
Open the builderPhones and tablets covered by the builder. The browser reports width, height, pixel ratio and orientation; the exact model is always user-selected from the catalog on Device Setup.
HUD Builder
Pick a finger count, then set the fire, joystick, scope and jump positions to fit your grip. The preview shows the layout before you save, copy or export it.
This is a layout plan you configure in Red Dragon. It is not a screenshot of a game, and Red Dragon does not modify Free Fire game files.
Sensitivity
Tune each channel on its own scale. Every channel is editable, and device-specific recommended profiles start you off.
Editable value range 0 – 200
Editable on its own scale
Editable on its own scale
Editable on its own scale
Editable on its own scale
Editable on its own scale
Editable on its own scale
All devices, HUD layouts and sensitivity profiles are included in every VIP membership — from 2-finger to 5-finger layouts, custom fire button size, joystick, scope and jump positions, through to the six sensitivity channels and their device-specific recommended profiles.
No extra chargeThere is no per-phone-model purchase. Selecting your exact model costs nothing beyond your membership.
hud-builder-sensitivity does not modify Free Fire game files. It reads your browser-reported screen readings and the exact model you select; nothing on your device is edited.
No comments yet. Be the first!