Systems | Development | Analytics | API | Testing

Our New user interface has kept us busy for a while now, which explains why we haven’t made an update post like this one in a while. You’ve probably noticed that the UI has changed a lot since the first version released last year. It’s obvious when you put them side by side. The beta version: And the latest: A lot of it had to do with updating to Angular 15 but this was also the perfect occasion to offer an even better user experience.

Have you ever been in a meeting and wondered how something is calculated? Or what another department’s acronym means? Or how that topic is actually defined? In some moments, you don’t need the data itself — you just need the definition of a data term. In that situation, you want the ability to look up a term in a business glossary (or data glossary) as quickly and simply as possible.

When Plastic SCM (now Unity Version Control) was acquired by Unity in 2020, game dev and VFX studios already using the Unity Engine started considering it more seriously for version control. Why? On the surface, Plastic SCM is an attractive solution. It offers a friendly UI for artists and handles the basics of version control at low scale. But what happens when your projects grow and get more complex? Does Plastic still hold up? Read along or jump ahead to the section that interests you most.

The past few years—accelerated by the pandemic—have seen people move more of their work and personal lives online. There’s a huge growth in teams working remotely, either on a full or part-time basis. And many companies have embraced the remote-first model - offering remote-first or hybrid positions as standard. However this shift to remote, online-first interaction brings challenges. For remote workers, one of the biggest impacts has been in the way that they work together.

With software such as Google Docs and Figma now part of the everyday productivity toolkit for millions of people, multiplayer collaboration features have become mainstream. Thanks, in part, to the boom in distributed teams and remote working, new software is increasingly built from the ground up with realtime collaborative features – and other vendors are looking at how to retrofit multiplayer collaboration to existing products.

Test management is essential to software development, ensuring applications meet quality standards. Effective test management requires a systemic approach to creating, executing, and tracking test cases. The hard part is usually incorporating test management into your existing development workflows. Many Agile organizations use Jira to manage projects, track issues, and communicate between teams.

We see a lot of teams working with automated testing, and many feel the need to take the next step in order to optimize and excel in their product release cycle. Prior to implementing DevOps, companies can experience a stall in releases and only make new ones every 6 months. This means that development efforts are not bringing value to users quickly enough. For companies that work in regulated industries, it’s also critical that they set up reporting and traceability into their DevOps pipeline.