Kapitall

Don’t Make Me Sign Up

If you’re product is truly desired and has a good purpose, people will sign up to use it no matter what.  But don’t force your visitors to sign up just to look at the capabilities of your site, that’s just plain annoying.  Here’s a quick example of Kapitall.com:

I’m visiting, so let me try out the product.  I neither want to give you my information, read the terms and conditions document, nor want to sign up for your newsletter.  So don’t block me from your supposedly great product with a modal dialog.  I’d rather go straight into demoing the product, then sign up when I want to use it.

What shape would a hybrid be?

There’s been a growing recognition & usage of the term T-Shaped people.  What’s a T-Shaped person you ask?  Well, to summarize, a T-Shaped person is an individual that has a depth of experience/skills in one specific area, but also has a breath of knowledge in a number of other fields.  The depth is represented by the vertical strike, and the breath is marked by the horizontal line.

Well, I had a conversation last night regarding how I’m a hybrid of an engineer and a designer, so what shape would I be?  The letter T won’t work here because I have two verticals of experience/skills.  Possible candidates are the letters of N, U, H, and X:

  • N – There are two verticals, cross linked between by a diagonal slash.  The diagonal slash forms a continuous pathway between the two verticals, sort of suggesting that one discipline picks up when and where the other one ends.
  • U – There are also two verticals, but they are linked with a curved pathway.  The parallel characteristics at the top of the U suggests that the separate disciplines will forever remain separated.  But the curved link at the bottom of the U suggests that the two disciplines can bend and become one.  (Wow, that’s pretty powerful).
  • H – The two verticals are joined by a straight horizontal bar in the middle.  This reminds me a bit of the interpretation of the T.  However, the horizontal bar of the H is terminated at the two verticals, which kinda suggests that one cannot extend beyond the two dominate disciplines.  Whereas the T’s vertical bar can technically extend indefinitely, thus suggesting potential for infinite growth of breath.  H also stands for Hybrid, but that’s not that great of a reason.
  • X – The two verticals aren’t actually verticals, but intersecting diagonals.  This is a pretty good illustration of how a true hybrid operates on a regular basis.  Whatever it is that I’m doing, I often switch between my logical engineer brain (left) and my creative designer brain (right), so I can examine the subject/problem/issue with different angles.  Also, the openness of the line endings suggests potential for growth in all directions – a very good characteristic for a hybrid believer.  We’re constantly striving to become better in each of our disciplines, but it’s the cross-linking of the two disciplines that makes us special.

So, which letter should be used to represent the hybrid individual?  My vote goes to either U or X, with a strong preference for X.  (It’s kinda funny how UX stands for usability experience, which is one of my favorite subjects).  Here’s a bit more reasoning for my preference of X over U:

  • The crossing of the X is at the middle, and that suggests frequent switching between the two disciplines/mindsets.  Whereas, the U shape suggests more of a sequential order.  When it comes to UI development, I would try to engineer a great solution, but at the same time keep my mind constantly on designing for the end user.  It’s not engineer then design, or vice versa.  It’s engineer and design, at the same time.
  • As I mentioned earlier, the way the lines on the X points openly towards different directions suggests potential for open growth.  No matter how much each of those points extend – grow in a specific discipline – the two disciplines will always be connected at the center and integral to each other.  Whereas with the U, growth comes in two parallel verticals.  This suggests that the more growth happens in each discipline, the lesser impact the connection has on the two verticals.  Just think of a U with really really long verticals, you’ll get the idea.

I wonder what other hybrids out there might think, and which letter they prefer.  Maybe we can start a movement here, something to achieve recognition for hybrid individuals in a specialization-preferred world.

whichisit

Which is it?

As a usability junkie, one thing that bothers me frequently is the feedback message you get after an incorrect login.  The message typically goes something like this:

The message is 99% similar to Your Email or Password is incorrect. Well thanks, but which it is?  Is it my email (username)?  Or is it my password?  That error message doesn’t help me at all.  As a software engineer, I know it’s not that difficult to determine which of the two is incorrect.   I can:

  1. Check for the existence of the username/email submitted.  If it exists, go to #2.  If not, then say “Username is incorrect.”
  2. Check the correctness of the submitted password.  If it’s correct, then login.  If not, then say “Password is incorrect.”

Done.  Not that hard at all.

On the flip side, there are counter arguments against providing this sort of feedback (thanks to my buddy Steve who pointed them out to me):

  1. You wouldn’t want to confirm the existence of a user, because then it can be bombarded with password attempts for account access.
  2. You wouldn’t want to confirm the existence of an email address, because then it can be added to spamming lists.
  3. In API’s, most authentication methods are authenticate(username, password) that returns a True or False.  So you wouldn’t be able to determine the existence of a user.  (But I think this is just due to laziness.)

Counter arguments #2 and #3 do not hold much weight.  #2 can be addressed by spam filters.  Who among us do not receive a single piece of spam?  #3 is just a byproduct of laziness, I think.  #1 is the important one because technically speaking, it’s a very difficult problem to address.  The system admin might be able to implement some sort of lockout-after-X-attempts system, but that has the danger of locking out the actual user when the bombardment is performed by a perpetrator.  The admin can then move into IP-specific-lockout solutions, but those can be bypassed as well.  So ultimately, it becomes a tradeoff question:

What usability aspects can be bypassed in exchange for a simpler security scheme?