Skip to main content

How To Demo With Zero Barrier

When one browses to MindMeister and looks at the nicely designed page, the user will notice a nice screenshot of the service. This is not a screenshot, but an anonymous, live embedding of the actual mind mapping service. Right at the first page, you get to start messing around with things. I think all Web 2.0 apps need to provide this kind of immediate use. We can provide such a low barrier to use, with no installation, but we've really lowered the bar, so to speak. The users won't jump very high for us these days. Let them trip and fall right into our arms.

For Web 2.0 This Means...

Web-based applications need to provide an anonymous access to their application on the front page of the website. If you have a to-do application, let the user start interacting before they do anything. Even registration is a barrier to entry. Of course, if you take what they did anonymously and migrate it when they register, you get a gold star. You get two gold stars if you also keep their anonymous data around when they return with a cookie.

For Development Frameworks This Means...

Frameworks need to provide the infrastructure to do this easily. We build things in the context of a user, so sometimes there is a barrier we have to cross ourselves to provide this. Built-in ways to create anonymous uses, promote them with credentials, and expiration anonymous accounts: all will let developers provide this Siren call to users at little cost.

For Users This Means...

More choices, because I can try more things. I don't need to give out my information and remember credentials just to try out yet another twitter clone, to-do app, or mind mapping software.
Labels:

Comments

Post a Comment

Popular posts from this blog

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…
Post a Comment
Read more

On Pruning Your Passions

We live in a hobby-rich world. There is no shortage of pastimes to grow a passion for. There is a shortage of one thing: time to indulge those passions. If you're someone who pours your heart into that one thing that makes your life worthwhile, that's a great deal. But, what if you've got no shortage of interests that draw your attention and you realize you will never have the time for all of them?

If I look at all the things I'd love to do with my life as a rose bush I'm tending, I realize that careful pruning is essential for the best outcome. This is a hard lesson to learn, because it can mean cutting beautiful flowers and watching the petals fall to the ground to wither. It has to be done.

I have a full time job that takes a lot of my mental energy. I have a wife and a son and family time is very important in my house. I try to read more, and I want to keep up with new developments in my career, and I'm trying to make time for simple, intentional relaxing t…
Post a Comment
Read more

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…
1 comment
Read more