Overview
TwikBot is a cloud-based platform — all processing, asset management, and configuration logic runs server-side and is accessed entirely through the browser. No local installation is required. A stable internet connection and a modern, WebGL2-capable browser are the foundation for any TwikBot usage, regardless of role.
Recommended browsers: Any modern, up-to-date browser with WebGL2 support — Chrome, Edge, Firefox, and Safari are all fully supported. Always use the latest stable version for the best experience.
Internet connection: A stable broadband connection is required. TwikBot streams 3D assets and communicates with the platform in real time — an unstable or low-bandwidth connection will directly impact loading times and responsiveness.
Hardware acceleration: Must be enabled in the browser for WebGL2 rendering to function correctly. To verify that your browser has WebGL2 enabled and hardware acceleration active, visit webglreport.com. A result showing no major performance caveat confirms both are functioning correctly.
If WebGL2 is not available, check the following:
-
Enable hardware acceleration in your browser settings
-
Update your GPU drivers to the latest version from the manufacturer
-
Try switching to Google Chrome, which has the most reliable WebGL2 support
Required WebGL extensions: TwikBot's 3D renderer depends on specific WebGL extensions beyond basic WebGL2 support. The most critical is OES_texture_float_linear, which is required for material rendering. This extension is available in all modern desktop browsers and up-to-date mobile devices, but may be absent on older or embedded hardware such as digital signage displays, kiosk systems, or ARM-based devices with outdated GPU drivers. To verify that all required extensions are available on your device, visit http://webglreport.com and check that OES_texture_float_linear is listed under Supported Extensions in the WebGL 2 tab.
For Partners & Agencies (Graph Editor)
Partners and agencies working in http://platform.twikit.com — building products in the Graph Editor, managing assets, and configuring logic — require a more capable setup than a typical end user. The Graph Editor involves complex 3D scene management and real-time rendering within the browser.
Recommended Setup
|
Component |
Recommendation |
|---|---|
|
Operating System |
Windows 10/11 (64-bit) or macOS 12 and above |
|
Browser |
Latest stable version of Chrome, Edge, Firefox, or Safari |
|
RAM |
16 GB or more |
|
GPU |
Dedicated graphics card with 4 GB VRAM or more (NVIDIA or AMD recommended) |
|
GPU Drivers |
Up to date — always install the latest drivers from the GPU manufacturer |
|
Hardware Acceleration |
Must be enabled in the browser |
|
Internet Connection |
Stable broadband — 3D asset loading and platform operations are bandwidth-dependent |
Minimum Setup
|
Component |
Minimum |
|---|---|
|
Browser |
Any WebGL2-enabled, 64-bit browser |
|
RAM |
8 GB |
|
GPU |
Integrated graphics with WebGL2 support and up-to-date drivers |
Working with complex products — large polygon counts, many materials, or intricate rule sets — on a minimum-spec setup may result in degraded performance in the Graph Editor. A dedicated GPU is strongly recommended for day-to-day implementation work.
For End Users (Configurator Experience)
End users accessing a TwikBot configurator via a web browser require a WebGL2-capable device and browser. The specific requirements depend on the complexity of the product being configured and the target deployment context agreed during implementation.
Desktop
|
Component |
Recommendation |
|---|---|
|
Browser |
Latest version of Chrome, Edge, Firefox, or Safari |
|
RAM |
8 GB or more |
|
GPU |
Dedicated or integrated GPU with WebGL2 support |
|
Hardware Acceleration |
Must be enabled in the browser |
Mobile
Mobile rendering is supported but is resource-intensive. For mobile deployments, device performance should be validated early in the implementation process against the specific product being configured.
|
Component |
Recommendation |
|---|---|
|
Device |
Mid-to-high-end smartphone or tablet |
|
RAM |
4 GB or more |
|
OS |
Latest version of iOS or Android |
|
Browser |
Chrome (Android) or Safari (iOS) |
Poorly optimised 3D assets are the most common cause of performance issues on mobile devices. Refer to the Assets & Materials page for guidance on optimising assets for mobile rendering.
Augmented Reality (AR)
AR mode requires a device with camera access and AR support. AR availability is queried at runtime via the Web SDK. iOS devices running Safari and Android devices running Chrome provide the broadest AR compatibility.
For Partners & Agencies (Unreal Engine Deployments)
For partners implementing TwikBot's Unreal Engine plugin for high-fidelity rendering deployments, hardware requirements are significantly higher and are determined by the Unreal Engine version in use. Refer to Epic Games' official system requirements for Unreal Engine 5 for detailed specifications.
Virtual Reality (VR)
VR deployments using the Unreal Engine plugin require additional hardware beyond standard desktop requirements:
-
VR headset: A supported PC-tethered HMD (e.g. Meta Quest via Link, Valve Index, HTC Vive). Standalone headsets may be supported depending on the deployment target — confirm with your Twikit implementation contact.
-
GPU: A high-performance dedicated GPU is required. NVIDIA RTX series or equivalent AMD is recommended for stable VR frame rates.
-
USB / connectivity: Ensure sufficient USB bandwidth for tethered headsets. For wireless streaming (e.g. Air Link), a dedicated Wi-Fi 6 access point on the 5 GHz band is strongly recommended.
-
RAM: 32 GB recommended for VR scene complexity typical of TwikBot product configurations.
VR hardware compatibility should be validated early in the project scoping phase. Performance targets (frame rate, resolution) will directly influence asset optimisation requirements.