We view this as a business within a business. Nobody from the Flow development team is being distracted with Concierge, it's just another part of the MetaLab umbrella.
Also, I find it weird that you think us "focusing on monetization" is a bad thing. What's wrong with having a sustainable business?
I appreciate what you're saying here, but I think you're mischaracterizing the point of both of our articles. Neither of us proposed our mockups as comprehensive redesigns or attempted to address anything past the basic visuals. I wanted to buy shoes, and I found it to be a really frustrating experience, so I said something.
If the door to a retail store is hard to open and you complain about it, does it make you an arrogant prick for failing to think through all the potential reasons for the problem? Maybe the company handyman only comes every two weeks. Maybe there's a mountain of paperwork required before any repairs can be made. Maybe the staff needs approval from management. Does that make your frustration with the door situation any less relevant? It definitely makes you empathize with the staff, and speaks volumes about the company's ineffective management, but that doesn't change the fact that the door is really hard to open, and this is a problem for you as well as other customers. Understanding the context is important, but it doesn't make our critiques any less relevant.
You argue that, "it’s easy to 'design' when you’re unencumbered by things like metrics, creative direction, business acumen, sales experience, actual functionality". Of course, but think about all the companies that manage to get it right. Huge, lumbering corporations like Amazon, JetBlue, and Virgin all manage to pull off great user experience despite facing the same challenges. Why shouldn't Zappos and American Airlines be held to the same standard?
I found the Zappos website insanely frustrating to use, so I spent an evening identifying some of the problems I spotted and added a mockup to clarify. Yes, I was a little inflammatory, but the overarching message was a positive one. I wasn't trying to tell them how to sell shoes or reinvent their business - my article was intended to show how a few simple changes overtop of the existing website could help make it easier to use. Blurry images have nothing to do with metrics, business acumen, or sales experience. If this helped push them towards making their website easier to use in any way, then I'm happy.
I feel awful for any designer who has to deal with Dilbertian management and bureaucracy, and I agree with the previous commenter - our frustration should have been primarily directed at the management team at either company. That still doesn't change the fact that there are designers responsible for crafting the pixels, and the pixels show a general lack of care. This might be due to the culture of the company, poor direction, or a myriad of other factors, but it doesn't make the work itself any less sloppy.
I'll be the first to admit that I'm a brash 23-year-old, but I'd rather say something and risk looking like an asshole than continue to patronize a company that doesn't care about their customer experience.
So when you glance at your car dashboard do you look for "DEFROST" or "RADIO POWER"? No, you look for cues based on positioning, size, and the icon on the button.
I'm Andrew, the guy who did it. The key thing that I want to drive home is that their execution stinks. I figure they know how to sell their product - they did $1 billion in sales last year - but the site itself is incredibly sloppy.
This is Andrew from MetaLab. I just wanted to say thanks for all the compliments on the design. I hope that you guys will take it for a spin and let us know what you think.
Quoted from cominatchu:
"The 'under 10k' price tag is misleading because it does not include the opportunity cost of the web designers time. In other words, one has to calculate (the hours spent by Metalab web designers * their normal hourly rate) and add this to 10k to arrive at a more accurate cost for building this site."
Yes, we really did build it for less than $10k. Our key expenses were: Rails development (1 developer a few hours a week), a SliceHost server, and some custom icons we hired out. We're planning to break it down in more detail on our blog in the next little while, but I'd like to debunk this a bit here. You're absolutely right about the cost being higher if you consider what it would normally cost at a full consulting rate, but I feel like that's kind of fallacious logic:
If you learnt how to woodwork, built a bookshelf, then told your friends that it cost you $15 (the price of the wood and a couple of screws), they aren't going to argue that the true cost was $500 (the hours spent learning woodworking or a carpenter's rate).
If a founder who was an incredible programmer paid himself $1,000/month during the early months of his startup, would you say that his time really cost the company $15,000 (what he would have charged at a consulting rate)?
The point isn't that someone with no technical skills can do this for 10k (after all, this is Hacker News, and I assume most of you are highly skilled in the field), we're just pointing out that we managed to create a business by pulling a few extra hours a week over 6 months. We didn't have to quit our day jobs, move to the valley, or build a board of advisors - we just went ahead and built it. This isn't to say that it's an especially complex app or that it is some sort of technical feat, just that a little bit of money went a long way.
I don't think taking funding is always bad or anything, especially small seed funding like YC. Sometimes advantageous ideas need money to make them happen. The point is that most of you already have many of the skills required to build things, so funding really shouldn't be a barrier to entry. If your idea requires more money than you have, boil it down to the bare minimum and build it within your budget. We could easily have decided that we wanted to build the best invoicing app ever, figured out that invoicing was a 1.3 kagillion dollar industry, secured some funding, built up the stakes, then gone crazy with features. We could have convinced ourselves that we needed to close down our consulting business, hire a full-time Rails developer, and move in together. Instead we took a simple idea that we felt wasn't being done right, boiled it down to its core, then built it when we had the time.