raganwald
(This is a snapshot of my old weblog. New posts and selected republished essays can be found at raganwald.com.)

Thursday, October 06, 2005
  The classic question: end-to-end or point solution?


This has got to be the most basic design question, ever. It's so universal, it applies to everything. Specialist or generalist? Full-service department store or specialty boutique? Integrated application or specialist tool?

The fact is that these "point solutions" have a vitality that comes from their authenticity, their simplicity, and their sizable and active user bases.

I heard a user of one of these services talk a couple weeks ago about the "emotional connection" he had to one of these services.

I know what he is talking about. I feel that way about Flickr, Typepad, Google, My Yahoo!, delicious, and many other web services I use on a daily basis.

I have rolled my own web experience and it is unique to me. It is mine.

Fred Wilson, "Point Solutions vs End to End Solutions"
Fred does a good job of contrasting the approaches in the web services and web application business. Are point solutions strictly for early adopters and end-to-end solutions (like Yahoo! and AOL) for the mainstream?

I wouldn't count on it. If that was the case, why don't AOL and Microsoft own the Internet? It's not for a lack of trying or paucity of resources. Google seems to be trying to do it by becoming Yahoo. Strange that they aren't dancing with the date they brought to the ball... their success began with laser-like specialist focus.

All in all, I suggest making the very best software you can. That almost always means making a narrower tool that is more focused.

That doesn't mean making a web service that can't do anything until someone mashes it up with another tool. You'll notice that point solutions are still solutions. You still have to solve one problem and solve it well.
 

Comments on “The classic question: end-to-end or point solution?:
Agreed.
 




<< Home
Reg Braithwaite


Recent Writing
Homoiconic Technical Writing / raganwald.posterous.com

Books
What I‘ve Learned From Failure / Kestrels, Quirky Birds, and Hopeless Egocentricity

Share
rewrite_rails / andand / unfold.rb / string_to_proc.rb / dsl_and_let.rb / comprehension.rb / lazy_lists.rb

Beauty
IS-STRICTLY-EQUIVALENT-TO-A / Spaghetti-Western Coding / Golf is a good program spoiled / Programming conventions as signals / Not all functions should be object methods

The Not So Big Software Design / Writing programs for people to read / Why Why Functional Programming Matters Matters / But Y would I want to do a thing like this?

Work
The single most important thing you must do to improve your programming career / The Naïve Approach to Hiring People / No Disrespect / Take control of your interview / Three tips for getting a job through a recruiter / My favourite interview question

Management
Exception Handling in Software Development / What if powerful languages and idioms only work for small teams? / Bricks / Which theory fits the evidence? / Still failing, still learning / What I’ve learned from failure

Notation
The unary ampersand in Ruby / (1..100).inject(&:+) / The challenge of teaching yourself a programming language / The significance of the meta-circular interpreter / Block-Structured Javascript / Haskell, Ruby and Infinity / Closures and Higher-Order Functions

Opinion
Why Apple is more expensive than Amazon / Why we are the biggest obstacles to our own growth / Is software the documentation of business process mistakes? / We have lost control of the apparatus / What I’ve Learned From Sales I, II, III

Whimsey
The Narcissism of Small Code Differences / Billy Martin’s Technique for Managing his Manager / Three stories about The Tao / Programming Language Stories / Why You Need a Degree to Work For BigCo

History
06/04 / 07/04 / 08/04 / 09/04 / 10/04 / 11/04 / 12/04 / 01/05 / 02/05 / 03/05 / 04/05 / 06/05 / 07/05 / 08/05 / 09/05 / 10/05 / 11/05 / 01/06 / 02/06 / 03/06 / 04/06 / 05/06 / 06/06 / 07/06 / 08/06 / 09/06 / 10/06 / 11/06 / 12/06 / 01/07 / 02/07 / 03/07 / 04/07 / 05/07 / 06/07 / 07/07 / 08/07 / 09/07 / 10/07 / 11/07 / 12/07 / 01/08 / 02/08 / 03/08 / 04/08 / 05/08 / 06/08 / 07/08 /