Well, it's easy when you're the only decent [1] cross platform UI library left on the face of the earth that does not instantiate a browser. Also the only option to get a lot of infrastructure pre done for embedded projects.

[1] My friends who still do Qt whine occasionally about quality going down, but it's not like they have other options.

These guys were pretty good when I used them: https://www.cranksoftware.com/storyboard.

Crank doesn't scale. The project is a binary file. You can't have multiple people developing screens. Its fine for small projects, anything big and it falls apart.

I used to look down on Crank like it was the next coming of Flash Lite, but after finishing a project in QML and realizing most of the heavy lifting was connecting the Javascript components to business logic C++ code running underneath through their clunky interface methods... it's pretty much the same thing.

And I bet Crank will actually run on a Cortex-M3.

"Get a quote." Cue Bugs Bunny: "Nooooo."

"Someone" in this case is almost the entire automotive industry, among others.

which could be overtaken by AAOS(android auto) down the road?

For infotainment certainly, maybe not for instrument clusters, especially in base model or commercial vehicles.