Hey, author here. Thanks for the feedback! The goal definitely is to focus on the core. I mentioned this in the video, I like to think of this as a (multiplayer) work sandbox. I'm really curious about all the different workflows people have/ could build.
Fully agree (been an early Flutter adopter!). It's always the right too for the right job, declarativness makes a lot of sense for most UIs. UIs are surprisingly more complicated than one might think, there is accessibility/ theming/ keyboard traversal etc., just declaring UI and letting the framework figure out the rest has held up pretty well.
And because of the open source nature you can always drop down in layers, just a few weeks ago I made a very specific engine optimization, all while the application code on-top can stay declarative!
I would assume the acceleration pattern of being in a vehicle is somewhat distinct.
I'd be curious what happens when you are in a vehicle that drives completely steady (no turns/acceleration/deceleration) - would it eventually turn off? I guess you wouldn't get motion sick in that case either way.
I've used it on trains a bit and it does turn off when the train is going straight ahead. You might be going 200km/h, but if the speed isn't changing and you're always going forward you don't really feel any force, and neither does the phone, so the dots don't need to be there any more.
Windows, Linux and even web versions are planned!