My only problem with all this . . .
. . . is the changing navigation for the learner, especially if all this is embedded in an AP preso. You could have an AP preso with it's unique navigation (usually at the bottom), then your main Engage interaction (which may switch navigation to the top left), and then the same with the inserted Engage in an engage interaction.
No wonder learners get bewildered by us some time . . .
. Seems like developers being "cool" at the expense of learner usability.
I'm getting feedback from many of our users that even with a simple Engage interaction in AP that the switching of the navigation focus is something that many people do not like.
That's why during the 09 betas we raised the point of having AP navigation control the navigation of any inserted Engage interactions--this is something Articulate should address (I've submitted my feature request on this). I'm usually of the school you should keep learner navigation simple and in the same spot.