It’s the master compositor, laying all windows out to generate the image to be displayed. It also handles input and other event routing, as it knows where each app’s windows are, and which are at the front.
Catalyst
How to recognise Catalyst and iPadOS apps from RunningBoard’s job descriptions, and how iPadOS apps are launched differently. And why RunningBoard can take a high CPU %.
I was having problems in the Twitter app, with it stealing 100% CPU and upsetting WindowServer. Here’s how I discovered what the problem was.
One second, the app was fine. Then it just vanished. There was nothing wrong with that app: it was murdered. Join this game of Cluedo/Clue in macOS.
From LaunchServices and an initial security check by MIS, to FuseBoard and FrontBoard handling the app’s scenes, all you need to know about how an M1 Mac runs iOS apps.
The M1’s honeymoon is over. Speed is great, but users are asking what else the M1 offers. Catalyst and the M1 iPad Pro could prove crucial to the answers.
iOS and iPadOS apps run on M1 Macs in an environment managed by RunningBoard, FrontBoard, FuseBoard, and several assistants.
Does that app use Electron, Catalyst, SwiftUI, AppKit, or is it an iPhone app? How to find out easily.
Recommended for all users, as it also fixes a bug displaying the busy spinner, and improves detailed and text output.
From launch, through security checks, TCC and privacy, RunningBoard, to memory management and the Main Event Loop. A comprehensive summary.
The Eclectic Light Company 