Snapchat/Valdi
Valdi
Valdi is a cross-platform native UI framework that compiles declarative TypeScript code into native platform views. It functions as a declarative UI engine and multi-platform frontend toolchain designed to achieve high performance by avoiding web views.
The framework features a native bridge binding tool that generates type-safe bindings between TypeScript and native languages, allowing direct access to platform APIs. It supports a hot-reload development workflow, enabling real-time updates to the user interface across platforms without requiring full project recompilation.
The system includes a flexbox-based layout engine for responsive design and a rendering pipeline that optimizes performance through view recycling and multi-threaded logic execution in worker threads. Additional capabilities cover component state management, application screen navigation, interface localization, and a visual hierarchy inspector for debugging layout structures.
Features
- Cross-Platform Native Renderers - Compiles declarative TypeScript code into high-performance native platform views across multiple operating systems.
- Cross-Platform Rendering - Renders native user interfaces from a single TypeScript codebase across multiple platforms.
- Type-Safe Binding Generators - Generates type-safe bindings between TypeScript and native languages for compile-time safety.
- Native API Bridges - Bridges TypeScript code to native platform methods and hardware capabilities.
- Native UI Bindings - Connects custom native view factories and attribute bindings to implement specialized platform functionality.
- Logic Thread Isolation - Offloads complex JavaScript processing to worker threads to prevent blocking the main user interface thread.
- Native Bindings - Generates type-safe bindings between TypeScript and native languages for direct platform API access.
- Automatic Element Alignment - Automatically calculates component positions and sizes using a flexible box model for consistent alignment.
- Declarative Layout Engines - Manages component state and layout through a declarative rendering engine.
- Flexbox Layout Engines - Uses a flexbox-based layout engine to ensure consistent and responsive element alignment across screens.
- Declarative Native Renderers - Compiles declarative TypeScript UI definitions directly into native operating system views.
- Native Compilation Frameworks - Compiles TypeScript and JSX user interfaces into native application code for high performance.
- Cross-Platform Toolchains - Provides a comprehensive toolkit for building and debugging native interfaces across diverse platforms.
- Hot Code Reloading - Provides a development workflow that updates the interface in real time without recompiling.
- Hot-Reloading Systems - Implements a runtime reloading mechanism that updates the UI without requiring a full application restart.
- Native View Embedding - Inserts custom platform components into declarative layouts or hosts native view hierarchies within the app.
- UI-Responsive Background Workers - Executes long-running logic in background worker threads to keep the interface fluid.
- Component State Managers - Tracks internal component data changes to trigger automatic visual updates of the user interface.
- Screen Transitions - Controls the transition and stack of different view hierarchies to manage multi-screen user flows.
- Responsive Design - Implements flexible layouts and animations that adapt to different screen sizes and orientations.
- State-Driven View Refreshing - Automatically refreshes the native view hierarchy by tracking changes in internal component state.
- View Hierarchy Inspectors - Provides a visual inspector to analyze and debug the rendered view tree and layout structures.
- View Recycling Systems - Optimizes memory and performance by recycling UI components that have scrolled off the screen.
- Generic View Recycling - Optimizes rendering performance and reduces latency by recycling view components that scroll off screen.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
