PIXIDA

Tech Radar
Meet our passion for technology

The Pixida Tech Radar is a tool to inspire our engineering teams to pick the best possible tools, frameworks and platforms for new projects. It helps us to share knowledge and experience in the company and reflects our way of working - so that you can get to know our understanding of modern development practices even before you join us.

LANGUAGES AND FRAMEWORKS
Adopt
  • Python
  • Node.js
  • React + Redux
  • Room
  • Spring framework
  • Swift
  • TypeScript
  • mbedTLS
  • (embedded) C
  • C++17
  • Java
  • Kotlin
Trial
  • Combine
Assess
  • Dart
  • Material-UI
  • Next.js
  • Rust
Hold
  • Bootstrap
PLATFORMS
Adopt
  • Android
  • iOS
  • Material Design
  • ECU Test
  • Jupyter
  • STM32
  • Nordic NRF52 Platform
  • AWS
  • AWS CDK
Trial
    Assess
    • Kibana
    • Cross Platform Development (Flutter/Cordova)
    • Android Automotive
    • RISC-V
    • Azure
    Hold
      TECHNIQUES
      Adopt
      • Test activities based on ISTQB
      • Agile & Lean Development
      • Continuous
      • Event Driven Architectures
      • Everything as Code
      • Everything as Markup
      • Free Tool Selection
      • Microservices
      • Serverless
      Trial
      • Self-Contained Systems
      • Production-Readiness Guideline
      • Customer Interviews and Analysis
      Assess
      • Design Thinking
      • Life Cycle Management
      • Semantic Monitoring
      • Token Vending Machine
      • UX Prototypes
      Hold
        TOOLS
        Adopt
        • JIRA (incl. plugins for test management,…)
        • GitLab CI
        • CANoe / Vector Tooling
        • QGIS
        • GeoPandas
        • HERE Services
        • Docker
        • Pixida Sea Star
        Trial
        • Figma
        • Storybook
        • MS Project
        • Opsgenie
        Assess
        • Google Analytics
        • Zeroheight
        • Camunda Modeller
        Hold
        • Adobe XD
        How to read the radar?

        The Pixida Tech Radar is a list of technologies, platforms, tools and techniques that we use in the company. Each of the categories is complemented with an assesment and expresses the level of adoption in our teams:

        ADOPT

        Technolgies we think should be the standard choice for our development and our colleagues have a lot of experience with. They are proven to be mature and effective and, depending on the context, should be used whenever possible.

        TRIAL

        Technology in trial is not yet mature enough to be fully adopted, or we are not 100% certain that it is better than existing technology or practices. However, it can still evaluated in a productive setting with a bit of caution. We want to gather more information about them to see if adding them to our standard development toolkit would be beneficial.

        ASSESS

        Technologies that seem promising but we do not yet have a very good understanding of. We either think they have a potential for general adoption or we want to better understand, e.g. to better consult our clients regarding it. Typically, these technologies are assessed in our Competence Areas in dedicated projects.

        HOLD

        Technologies we do not recommend or we do not want to work with (anymore). There can be a lot of reasons for this, including being outdated, not mature enough yet or we simply made a strategic decision against them.