It's been a while since I wrote Maplets. However, I always used components just like the ones you call Embedded Components for which one can write code which is carried out when the user does various actions, in other words object programming. Perhaps Möbius Apps lack this object programming behavior (and flexibility) since they don't mention this aspect anywhere in their documentation. This limitation to having a separate Maple Player to run the App seems a problem.
Since the Möbius Apps you referred be to all seemed to require Java, that hardly seems different than Maplets. But then again, the Möbius Apps just use Maple, and Maple itself runs on a Java virtual machine.
I myself certainly do not want some "helper" program writing my Maplet or other App. I need to write it in Maple and know and control what it does. Having such a helper program is the kind of thing I always have to spend some time shutting down in other programs because it tries to "out think" me, which means it usually does exactly what I don't want.
Well, I would like to see what these Möbius Apps do. The ones on the websites you directed me to do not run. That is, they often put up a screen of information, but the EC's, like the sliders, don't work. There is no information on how to download the mw files or what is required to run the apps. However, from what I see, there is no improvement over Maplets, but instead some movement in the other direction.