The Connected Animation functionality seems to be processed in two steps and this breaks the fluent feeling:
This behaviour happens at least on Windows 10 build 17730. It can be reproduced with the Community Toolkit Sample App. Please see the gif below (source at https://i.imgur.com/cdcn9ix.gif):

I would expect the animated element to move directly to its destination instead of having this snapping behaviour.
```
Nuget Package(s):
Windows 10 Build Number:
App min and target version:
Device form factor:
Visual Studio
In my own app, the snapping is even worse (more visible):
I tested it. I can reproduce this bug on an Insider build too (17723). But it works fine on the latest Windows release (April Update). So, I suppose it is not related to the toolkit or maybe there was a change in the Connected Animations API.
Thank you for confirming it!
How can we best take it further from here? I know it is possible to report developer platform bugs in the Feedback Hub but I fear that it won鈥檛 be picked up there..
Hey @stmoy, wonder if you are aware of this issue? I saw this on @nmetulev 's machine the other day too.
Thank you for reporting! This is a known platform regression and has been fixed in the very latest version of Windows.
Awesome! Thanks @stmoy, good to know it's already fixed. I am closing the issue now.
Most helpful comment
Thank you for reporting! This is a known platform regression and has been fixed in the very latest version of Windows.