Choosing a graph data visualization technology is a big commitment. You need to be certain that the technology partner you work with is not just a good fit in terms of features, but is also the right choice for a long-term partnership.
In a previous blog we compared open source code libraries with commercial visualization software development kits (SDK) to show you why an SDK like KeyLines should be the obvious choice.
This time, we look at three high-level questions you should consider when choosing a graph visualization partner to make sure they’re up to scratch. Let’s take a look.
Having a developer-friendly API makes a huge difference to the success of your project. We’ve helped many developers who’ve turned to us after spending months unsuccessfully hacking with other less user-friendly options. With KeyLines, they made more progress in a few hours than they previously did in a month.
Don’t forget to consider the documentation – is it clear, easy to search and easy to understand? Over the years, we’ve discovered that text-based documentation alone isn’t enough. So, we also provide demos to make developing your application much easier.
We’ve worked hard to make KeyLines easy to use – with excellent documentation and a faster developer experience.
Another important aspect to bear in mind is quality. Has it been tested in production by many other organizations? Are issues fixed quickly?
Based on our experience of helping hundreds of organizations – from pioneering startups to Fortune 500 companies and national governments – we’ve developed a robust understanding of what our customers require.
Our team of experienced developers are continually finding ways to improve KeyLines with new features and we release updated versions monthly. This ensures that KeyLines works with the latest technologies and helps our customers improve their products.
You also need to evaluate the functional capabilities of your potential partner’s technology. Your precise needs will depend on your scenario: your users, data, use case, etc. That said, certain points come up repeatedly, such as:
Other considerations include whether or not the technology allows for the exporting of the chart to an image file or a JSON file and if the visualization is optimized to take advantage of graphics processing units (GPUs) for instance, by using WebGL. WebGL rendering means KeyLines is a lot more powerful and performs better than other technologies.
You can use the list above to decide which capabilities are important to you. From there you can get closer to deciding whether or not you should work with a potential partner to build your graph visualization application.
Choosing the right graph visualization partner isn’t a tick-box exercise. The questions in this blog post reflect some of the criteria you should consider and benchmark, but the best way to choose is by trying the technology for yourself. We’ve put together a short guide of the factors you should consider when evaluating graph visualization partners. If you’d like a copy, just get in touch.
Keep an eye out for part two of this blog where we’ll look at three more high-level questions you should consider when choosing a graph visualization partner.
If you’d like to see KeyLines in action and how it can help you build a powerful app, request a free trial below.