Suggestion - include some sample screens built to your best practices and a couple storyboards using those screens.
Better samples, better screencasts - all this is on my list. But like for any coder it takes some great effort for me to spend my time on website/marketing. But I'll get there I promise.
In case you did not see Dan Grover's response about the work breakdown on his Etude sheet music iPhone app:
"Were you the only one developing it? How long did it take? Love the app and the video on the webpage, by the way."
"Luckily, I have a precise answer to this because I have this weird habit of tracking every minute of my time on my own projects. Here's the breakdown on Etude in hh:mm
Actual iPhone app: 210:11
Song converter: 72:52
Store (UI + server side): 82:23
Building site and designing marketing materials: 44:52
I did most of the work, but I did contract some of the graphics I had trouble with to a designer, and I've taken someone awesome on board to work with music companies and other "strategic" stuff for the future."
I realize that Eclipse is not for everyone. But a plugin for IntelliJ or some other IDE is a completely different product. FWIW there is a "standlone" version of WireframeSketcher that you can get through Yoxos: http://wireframesketcher.com/install_details.html#yoxos
I'll see what I can do about the immediate edit box. Obviously an option for it could be a solution. I'll see if there are more requests for it.
Take a look at master screens. I think it might be what you are looking for. You can reference screens from other screens and create reusable units this way. Changes to referenced screens are propagated automatically.
I plan to add editing inside groups. I think your idea of logical grouping is good. It was actually this issue that was stopping me from adding the possibility to put in Outline the complete contents of a group. Logical hierarchy would give much more appropriate results.