Is user interest enough for the OP, or are you looking for other contributors?
I am specifically looking for someone with JS skills to handle building animation in between screens (similar to push.js in Ratchet http://maker.github.io/ratchet/#push ). This in turn is inspired by jquery-pjax ( https://github.com/defunkt/jquery-pjax )
Explained in short - there should be some way to fetch the HTML for a "new page" replacing the older page without a page refresh. This way we can have nice CSS transitions between the pages. If we can plug the effects from something like Effeckt (http://h5bp.github.io/Effeckt.css/dist/) in there this could lead to nice demo/prototype material and will also give the native coders a good idea about the animation.
The demo UI works with Angular.js.
what you have looks great so far.
additionally I was getting my web app to host mockup images, sketches or just notes so I could think about the app flow and still be able to click around. I was doing it with express so I could parse markdown files (for the raw notes).
I would say keep using angular as its very fast to add new pages. sliding page transitions and grabbable affordances would be the most useful things I think.
The value of such of tool though points to one of the reasons why web technologies will ultimately prevail over native for most applications -- ease of use.
There are apps popping up that are really an ember or angular one pager wrapped in a native shell.
HTML/CSS on Webkit gives you an amazing layout engine for free. Building UI for native apps feels like "web coding like it's 1999" with a lot of absolute positioning and use of sprited images. I wonder if things improved in iOS7.
All your users care about is UX and features. Native sdks provide more features than web apis, are more powerfull and your users feel the difference. Native sdks are not going away anytime soon.
So PhoneGap applications are technically "hybrid apps." The WebView portion of the app is native code - but that really is just a technical nuance with no implications for performance (in fact, the performance implications are negative), because it's like claiming that your website is "native" since it runs in a browser (say, Safari) and the browser is written in native code. But the non-native portion of the app is what goes inside the WebView (HTML/CSS/JS).