Is anyone working on something that is not a website?

Web is certainly where the money can be at. But everyone probably realizes that there are plenty of other things you can do and still create a startup. The advice in Paul Graham's essays and YCombinator's library holds just as true if you're not working on a webpage startup.

For example, I read about someone who created a startup selling knife sheaths on EBay. Even if he were to create a website advertising his knife sheaths, he still wouldn't really have a webpage startup.

So, is anyone working on a non-webpage startup, and if so, what're you doing? :)

Shawn

There are plenty of startups that make cool software. Trolltech, Sleepycat (now Oracle), VMWare, Coverity are just a few that come to mind. I think the main difference between software startups compared to web startups is that there is a lot more depth to them. I don't think an average kid out of college is capable of something like this.

I am working on software development tools: http://www.codesynthesis.com

I have plans for two projects dealing in physical goods. For one, I'll probably use cafepress for production & fulfillment until volume justifies reshuffling my supply chain.

For another, I'm going to advertise a blog we already have that has a small but growing audience. We'll have a small inventory with a limited number of skus. We'll probably make the items ourselves. I'm not sure how I'll handle the commerce (ebay, yahoo store, paypay...). We'll do fulfillment ourselves too. Once we establish a microbrand I have what I think is a clever bundling idea to increase our average transaction size by about 2-5 fold without needing to bloat our inventory. At that point, I'm not sure exactly what's next, we might try it on a small scale, continuing doing our own manufacturing, or we might line up offshore manufacturing and outsourced fulfillment and make a big push. I think we'll probably do a blend of the two. Start rolling out the evolved business model while still making the items ourselves at the same time we're lining up manufacturing and fulfillment with the goal for having them on-line in time for the holiday shopping season.

I also have ideas for web apps, but I'm cautious about both ad revenue and hoping to be bought out. I do have an idea for a service that would be monetized by transaction based revenue, but I have quite figured out how to put it into practice.

"I don't think an average kid out of college is capable of something like this."

I've done both desktop/server software and web software, and IMHO good web software is harder. With web software, you have to explicitly think about many things that just aren't an issue with conventional software, like how to distribute the load of a million users over dozens of boxes. It helps that user expectations for UI responsiveness and robustness are somewhat lower with webapps, but that's changing with AJAX. You also need to know many more technologies to build a successful webapp: CSS, HTML, Javascript, a web scripting language, SQL, database performance, server administration & shell scripts, and any libraries necessary for your problem domain.

It is a completely different skillset. With conventional apps, you need to know how to architect a large single app instead of architecting a large collection of collaborating servers. You need to know C++, Java, or C# instead of PHP/Python/Ruby. You need to know intimately the particular toolset that your app fits into - VMWare can't live without device drivers; Sleepycat can't live without transaction algorithms; one desktop app I worked on needed an intimate knowledge of TCP, including Winsock LSPs and Linux kernel hacking. You get much more out of deep knowledge with conventional apps, while webapps require a more shallow understanding of a very broad range of topics.

Also, the technologies you need for desktop apps don't have zillions of articles on them plastered across the web, and the documentation is often poor quality. But if you take a professional software engineering job, you'll be expected to make sense of it and figure out how everything works (possibly through prototypes, debuggers, and a lot of pain and patience). It's not taught in college, but that doesn't make it particularly difficult.

There are some food items that I would love to import/produce in the US, from Italy. I'll see about it when/if we ever move back to the states. Food has a lot of legal requirements, and more capital to start something up. On the other hand, it's the thing I'm most certain of in terms of I know people would like this stuff.