Skip to content
All articles
  • Engineering
  • airdesk

Introducing the airdesk engineering blog

A place to document the questions, design choices, and validation work behind remote computing.

airdesk team
1 min read

A remote screen passes through several stages before it appears on another device: capture, encoding, network transport, decoding, and rendering. Keyboard and mouse input travel in the other direction.

This blog is a place to document the questions and decisions along that path.

What we plan to write about

  • Connections and networking: finding a connection path and observing latency and packet loss
  • Displays and media: choices and constraints in capture, encoding, and decoding
  • Platform differences: understanding behavior across operating systems
  • Development and operations: reproducing problems and validating changes

Separating plans from results

We will distinguish a design proposal from an implementation, and an implementation from a result verified on real devices. When sharing performance measurements, we will include their environment and conditions.

We also intend to write about open questions. We hope these notes will be useful to developers working on similar problems.

AIRDESK ENGINEERING

Notes for the next connection.

Keep exploring the engineering behind airdesk.

Explore all articles