Explore the story of Joonas Püüa, Lead Engineer at Riverty in Tallinn, and how he builds and scales secure payment systems processing millions of real-time and batch transactions. 

Learn how ownership, collaboration, and AI-supported engineering drive innovation and reliability in FinTech.

Read his full story

Carina spent the past decade crafting a career defined by transformation, trust, and the freedom to grow. Her journey reflects what’s possible when opportunity meets initiative, and when leadership is built on clarity, trust, and the willingness to step into the unknown.

Read Carina’s story and explore how she balances life and leadership with purpose.

Building charts once and shipping them everywhere sounds simple - until you're maintaining separate rendering logic for web, iOS, Android, macOS, and Windows, and your "unified" solution turns out to be a web-view wrapper in a native shell.

The core problems for dev teams: duplicated charting code across platforms, web-view wrappers that choke on custom interactions and synchronized multi-chart views, and libraries that fall over once you throw dense, streaming datasets at them (think financial tick data or industrial sensor feeds).

The comparison is blunt about the popular options. 

• Plotly leans hard on JavaScript, which shows up as real mobile performance bottlenecks. 
• Highcharts is mature and accessible but web-centric at its core, so native mobile still means shipping a browser component under the hood. 
• ECharts handles big datasets well and is fully open-source, but has no dedicated commercial support and the same browser-rooted architecture as Highcharts.

SciChart takes a different route. At the core is Visual Xccelerator™, a proprietary C++ engine that renders natively against DirectX, Metal, OpenGL ES, or WebGL depending on the platform — no web-view in the loop, no browser component smuggled into your native app. That architecture is what makes handling up to 1 billion data points possible, backed by dedicated native SDKs for Android, iOS, macOS, WPF, and JavaScript instead of one implementation wrapped six different ways. Licensing is developer-based too, not per-seat or usage-based, so your bill doesn't spike the moment your user count does.

For teams evaluating a charting stack, the practical takeaway is to test against your actual constraints - streaming data volume, true native rendering vs. embedded browser, and how licensing costs behave as you grow - rather than picking on ecosystem popularity alone.

Curious how that stacks up against Plotly, Highcharts, and ECharts for enterprise-grade apps? Full breakdown here:

Source: SciChart Blog — Best Cross-Platform Charting Libraries for Enterprise Apps

Hier erzählen unsere IT-Expert*innen über ihren Arbeitsalltag bei uns. 
Zum Beispiel Softwarearchitekt Jürgen.

Wie arbeitet es sich so als Softwarearchitekt bei der ING? Was ist das überhaupt, Softwarearchitektur? Und was hat es mit diesem Orange Code auf sich? Hört mal rein!