Engineering

How Productboard monitors frontend applications

And that is correct! Network glitches, deployment glitches, dependencies upgrades, developer’s carelessness or just small data inconsistencies. There’s plenty of stuff in web development that can go wrong, and it will go wrong at some point. What’s far more important than trying to prevent anything from going south is having solid monitoring in place and clear processes to follow.

Productboard

Matej Minarik

⚔️ Spinners versus skeletons in the battle of hasting

This article describes how to identify intermediate states while loading using React Suspense.
Every modern app needs to load data from a server. This may take a while, and making our users wait on a blank screen just won’t do.
Now comes the choice — loading spinner or loading skeleton.

Productboard

Martin Nuc

How we measure adoption of a design system at Productboard

Building a design system without knowing how it is used can be very tricky, and even the simplest of questions can be hard to answer. Do you know how often your components are used? Can you remove deprecated components from the code? What is the adoption of your design system?

Productboard

Filip Danisko

What life’s really like as a designer at Productboard

It was in the spring of 2018 when I first interviewed for the position of a product designer at a local startup — you guessed it, Productboard.

Productboard

Zdenek Kuncar

Design at Productboard – how we work

In part one, I provided an introduction to our design ethos and team set-up here at Productboard. For part two, I’ll discuss how we work, focussing on the important matters of collaboration and feedback.   

Productboard

Zdenek Kuncar

Design at Productboard – an introduction to the design team

As we continue to grow at a rapid pace, we’re always on the lookout for talented new designers to join our team. We interview a lot of people in the process. And those people ask a lot of great questions. In this series of articles, I’ll answer some of the most frequently asked questions we get asked.

Productboard

Zdenek Kuncar

Design at Productboard – what candidates and new hires can expect

In this series of articles, I answer some of the most common questions we get asked by design candidates during the interview process. The aim is to provide as much clarity as possible, giving future candidates all the information they need to approach their Productboard journey with confidence.

Productboard

Zdenek Kuncar

Countering microservice disasters

At Productboard, we’re adopting a service-oriented architecture for two reasons — to enable faster decision-making in empowered teams and allow us to staff quicker by adding two more stacks into the mix we develop in.

Productboard

Vojtech Vondra

Scaling monorepo — to infinity and beyond!

One interesting thing I have observed over time is that open-source solutions tend to struggle with bigger code bases. That’s when custom tooling comes into play — or not necessarily. The truth lies somewhere in the middle.

Productboard

Jakub Benes

How to connect “Can I use” with your Google Analytics to show real browser support

Web Can I use is an indispensable part of every web developer today. Can I use provides up-to-date browser support tables for support of front-end web technologies on desktop and mobile web browsers.

Productboard

Jan Vaclavik

How we wrote our Design team’s charter, together

ur Design team grew three-fold last year, from four to twelve, including our first dedicated UX Researcher. This year, the plan is to expand the team further across the EU and the US. 📈

Productboard

Jan Srutek

How we revamped our RFC process at Productboard

A year and a half ago, I took the opportunity to build the Frontend Platform team that I’m still leading today. While I did this for many reasons, one of them was particularly striking: To empower product teams to make high-impact changes, enable and support innovation, and share our learning across the frontend community.

Productboard

Jakub Benes