If UX can't make a decision on this issue, the marketing folk will respond, "we like sending email to users. Since, for once, the UX folks aren't raining on our parade, let's send it by default."

Should the middle mouse button close tabs? Yes. Do most users expect that behavior? I'm not sure, but the ones who don't are not middle clicking on tabs.

Maybe a dot in the middle of the d (like Source Code Pro's 0)? It would probably take a while to get used to it, though.

@RumiP. One possible compromise with your product owner: Don't call it "How would you like your name to be displayed in the application?" Call it, "Your Name" or "What is your name?" As with your original proposal, users who want to be addressed as "Dr." can enter "Dr." as part of their name.

While truly monochrome vision is incredibly rare, red-green color-blindness is common. Random googling suggests 7-10% (depending on who you ask) of males are red-green color-blind. So, using red/green as a sole method for communication is especially bad.

@SurrealDreams: The usual strategy is to A) have an upload size limit and B) just convert the file after the user uploads it.

Personally, I think I'd be more apt to share a video if it was launched within a youtube app than if it was launched in situ, since I am more comfortable with the definition of "share" within youtube than within an arbitrary app. That said, I'm not a typical user, so I don't know how well this carries to real users. RK, I think your flow is assuming the user is sharing within the app, but youtube has its own sharing functionality; some users are probably familiar with it. None of this applies to desktop apps; don't launch youtube from a desktop app.

@17of26: No, because that line makes use of the gap from the bottom line. It's possible that a variant on this question would be on topic within electronics.SE, if you want an answer from that perspective.

This is better, but personally I still feel uncomfortable with secret badges.

@David: It's not surprising that you aren't seeing one-page sites. The technology (browser support, engineering experience, library support) for doing so is somewhat new, and adoption takes a while. Further, more well-established sites tend to be hesitant (rightly so!) to do large-scale redesigns (and gradual redesigns take a long time to ramp up, for those taking a more measured approach).

Google recently spent a lot of time/money/effort redoing their play store to use a one-page layout. You may also have noticed that they've had their search load in the same page. Really, the main advantage one-page layouts have over identical, template-based layouts is that the site is feels more fluid and much more responsive. There is plenty of data to show that responsiveness significantly improves [insert metric your customer cares about].

@Keiwes: No. Any overlay (i.e., overlay on the tv screen itself) will be distracting. During regular TV watching, such an overlay would be a source of anger, akin to a prominent dead pixel on an LCD screen. However, such overlays are fine if integrated into an existing, user-acceptable overlay. Thus, showing such an indicator while the user is changing the volume is fine; the user is already partially disengaged from the show, and you're forced to show an overlay anyhow.

@snipe: The fact that these issues are easily addressed (for most sites; it's probably a big hassle to address them in some older sites) doesn't prevent them from being issues. However, non of these concerns are UX concerns.

Users have been trained to be wary of sites which perform transactions without SSL. Users do tend to prefer EV certificates over non-EV certificates. However, I suspect this is because browsers tend to use friendlier graphics for EV certificates (e.g., greens instead of yellows), rather than because users actually understand the difference between an EV certificate and a normal certificate.

I picked Install Later because right now I'm doing something important. What promise do I have that I won't be doing something important later? Per alexey's answer, I'd omit "Install Later."