To be honest, I was actually a little bit shocked when I found out that there is no morph/blend/tween function implemented in AD. I mean it's a fundamental function in all vector programs I encountered over the years: Aldus Freehand (later Adobe Freehand) had it, CorelDraw does, AI of course and even CAD packages offer it these days. What's worse is that people have apparently been telling Serif since 2015 that this function is a must. That's EIGHT YEARS!
I must say that I am sometimes truly baffled about the number of significant shortcomings in the designer application (array function, aligning objects along a curve (w/o the text path workaround), proper implementation of boolean functions (one that's not producing 2 useless shapes and 3 random artefacts when your cutting object is a closed topology), perspective adjustments of shapes/groups etc. are other known deficits that simply leave me speechless). I mean, that's just simple, basic stuff that's still not there!
Correct me if I am wrong but I am under the impression that the software is mostly being built by young programmers with no first-hand knowledge of the established workflows that are in place across the creative industry... if that's the case, then the product managers really need to up their game and start looking into an improved development process like the co-creation approach you find in the development of the Blender rendering/modelling application. (about me: industrial designer & design manager and team lead in the consumer industry for 25+ years).
When V2 came out, one of our designers yelled: "Designer V2 - now with basic functions that almost work!" (I understand the frustration, as management had forced the creative team to make the switch from Adobe to Affinity, promising them a mature product environment and a smooth workflow... yeah, right.)