HTML5 v Quark AVE Interactivity

Hi Everyone

Maybe I've missed it, but is there a summary anywhere outlining the differences between using HTML5 and Quark AVE Interactivity in terms of the options available? More specifically, something like:

- If you want to achieve this, then you have to use Quark AVE Interactivity...
- If you want your app to .... then HTML5 is best.
- If you want to do this, then Quark AVE is best, but you can achieve a similar outcome in HTML5 by ...

Basically what I'm wanting is a summary that users can refer to prior to designing an app to help them determine which way to go? A checklist perhaps so they can make an informed decision prior to starting out.

Example 1
I've just started working on a one-off standalone app and assume the only way to go to achieve this (at present at least) is to go with the Quark AVE option. Is this correct?

Example 2
If I want the flexibility to design my own menu and/or navigation elements in order to dictate what the user can do, and would prefer to have no default Navigation Bar, is this possible? And, if so, how? (Is this only possible in the AVE-Doc format, or is it also possible in HTML5?)

Anyway, I think you get the idea.

Thanks.

Joe.