This is our big v2. Cool things you could try: the front page has an onboarding bot that simulates using the product; commenting on designs use Pusher and stream live; and I like to think I made it pretty damn fast.
Appreciate the feedback! (eh eh)
Coding front-end and animations is just searching google for examples + practice. I didn't find a shortcut, sadly! I fiddle with CSS animations until they match what I imagine them to be. Ceasar (http://matthewlein.com/ceaser/) is really good for getting kinetics right.
It's also a huge help when designers better than you give you feedback and suggestions; because they can picture a different finished product to you. During Red Pen's development I would share Red Pen with other designers who would give me feedback about Red Pen on Red Pen (whoa).
Back-end learning was harder because I came in (a year ago) with little Ruby or Rails knowledge. Why the Lucky Stiff's ebook on Ruby was inspirational (and it had cartoons cats!!). Rails for Zombies was a nice primer to Rails. The rest was Google. Knowing devs was a bonus because I could hire them to cover my arse (security audits and performance optimisation.)
I used to do a similar thing on Basecamp. Annotate the picture with OS X's Preview.app and then drag and drop to upload it.
Collect the textual feedback and then upload a new work again. Repeat that for like 10 iterations.
Also, I upload the works for remote peer reviews. Not real-time client reviews.
In those cases, there isn't a strong advantage in using Red Pen.
Just share my thoughts.
Pricing
Log in
This word's meaning has been hugely diluted but "experience" matters. If you're trying to communicate something, you want your message to come across as you intend. If you want someone to be honest with you, you want them to feel at ease. That's the difference. It's easy to give feedback on Red Pen.