Always good advice. I read another good version in an entirely unrelated context recently: "I think the secret to doing things is just doing things." (By the late Mark Baumer: http://thebaumer.com/post/155579953958/day-87-of-crossing-america-barefoot-day-87-vlog )

How do you use AirTable for design research? I have only seen the product demo video, but am having trouble imagining that use case.

For a general overview of some privacy-oriented services, see TorrentFreak's annual roundup: https://torrentfreak.com/vpn-services-anonymous-review-2017-170304/

One thing to note, some services (aka Netflix) will not work over most VPNs. I tried placing my whole network on a VPN, but reverted to connecting from the individual devices once all the denials became too annoying.

"Completely" is a bit strong. The new design is more usable for the task, but it is not obvious that the label deserves full credit. Besides having a label, the button is also much more visible. The original heart icon is practically invisible against the bright lights. Simply adding the transparent black box below the icon may have similar results.

Ha, sorry, I meant how is the quality of the transcriptions?

How do you find the automatic transcription? I've always had problems with it (Google, Watson, and others), especially for conversations with lots of jargon.

It sounds like in the proposed architecture, an email confirmation is still needed, but not right away. That is, a user can immediately start using the product without verifying their email address, but will need to do so eventually.

The million dollar question is when to require confirmation. The proposed answer (based on functionality/privileges) seems destined for failure. What if a user spends hours using your product, then comes across a "needs-confirmation" feature, and can't move forward because they mistyped their email on signup.? Or leaves and comes back a day later only to realize they can't login?

Maybe the solution is to give them a taste of the product "for free", then require email confirmation after X number of minutes (30? 1 hour?).

The trick is balancing not punishing people who enter everything correctly while ensuring people can recover from a (pretty common) error.

(Just an FYI, the text under The Deets says "Layers is a 3-day design conference taking place in San Francisco June 9-10 at the same time as WWDC." Should be June 8-10.)

Easily fixed: http://jsfiddle.net/qtg06ptx/4/