简体中文
English
Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Kinesis Software?
Kinesis Software is a small research-and-development studio, founded in 2002, that builds high-performance user-interface components for financial and data-heavy applications. Its work centres on a Flex datagrid designed for performance-critical banking systems, capable of showing thousands of deeply nested data changes per second while staying responsive — the kind of load you get in trading blotters or live portfolio views. Alongside it sits a Hierarchical List: a structure that flattens dynamic hierarchical models, such as client portfolios or price-band groupings, into a linear list that scales to large numbers of objects.
The company's history includes KineticFusion, an early Flash development and production tool with an incremental ActionScript 2.0 compiler and decompiler, which was sold commercially for about two years before its rights were bought by QDC Technologies. The site also points to ongoing consultancy in the financial industry, notably work connected with Barracuda FX.
Who it suits
- Development teams maintaining Flex 3.x or 4.x applications who need a datagrid that holds up under rapid, nested updates.
- Financial software groups dealing with blotters, portfolios or grouped pricing data, where a flat table view is too limiting.
- Anyone researching hierarchical-to-linear data structures for large object counts.
A practical next step
If you are evaluating it, start with the two component pages — KineticGrid and Hierarchical List — and compare them against your own data shape: how deep the nesting goes, how often values change per second, and whether you need a flat grid or a collapsible tree-like view. The key trade-off is specialisation: this is focused, finance-oriented component work rather than a broad framework, so it fits best when your problem matches its niche. For wider context on the Flex ecosystem, Apache Software Foundation documents the platform's later stewardship.
How does the KineticGrid Flex Datagrid handle thousands of nested data changes per second?
KineticGrid is presented as a visualization component built for performance-critical banking work, and the site's own claim is that it handles thousands of deeply-nested data changes each second while staying responsive. That is a design goal rather than a published technical breakdown, so treat the "how" as a set of architectural decisions implied by the problem it targets rather than a documented algorithm.
What the page actually establishes
- The grid was developed for the performance-critical banking sector, which points to financial blotters and similar continuously updating views as the primary use case.
- It is described as handling deeply-nested data changes at high frequency, not just flat row updates.
- The companion Hierarchical List maps dynamic hierarchical models (client portfolios, price band groupings) into a linear, flattened list that scales to large object counts.
- The datagrid targets Flex 3.x and 4.x, so any evaluation should start with whether that runtime is still part of your stack.
The mechanism, read practically
Three things usually separate a grid that survives thousands of nested updates per second from one that stutters:
- Flattening the model. Deep hierarchies are expensive to traverse per render. The Hierarchical List converts a nested model into a linear list, so the grid iterates a flat structure instead of walking a tree on every change.
- Index-based access. A flattened list with fast indexing means a changed node can be located and marked without scanning the whole model.
- Decoupling updates from rendering. Responsiveness under continuous change depends on batching or coalescing changes so the view repaints on a frame cadence rather than once per data event.
The page supports the first two directly through the Hierarchical List description. The third is general advice for high-frequency grids, not a feature the site spells out.
Who this fits
| Situation | Fit |
|---|---|
| Flex 3.x/4.x financial blotter with nested portfolios | Direct match |
| Modern web stack (React, Angular, Vue) | Wrong runtime; the concept transfers, the component does not |
| Moderate update rates with flat data | Overkill; a standard grid suffices |
| Need for current vendor support and licensing terms | Verify first; the site is an R&D consultancy page, not a product storefront |
Next step
If you are assessing this for a live project, the decisive question is not throughput but runtime: confirm whether you are maintaining a Flex application. If you are, ask Alex Bradley directly about update-coalescing behaviour and how the grid behaves when nested changes arrive faster than the frame rate. For a modern equivalent, compare data-grid options from AG Grid or Sencha against the same flattening-and-batching criteria.
When should I use a Hierarchical List instead of a standard hierarchical model?
Use a Hierarchical List when you need to render or scroll a deep, frequently changing tree in a flat UI control — and a standard hierarchical model when the tree structure itself drives the logic rather than the display.
Kinesis Software describes its Hierarchical List as a structure that maps dynamic hierarchical models (client portfolios, price-band groupings) into a linear, flattened list that scales to large numbers of objects. That framing points to the real trade-off: a hierarchical model is good at representing parent-child relationships, while a flattened list is good at presenting them efficiently.
Where each fits
| Situation | Better choice | Why |
|---|---|---|
| Rendering thousands of nodes in a grid or list with fast scrolling | Hierarchical List | Flattening avoids per-node traversal during paint and scroll |
| Deeply nested data updating many times per second | Hierarchical List | Linear indexing keeps updates cheap as depth grows |
| Business logic that depends on ancestry, inheritance or subtree aggregation | Standard hierarchical model | Parent-child links are the point; flattening loses easy upward traversal |
| Small trees, infrequent changes, simple expand/collapse | Standard hierarchical model | Simplicity outweighs any performance gain |
| Sorting, filtering or virtualising a single visible column | Hierarchical List | One linear sequence is easier to index and window |
How to decide in practice
Ask whether the tree is primarily a data structure or a view. If users mostly see an indented, expandable list and the app needs to keep it smooth under heavy updates, the flattened approach is usually worth the extra mapping code. If code constantly walks up to parents, computes subtree totals, or moves nodes between branches, keep the hierarchical model as the source of truth and flatten only at the rendering boundary.
A common middle ground: hold the canonical tree in a hierarchical model, then maintain a derived Hierarchical List for display, rebuilt incrementally on change. That gives you correct semantics plus fast painting, at the cost of keeping two representations in sync — the main thing to test.
For related background, the developer behind this work, Alex Bradley, also produced KineticFusion, a Flash development tool later sold to another company, and the site notes consultancy in the financial industry.
Next step: prototype both with your worst-case data — maximum depth, highest update rate — and measure scroll frame time and update latency rather than guessing from node counts.
What consulting services does Kinesis Software offer for financial industry projects?
Kinesis Software is a specialised R&D consultancy rather than a generalist agency. Its stated focus is research, development and consulting, with the financial industry as its main consulting arena. The page describes work carried out for the performance-critical banking sector, often alongside Barracuda FX, so the practical shape of the offering is custom component development for trading and data-heavy applications rather than strategy decks or process consulting.
What the work actually covers
- High-performance data visualisation. The KineticGrid datagrid is described as a Flex component built for demanding financial settings, handling thousands of deeply nested data changes per second while staying responsive. That points to blotter-style screens, live order and price displays, and other views where stale or sluggish UI is unacceptable.
- Hierarchical data structures. The Hierarchical List maps dynamic hierarchical models — client portfolios and price band groupings are the examples given — into a linear, flattened list that scales to large numbers of objects. This suits tree-like data that must remain fast and navigable.
- Financial-sector consultancy. Alongside product work, the company takes on consulting engagements in the financial industry, typically with trading technology teams.
- Earlier tooling background. The company was founded in 2002; its first product, KineticFusion, was a Flash development and production tool with an incremental ActionScript 2.0 compiler and decompiler, sold commercially for two years before the rights were bought by QDC Technologies.
Who this fits
A trading platform team with a Flex 3.x or 4.x front end, or a legacy desktop-style UI, that needs a grid or hierarchical list to keep up with streaming updates is the clearest match. The value is in deep component-level engineering for latency-sensitive screens, not in broad IT or management consulting. Teams on modern web stacks should treat the Flex-specific material as evidence of the underlying specialism — high-volume, nested, real-time data rendering — rather than as a drop-in fit.
Next step
Before making contact, write a one-page brief covering your data volumes, update frequency, nesting depth and target platform, then ask directly whether the engagement would be a custom build, an adaptation of KineticGrid or the Hierarchical List, or advisory work. If your stack is not Flex-based, ask early what comparable work has been done outside it — that answer will tell you quickly whether the fit is real. The site's own "Recent Work" and "Prior Work" sections are the fastest way to judge relevance before a conversation.
For wider context on the trading technology vendors the company has worked alongside, see Barracuda FX.
How does the KineticGrid datagrid compare to other Flex datagrid components for financial blotters?
KineticGrid is presented as a high-performance Flex datagrid built for the performance-critical banking sector, specifically capable of handling thousands of deeply-nested data changes per second while staying responsive. That focus makes it most relevant to financial blotters, where rows update constantly and the grid must keep up without freezing the UI.
Where it differs from typical Flex grids
- Update throughput: The page claims thousands of deeply-nested changes per second, a level that standard Flex DataGrid and AdvancedDataGrid implementations often struggle to sustain in blotter-style workloads.
- Hierarchical data: Kinesis also describes a Hierarchical List that flattens dynamic hierarchical models (client portfolios, price band groupings) into a linear list that scales to large object counts. That is a different problem from a flat grid and matters if your blotter groups by client, portfolio or instrument hierarchy.
- Lineage: KineticGrid is a custom component for Flex 3.x and 4.x, developed by a small R&D consultancy, not a broad commercial grid suite with a large support organisation.
Practical comparison
| Concern | KineticGrid (as described) | Typical Flex grid options |
|---|---|---|
| High-frequency updates | Explicit design goal for banking blotters | Often requires custom item renderers and throttling |
| Deeply nested changes | Handled at scale per the product description | Usually a pain point |
| Hierarchical models | Separate Hierarchical List structure | Usually handled via grouping or advanced grid |
| Ecosystem and support | Small vendor, niche product | Larger communities, more documentation |
Choosing between them
If your blotter updates in bursts and users complain about lag, a component designed around update throughput is worth evaluating. If you need broad third-party support, extensive documentation and a large hiring pool, a mainstream grid may be safer despite lower raw performance. For general Flex component research, Apache Flex and Adobe remain useful reference points, though both have moved on from the Flex era this product targets.
A reasonable next step: benchmark your own blotter's update rate and nesting depth, then test whether a stock grid with optimised renderers meets it before adopting a specialised component.
What was KineticFusion and why was it sold to QDC Technologies?
KineticFusion was Kinesis Software's first product: a Flash development and production tool that bundled an incremental ActionScript 2.0 compiler and decompiler. According to the company's own account, it was sold commercially for two years before all rights were purchased by QDC Technologies.
The reason for the sale is not stated on the site, so treat any specific motive as inference rather than documented fact. What the timeline does suggest is a deliberate exit from tooling: Kinesis Software describes itself as a specialised R&D company founded in 2002, and after KineticFusion it moved toward contract research and development, notably performance-critical work for the banking sector such as a high-performance Flex datagrid and an index-based list for hierarchical data models. Selling the rights to a finished, commercially proven tool is a common way for a small R&D shop to convert a product into capital and free its time for consultancy and new components.
What this means in practice
- For a developer evaluating Flash-era tooling: KineticFusion's relevance is historical. Its incremental ActionScript 2.0 compiler targeted a language and runtime that are long obsolete, so it is not a candidate for new work.
- For someone studying small software businesses: the pattern is instructive — build a niche tool, sell it for two years, then sell the rights rather than sustain it indefinitely.
- For teams needing the kind of component Kinesis later built: the datagrid and hierarchical list address different problems (rendering thousands of nested updates per second, and flattening dynamic hierarchical models into a linear list) and are the more likely starting point.
If you want to understand the product's technical lineage, look at the compiler and decompiler pairing, since incremental compilation was the differentiator rather than the Flash authoring shell around it. For current alternatives in that space, Adobe's own tooling history is documented at Adobe, and general background on the language is available at Ecma International.
Haarlem, North Holland, The Netherlands
User reviews (0)