williamnewton

My main concern is immediacy. There's 0 setup time, and you can instantly share your work. Especially for (relatively) novice programmers, being able to immediately link to something someone more pro can see is invaluable.

+1 for plunker next, hell yeah. Thanks for sharing.

I deliberately left dabblet out because command + shift + left (the shortcut programmed into my brain for 'select this entire line') closes the editor. Annoying as hell.

yep at the bottom of the post. thanks!

I would use Standin if I used Adobe CC. Nicely done.

This post is talking about prototypes from a usability perspective, not a technical perspective. A prototype by your definition ( a "real" prototype) would use data and be built in about the same way as the final product would be. I'm talking about how to prototype the experience. I see how it's easy for you to misunderstand me - apologies for not being clear.

Exactly — start with intuition then get feedback and fix what you were wrong about. And it's definitely far from finished. Thanks!

Is it not clear that my approach is to 1. map out the idea (wireframing) and then 2. hack together a prototype?

That's accurate, and I think that's all the more reason to jump in and start. The content is all there, but there's more detail needed to make an app like this awesome, including stats and UX polish. I'm advocating for the 'just start' approach.

Looks cool, I signed up. Will be back with results.

Downloaded the free chapter, lots of interesting info in there.If you're an entrepreneur looking to raise cash, check this out.