We just got an angel round for a destop sw startup. It is a visualization tool that is OpenGL heavy and I'm not sure how I'd deliver that over the interwebs. www.uuorld.com We're using trolltech's Qt and releasing on Win32, OS X, and Linux. If anyone knows of any mature packages for interactive 3d over the web, I'm all ears.
Torque, Torque Advance, and now apparently Torque X. http://www.garagegames.com "Mature packages for interactive 3D over the web" They are general purpose game building frameworks. I am currently working with it in MMO form, all implementation code in Python. It is a mature package for interactive 3D over the web if I ever saw one. Hmm.. there may be something to that.... hey thanks! :)
Is anyone working on something that is not a website?
41–50 of 68 posts
Re: Is anyone working on something that is not a website?
#42Our product is not a website, but it is web-based (it is installable web-based system administration tools). I dunno if that qualifies by your definition. So we have all of the pain of developing a web-based application (browser incompatibilities, limitations of the medium, etc.) with all of the negatives of installed applications (high barrier to adoption, lower volume, etc.). But it does give us a business model th…
If your making your clients install software, why not just make your clients install a specific broswer ?
Seriously: Because we don't want to be evil. We're willing to not have rounded corners in some browsers, or have menus that don't get animation, or whatever...but we're not willing to prevent anyone (even folks who are blind or otherwise have accessibility problems) from using our product.
Re: Is anyone working on something that is not a website?
#43In addition to some web applications, I am slowly developing several products in the chemical sector. (I am a chemical engineer by training). But, the barriers to entry are so high and the risks are so great (often including literal physical danger) that software is decisively more attractive.
Re: Is anyone working on something that is not a website?
#44Earlier quoted context omitted.
"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 responsivene…
"I've done both desktop/server software and web software, and IMHO good web software is harder." I can only ask what kind of software have you developed, sir? If web software was harder, you wouldn't see "products" created over a weekend shaping up into companies a week later. And don't get me started on "millions of users on dozen boxes". The primitiveness of web application development is mainly the reason why so m…
Re: Is anyone working on something that is not a website?
#45I am working on WiMax, the next generation wireless network.
Re: Is anyone working on something that is not a website?
#46I'm fascinated by businesses that still deal in physical goods or services, but are enabled because of the web. The two best examples being netflix and city carshare-type businesses.
for example, here's an idea that's been kicking around in my head. (i'm not the right guy to start this company, so i'll just throw out this there.)
you know how people at the gym often track their workouts -- "3 sets, 10 reps, 150 lbs" -- with pencil and paper? that's so 20th century. why not build a sensor network for exercise equipment? you get on a scale or weight/cardio machine. it knows who you are -- RFID in your membership card? -- and it wirelessly uploads your workout data from that machine to a server.
as a gym member, you get a login to an accompanying web app, which is automagically populated with your data. you can set goals, track your workouts + results with pretty graphs, etc. no more paper+pencil tracking -- just work out and log in.
sell this sensor/software platform to gyms (or perhaps the equipment manufacturers), and you've got yourself a business.
where does the internet come in? well, aside from the tracking app for individuals, with all this aggregate data, you'd revolutionize exercise science. is interval training really better than marathon cardio sessions? more weight+fewer reps, or less weight+more reps? even basic collaborative filtering would be cool: "people with bodies like yours got these results with this workout plan."
it'd disrupt the (absurdly lucrative) personal training industry.
point is, out there in the "real world," there's tons of data that's just waiting to be aggregated and analyzed. that'll certainly be the basis of many interesting companies.
Re: Is anyone working on something that is not a website?
#47Re: Is anyone working on something that is not a website?
#48Re: Is anyone working on something that is not a website?
#49Protocol is named DITP (distributed information transfer protocol) and uses IDR (information data representation) as encoding rule (it's binary). The infrastructure is named DIS (distributed information system).
Some usable code will be out in a few weeks. The system is original in many ways and the curently forseen business model might be too. Coming out will be announced on Y Combinator news.
Re: Is anyone working on something that is not a website?
#50Earlier quoted context omitted.
"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 responsivene…
I'm not really sure why you think that web development is the only form of software development that writes distributed software. This seems like a bogus assumption. I've worked on two large projects that are distributed and not web based.
The difference is that in a webapp, you have to think of the implications of distribution on every user request. So you have to consider latency and status feedback for everything the user does, you can't use shared state, you have to keep in-memory data structures to a minimum, you can't count on getting notification when events occur, and so on. Desktop-based apps with a distributed back-end usually have a well-defined interface to the cluster. As long as you don't need to update the backend, you can keep anything you want in memory. And you usually have a two-way connection: you don't need to frame everything in terms of request/responses.