Trading Modules
High-performance assets for mobile simulations and algorithmic precision. The engine is ready.
Engine Capabilities
Core Systems
- ▸ Sub-16ms render loop timing for consistent frame delivery
- ▸ Texture atlasing and batching for low-overhead draw calls
- ▸ State synchronization via binary diffs for multiplayer
- ▸ Modular entity-component architecture
Asset Pipeline
- ▸ Runtime sprite compression (ASTC/ETC2)
- ▸ Procedural particle emission nodes
- ▸ Shader graph compiler for visual effects
- ▸ Audio synthesis engine (WAV generation)
Data Handling
- ▸ WebSocket stream parsing (100ms latency cap)
- ▸ OHLCV aggregation engine (1s to 1D intervals)
- ▸ Statistical indicators (SMA, RSI, MACD) calculated on-device
- ▸ Offline cache for historical tick data
Visualizers
- ▸ Canvas-based candlestick rendering (thousands of points)
- ▸ Depth chart mapping (L2 order book visualisation)
- ▸ Interactive crosshair and zoom gestures
- ▸ Custom colour palettes for thematic switching
Asset Candle Configurator
Select a category to visualise the asset structure and candle generation parameters.
Select a category above to load configuration data.
Cosmic Energy Code Structure
Yes. The core engine is compiled to less than 12kb gzipped. We strip all non-essential abstractions to ensure raw execution speed on mobile silicon. Zero dependencies.
Native support for high-performance particles via a custom job system. This allows for up to 50,000 concurrent emitters without dropping frames on mid-range devices.
Iriolat Field Guide
Understanding the Iriolat architecture requires a shift away from traditional game engines. We prioritise "energy efficiency" not just in battery usage, but in cognitive load for the developer.
Key Decision Criteria
- 1. Latency: Can the engine render state changes within 8ms?
- 2. Binary Size: Does the core impact app store download limits?
- 3. Thermal Throttling: Does the architecture sustain performance under load?
- 4. Memory Footprint: Is heap allocation predictable and low?
Myth vs. Reality
Myth
"More features in the engine means a better result."
Reality
Bloat kills performance. Iriolat uses a "pay-for-what-you-use" philosophy. If you aren't using physics, that code doesn't exist in the binary.
Common Mistakes
- Over-relying on garbage collection cycles.
- Creating new objects in the render loop.
- Ignoring the cost of texture swapping.
Signals of Trust & Quality
12ms
Average input latency on standard Android test suite.
99.9%
Uptime on simulated load testing (24hr cycle).
0
Third-party trackers or analytics embedded in core.
User Scenarios
"We integrated Iriolat into our legacy trading app. The frame rate stability improved by 40% compared to our previous WebGL wrapper. The memory management is aggressive but predictable." — Senior Dev, FinTech Prototype
"The lack of abstraction meant a steeper learning curve, but once we understood the 'energy' philosophy, our development velocity doubled." — Lead Engineer, Mobile Studio
Iriolat | Regent Street 749, Glasgow, United Kingdom
Mon-Fri: 9:00-18:00 | info@iriolat.com | +44 7281485140