HN user

grahamr

150 karma

now: founder & cto, rewarder.com past: vp products at localyte.com: travel like a local! past: product manager at intuit, 2004-2008 technical interests: rails, usability research, creating engaged online communities, elegant UI design, welding, fabrication

grahamr AT gmail.com

Posts4
Comments22
View on HN

I think it was Adobe that forgot it was a company that makes tools. They did make it Flash versus HTML5, and are now realizing that they should have been agnostic as a toolmaker.

I use the paperclip gem and store files on S3 with my Heroku apps and it works great. I believe this approach is very common.

I tend to think no. For a small site with few users, no one will care. Once a site has become large enough, downtime with press coverage seems to create a virtuous cycle of social proof, e.g. Twitter, Facebook, etc.

Free: http://openinviter.com/

Paid: http://www.octazen.com/ http://addressbookimport.com http://www.improsys.com/importer.htm

Most of these have the best support for PHP which may or may not work for your needs. Various free libraries have been released for other languages but 1) generally support only a few email providers and 2) may not be actively maintained. Octazen has a fee-based API which sounds great but I haven't used it.

I think the subtle point here is that users don't want bloated applications but 1) They will vocally advocate for additional features that meet their specific needs 2) They will buy upgrades (particularly of boxed software) based primarily on new/additional features

As an entrepreneur, I strongly want to believe that something which many people find useful or even depend on can find a viable business model.

I think this helps explain the obsession over Twitter and Facebook monetization within tech circles.

I think this article has some good tactics. Three additional points I would add:

1. An incredibly valuable skill is being able to clear your mind and see what you're working on from the fresh perspective of a potential user. This is even easier if you are your own target audience, or if your product is such that your team can 'eat your own dogfood.'

2. Don't forget that usability testing typically only makes sense if the participant is in your target audience. If you are targeting some sort of specific niche audience or need (and most businesses probably are), it's worth taking time/$ to find the right kind of person versus someone online who has no context for the need you're trying to solve. If you already have customers, some of them will almost certainly be excited to help test new features.

3. If you're doing research interactively, consider having someone who didn't design the product asking the questions: it's really easy to bias the results based on your expectations.

Finally, it's certainly not cheap but if you ever have a chance to do usability research in a lab with genuine 1-way glass, it's a blast!

First impressions: I really like the overall look & feel of the site: approachable, modern, clean, and not needlessly "web 2.0"

I have trouble knowing from your messaging who your target audience is, and whether I'm in it. E.g. needs for someone who travels casually and who is accruing miles towards a particular vacation would be very different for someone who travels for a living and has dozens of accounts to keep track of.

For me, I've mostly standardized on United Mileage Plus and therefore make sure that any reward programs I participate in are compatible with United's program. Therefore, United's site serves as the aggregator for all my mileage/reward programs.

I'll sign up and see how it goes.

As others have mentioned, the key distinction is whether you're targeting individuals or businesses.

Typically you'll have a tough time convincing individuals to part with $20 per month and typically there's a free alternative.

It's much easier to convince businesses to spend the same amount and, as a bonus, many will be suspicious of free offerings. In fact, others will subscript to a higher premium tier purely to "buy the best for my business."

I always refer people to this StartupSchool talk by DHH of 37signals which outlines their business model, and explains their focus on small businesses: http://www.omnisio.com/startupschool08/david-heinemeier-hans...

As a customer, I hate getting gouged by text messaging.

As an entrepreneur, it gives me hope that there are useful services which people are willing to pay for directly. The social/viral distribution of sms is impressive: it costs me to send a message to my friends, and I'm encouraging them to spend money with their provider in order to respond.

The reason I left a cushy, high-paying job was that I think I can always get another cushy, high-paying job even when I'm older. On the other hand, my mid-twenties are years when I can afford to take (calculated) risks and do all the things I know I will have regretted not doing when I'm in my 30s and 40s and have more responsibilities.

I was also surprised how many people at and above my level in a big company seemed envious that I'd go to a startup.

I agree with you that the writing is often not great.

On the other hand, I see a disproportionate number of "Top X reasons"-like posts hitting digg and delicious/popular which leads me to believe that lists resonate well with readers. I'm not a blogger or link-baiter, but I'd prefer to write a mediocre article which is read thousands of times via prominence on social media sites versus a 'well-written' article with no numbers/lists that no one reads.

It seems like consumers of blogs and social media like lists, so bloggers logically satisfy that need.

I highly recommend the Lynda.com online training for rails: http://movielibrary.lynda.com/html/modListing.asp?sid=229 It does a great job of explaining the theory of rails and is a great intro to ruby as well.

Obviously Agile Web Development with Rails is the bible of RoR books: http://www.pragmaticprogrammer.com/titles/rails2/

I'd personally be wary of many of the RoR tutorials you'll find online: none of the ones I used did a good job of explaining rails at the conceptual level: you'll end up with a rails app from the tutorial, but limited understanding of what you did and why.

Updated:

This page has a good selection of relevant books: http://www.sapphiresteel.com/Ruby-and-Rails-Books-the-essential

My opinion is that one should begin with a Rails-specific book or tutorial and not feel the need to learn Ruby first. Much of rails code is specific to rails and, while you'll want to master Ruby eventually, you'll get enough from the Rails books.