Update: The problem isn’t on Instapaper’s end. Marco already has a similar solution to what I suggested.
“Amazon doesn’t reliably deliver my messages to customers’ Kindles. For some people, it works great. For others, I trigger some filter after a while and Amazon randomly blocks Instapaper emails from hitting their accounts unless they call Amazon’s customer service and have them remove the block.”
That’s a shame because Instapaper would be that much more useful with consistent support from Amazon’s PDF conversion service.
I am constantly reading books, but they are mostly technical ones that I like to highlight and markup the margins. Amazon’s Kindle wouldn’t do me much good there. I read tons of blog articles, usually 20 at a time. This is where the combination of Instapaper and Kindle can become a game changer.
There is one thing that will immediately get me to shell out $259 for the Kindle: Instapaper automatically syncing with the Kindle. Instapaper has become a part of my daily routine. I check my feeds throughout the day, open any articles I want to read and save them to my Instapaper account. After I’m done work for the day, I sit on my couch and read the articles from Instapaper on my MacBook. Reading on a backlit screen isn’t ideal because it strains my eyes (and I’m a pretty young lad). I’ve tried reading on my iPhone too, but that didn’t help much either.
Possible User Experience for InstaKindle1
Not much would change about the way I save my articles. What would change is how I read them. Every night, my unread articles on Instapaper would be quietly converted to a single PDF document and emailed to my special Kindle address.2 It would arrive at my virtual doorstep at 6am and be ready for consumption during my morning tea. It would imitate the experience of a morning newspaper at a much lower cost. It would be targeted to exactly the articles I want to read because I’m the one that picked them. It would be comparably easy to read because of the Kindle’s E Ink.
Having Instapaper and the Kindle collaborate to bring me my ultra-targeted newspaper subscription in the morning would be the ideal experience for me.
- I just made that name up. Feel free to use it, although Amazon might not like that. [↩]
- Marco Arment already has a great start to this functionality. [↩]



23
Oct 09
Do Blogs Need Your Email When You Comment?
Short Answer: No.
Long Answer: The point of having an email field in a comment form is to have a way for the site owner to contact the commenter. I do not believe that field is necessary and adds unnecessary complexity to your form. Complexity discourages people from commenting and in turn weakens your blog community.
Real life example: Imagine you are giving a keynote. After your talk, you strike up conversations with audience members. They compliment you, ask you questions, and suggest alternatives to what you said. All of these are real world comments, but you’re not asking for any email address. At the most, you’ll ask their name to keep in touch.
That same practice should carry over to the blog world. People’s names and comments are most important to the discussion. If the person wants to be contacted, they can leave a link to one of their sites.
Spencer Fry eliminating one field form his comment form encourages readers to leave a comment.
Always keep your fields down to the bare minimum. Only include basic fundamental fields to ease the burden on your users.
Update: What’s worse than asking for your email when you want to comment?
Answer: Having an email field and a CAPTCHA. This is from a user experience blog nonetheless, the last place I'd expect to see one.