NOTWENNODE
Notwen ui product scene
IN DEVELOPMENTnot_ui
NOTWEN / UI

Notwen UI

A shared visual layer for menus, panels and dialogs so separate resources still feel like one product family.

FRAMEWORK BRIDGESESXQBCoreQboxCustom
STATUSIn development
RUNTIMEFiveM / CFX
MODELNotwen native
DOCSIncluded
CURRENT STATEIn development

The resource page is public for architecture and integration context. Purchase will open when the product is ready.

Open documentation
PRODUCT SCOPE

What this resource owns.

Reusable components, tokens, panels and interaction states for consistent interfaces.

INCLUDES

Core capabilities

  • Shared components
  • Design tokens
  • Layout primitives
  • Modal/panel patterns
  • Theme configuration
  • Resource ready UI helpers
USE CASES

Where it fits

  • Menus
  • Panels
  • Dialogs
  • Shared server interfaces
INTEGRATION MODEL

Own the domain. Bridge the server.

Framework-specific access stays at the integration edge so product behavior can remain consistent across server stacks.

FRAMEWORK BRIDGE

ESX · QBCore · Qbox · Custom

Framework-independent UI layer above ESX, QBCore, Qbox, custom cores or standalone resources.

RUNTIME APPROACH

Predictable responsibilities

Reusable components reduce duplicated frontend code and help keep rendering behavior consistent.

BEST FIT

Where it makes sense

Servers that want different scripts to share one coherent interface language.

TECHNICAL CONTEXT

Read the contract before deployment.

Purchase and delivery will be enabled when the resource is ready. Documentation covers dependencies, installation, configuration, APIs and troubleshooting.

Open documentationSupport
PRODUCT DETAILS

Notwen UI

Reusable UI system and shared visual language for building consistent Notwen-style interfaces.

WHAT IT INCLUDES

Core capabilities

  • Shared components
  • Design tokens
  • Layout primitives
  • Modal/panel patterns
  • Theme configuration
  • Resource ready UI helpers
WHERE IT FITS

Typical use cases

  • Menus
  • Panels
  • Dialogs
  • Shared server interfaces
FRAMEWORK MODEL

Own the domain, bridge the server.

Framework-independent UI layer. Can sit above ESX, QBCore, Qbox, custom cores or standalone resources.

PERFORMANCE APPROACH

Predictable runtime behavior.

Reusable components reduce duplicated frontend code and help keep rendering behavior consistent.

BEST FOR

Where this resource makes sense.

Servers that want different scripts to feel like one product instead of a collection of unrelated UIs.

NEED THE TECHNICAL SIDE?Read dependencies, installation, configuration and APIs before deploying.
Open Documentation Support