91 karma · joined April 23, 2008
We were actually pretty surprised to see users sharing their startpages on their blogs and such. At first we didn't really get it; I mean the only reason we made them public was so that you could access it from where ever you were without having to log in. Basically, we made start.io to act as an attachment to a browser.
But some people really do like sharing their links. Maybe it's just that they're used to sharing all their content online. One of the most visited start pages comes from a ministry sharing belief-oriented links to their visitors.
I'm not sure what un-prepped signups will use it for, but I don't really care, either. We developed this to be a flexible platform from the beginning. That's just what happens when you made a product customizable, and for a general purpose. People will shape it to their needs. The obvious example here is Twitter, which began as a service to publish away messages to the web. Then people wanted to group their thoughts to channels, then they wanted to message, now they want to network and expand their names and products. Twitter is a good example of a platform that made getting information from the users brain to a public domain incredibly easy.
Thanks for all the comments so far, this is great.
While you may find it challenging to read straight through, it works well, too, as something to pick up every so often or to read alongside other reading material. Even for those of you without a peaking interest in business, the advice presented in the book is undeniable logic that will definitely appeal to programmers and entrepreneurs alike.
http://www.amazon.com/Thinking-Strategically-Competitive-Bus...
We pushed it live just earlier today, so I don't have much data to share with you quite yet, but I'm curious to hear what the rest of you think about splash pages. Particularly ones that have a style that's different from the rest of the site. Have you seen any changes in your number of signups? Did you attract a different sort of user that wouldn't normally sign up?
http://www.ted.com/index.php/talks/view/id/197
Very inspiration for designers and engineers alike.
I will be curious to see how lean the product stays when as the updates continue to roll in.
To save time on both halves. That is, the designer is designing his/her piece without worry of the difficulty, and the programmer is designing the framework without worry of user intuitiveness and style.
It so often occurs that the designer and the programmer have slightly different ways of thinking. Each party has separate concerns for the final product, and each half should be individually thinking about the future of their work and how each can be maintained.
This article may certainly apply to, and almost addresses, a programmer without a sense of concern for the user's experience and general usability.
As a front-end designer, I need the mockup process for my own sake even more than for the sake of the final product. Personally speaking, if I were to attempt complex mockups without first laying out a grid and carefully choosing my color palette, I would quickly be overcome with the duties of writing the code, and the hundreds of short-term problem solving that would arrive. My passion is never to become a flawless programmer, but it is to flawlessly design an intuitive interface. When I am creating a mockup in photoshop, what I'm doing in my head is pretending. I imagine over and over again that I am a first time user to the site, and maybe even to the internet. This duty is daunting enough without having concern over how I will make it work.
Again, this article may whisper sweet nothings to a programmer on a tight schedule, but I can guarantee you that the time to simply layout a grid and pretend will save you the time it takes to just load the monster application. And I don't know about you, but I cannot imagine a site's usability on a simple piece of paper.