I use this on both my iPad and iPhone, and while it is definitely buggy (will occasionally fail to populate the URL field, as well as hangs a lot), I generally find it indispensable for sending Safari links to Evernote.My biggest gripe, however, is with its URL-scheme/bookmarklet support. I sync my iOS bookmarks between my iPhone and iPad via iCloud, and because of this, I can't use the EverWebClipper bookmarklet on both devices because the iPad version uses the URL scheme "everwebclipperhd://", while the iPhone version uses "everwebclipper://". So if you created the bookmarklet on your iPad, invoking the bookmarklet will only work on the iPad, but not the iPhone (or vice versa).The ugly workaround for this problem is to create two separate bookmarklets for both the iPad and iPhone. But there really should be a unified URL scheme between the iPad and iPhone versions of this app, so you don't have to resort to ugly hacks like this. The only reason I can think of as to why there's two different URL schemes is so that cheapskates who purchased the iPhone version first can use the iPhone version app on their iPad, without having to pay for the "HD" iPad version. While that makes sense on the surface, I can't imagine that anyone who purchased the iPad version would have any need to also simultaneously have the iPhone version on their iPad, so there isn't much sense in having a seperate everwebclipperhd:// URL scheme for the iPad.
Show Less 
