I'm one of the resident Wayland critics, and one of my most painful Wayland experiences was in a similar embedded/Yocto setting. A kiosk-style device where I ha

I'm one of the resident Wayland critics, and one of my most painful Wayland experiences was in a similar embedded/Yocto setting. A kiosk-style device where I had a perfectly working system for X. Sometimes there'd be one program drawing to the screen, sometimes two or three, and they very easily arranged themselves on the screen in the right position/size. Then I had to port this stuff to a different hardware platform that only supported Wayland. The programs could no longer place themselves where they wanted to, and a simple helper/manager script I had based on xdotool of course also no longer worked. As an extra bonus, on the X variant I'd use x11vnc for maintenance purposes to find out exactly what was being shown, which also broke down on Wayland. Took weeks to get things ported, leaving a few rough edges that were worse than on X, and not a single thing that was better for the system developer's or the end users from Wayland. I'm sure some of that has improved since. One of my first attempts there was to use ivi-shell, but occasionally I needed to show a browser on the screen and at that time Chromium had too many random crashes under Weston.