Yes, this is reminiscent of ReelCraft. I liked ReelCraft as it saved me a lot of time in the initial stages of a project (never did simply output and use as-is). Since ReelCraft went the way of the wind, when I saw Mootion, I was optimistic. There are some pros and cons to Mootion, which I'll outline, but the TL;DR version is: easy to use, quality output, lousy prompt adherence, animation costs a lot, worth checking out, especially if your use-case doesn't need strict adherent output.

Pros: It's easy to use in general. Editing scenes' text/VO and regenerating images is easy-peasy. The biggest pro is the quality output.

Cons: The biggest con is prompt adherence. It's fine to have to regenerate an image, it isn't fine to have to regenerate an image 8 times because it keeps outputting the same character instead of adhering to the prompt (eg. re-output an overweight man with graying hair when the prompt says a thin 25 year-old man). Other "cons" include the number of credits it takes to animate. Understand, I don't expect this necessarily to be cheap. Especially because businesses need to be able to stay in business and if it costs the company, then it will naturally cost the customer. However, when it costs more than double what it would to animate an image directly (eg on Kling)...and that animation is actually a simple pan shot over the image rather than actual movement of people, that's too high a credit cost. Now, if the animation was always "movie-like", then the higher cost could be justified.

A note here: on one project, the animation cost was reasonable; on another project the animation cost was more than double of what it would have cost to turn each individual image into a video using Kling. Not sure why.

Suggestions for improvement:
1. have options for animation that cost different credit amounts. Want a simple slide-show pan/zoom, not too many credits for that. Want movie-like action, costs more.
2. prompt adherence needs to be infinitely better. (even though I listed this second, it's the most critical issue, IMO)
3. have better input options before the initial storyboard is created so that we can use it as-is right now, suggest specfic scene prompts, tell it whether to use our input as a guide (eg. don't change my VO script or use it as a guide to create a better script)
4. Better selection of voices and music would be nice, but that's not a critical issue.