What ensures compliance with LI TOS? Nothing, really. Including Dux.

Interesting, what is your job? Contract lawyer? do you work in biglaw or in house counsel? or a vc firm?

Engineering marketing concentrating on government proposal requests. That involves contracts, described scopes of work, etc.

Seconding this :)

Ride (Uber for commuting) just launched yesterday. Given the size of their team and funding, I'm surprised that they'd pull something off like stealing an image from Apple's support page and replacing a logo.

This is very cool! makes me want to take a vacation... if I didn't have a 5 month old!

I like that i can almost 'sketch' out possibilities with the tool. reminds me almost like a vacation planning version of hipmunk in that sense. I like UIs that are flexible like this.

That WSJ article that Jessica was quoted from HN yesterday also made me think of you!

Hmm... I don't completely agree that adding Show HN would be a replacement for Product Hunt. It feels like the two communities are pretty different, and creating a separate community for product launches gives you the flexibility to incorporate new social protocols (like the AMA) more easily, and add in visual elements like mockups.

Just my 2 cents!

Agreed. Product Hunt and HN share a lot in common (and in part, HN inspired PH) but they're not competitive.

They have different audiences and longer term they will look much different from one another.

Hmm, what is the longer term vision you have in mind?

Congratulations Ryan, I feel lucky to be an early part of this (user #3 baby!) when you just sat down to think about doing it. It's come along a long way already, I can't imagine where this is going to end up in a year.

It’s a shame that this post can even be deemed heretical when in fact it’s the normal mechanism for completing tasks by the vast preponderance of developers for overcoming technical challenges.

Understanding the ways in which technical people find answers, and can fully grok and socialize those answers internally with options is invaluable in a technical interview.

The applicant can already do this, in asking the right sorts of questions from the interviewer to help them solve whatever rut they've found themselves in.

Products fall into multiple categories based on patterns of usage and intended audience.

Some products are daily/heavy use products which should optimize for the expert user. These products need to be designed such that, once the user has an understanding of how to navigate and understand the product's functionality, they can perform regular actions with ease.

Examples: A Todo list, a weather app, or an app for sports scores and the news on a mobile phone. A POS (Point of Sale) system where the operator has some sufficient time for training [Keep in mind that POS systems are designed for fast transactions to keep lines short and moving smoothly].

--

Other products are used many times by different users, infrequently. These interfaces need to be designed such that they're intuitive, require as little handholding as possible, and should offer 80% of the benefit for 20% of the effort. Additionally, that 20% of the effort should be possible by almost all of the people who enter into the experience.

Examples: a photo kiosk at the local drugstore, a fast food ordering counter with an iPad or self-checkout system at a grocery store.

What does this have to do with UI walkthroughs? Because the first class of products are not designed to be intuitive on first usage, they need scaffolds (extreme way of conveying this is a "crutch") for the user to understand their operating protocol. Once the user understands how the system works, then they will be able to use the product quickly and effectively on a repeated basis.