what are you describing as a desktop app?
-you can always create a plugin.
2) no graphics card. -there are a number of 3d accelerated plugins out there -http://www.papervision3d.org/
3) no digital camera. -i think flash connects to your digital camera
4) no phone. - flash and voip are being used together
5) no clipboard for anything but text. - link to a web copy of it
6) if I want to email my image from fauxto or flickr to someone via gmail I have to download them it upload it. (Nobody ever mentions this elephant in the web 2.0 living room. How do you get data from one web app to another? An un-started startup perhaps?) - we are using a combination of flash, javascript, and web proxies
7) Half ass interfaces. I really give props to the fauxto guys for pushing the limits but only half ass users like me will ever see it as a worthy replacement for photoshop. -its hard but the pay off is huge because of the reasons you listed above for a web app.
8) No OS integration. I like how Address Book, iPhoto and iCal can talk to Mail.app. that can all work together between web apps.
2) I've heard of papervision. But see #1. I also went to their site and I couldn't get past the landing page in safari. I'll try it in FFX later but I just would have lost every mac user who tried to install someone else's plugin.
3) If flash connects to your digi camera then it can probably connect to an iPod or any other USB device. If that's the case you've got me, I didn't know that.
4) I didn't mean voip I meant phone as a device to sync contacts. But if, like you said, flash talks to USB then you've got me here.
5) I used a bad example. What if I want to edit a song in a web-based mp3 editor and bring it back to anywhere.fm. Unless each web app has access to the other you can't do that w/o a download and an upload. The file system is neutral territory on the desktop. It's the place every app understands. There is no web file system that every web app can access yet. (I actually think that would make a mean startup though.) Even if you're using a combo of flash, js and proxies, you still have to have an interface to the other web-app. Is there a common web-app to web-app interface that the industry has decided on?
7) You're right it is hard. And I really do commend the people who have taken it so far. But most of your answers remind me of the people I see camping who have solar showers, fold out chairs and a battery powered TV. I look at them and say, "why not just go home?" There are a million hacks that get the job done but each one waters down functionality and increases complexity. Almost every answer you've given involves non-browser SW on the desktop. So we're both straddling the desktop and web-based world. We just don't agree where the balance point lies. I think that in most cases existing desktop apps should be connected to web-services that facilitate backups, sharing and collaberation. You tip further toward the web end. I'm sure there is a time and place for both.
Re: But 6) and 8): at the current stage there hasn't been a lot of interaction between web apps. There isn't a reason why this can't happen. I'm not sure about images in gmail (why not send a link?) but applications like fauxto can get your images from links. All these i-products are made by one company, a web company can make its programs just as intertwined. As a parallel to your example I think a fair number of web applications work with google calendar.
Re: But 1-4: If your company wants to work at the stage people get data off their devices then a web startup makes no sense. Once they've done that though - the first things they want to do is share it. Thats why the internet is huge, there are other people on it.
The main issue, I think, is privacy and authentication. The only reason I can't have gmail directly slurp my images from facebook is that Google isn't on my friend's list. Though the last time I tried to upload an image with facebook, the interface didn't let me use a hyperlink. That's not a limitation of the internet, that's just a sucky interface.
So the issue does get talked about, just not in those terms specifically.
I know everyone here is game-set-match convinced that web apps are it and that's that. I think that apps involving LOADS of data like youtube, facebook or (my absolute favorite) fuzzwich belong on the web. But I'm really not that into the notion of replacing previously desktop based apps w/ web apps.
I've said this before, but it feels like a camping trip. You can survive, just not comfortably. I used fauxto the other day to edit some images and it was great. But it was only really great b/c it was free and b/c it was there when I needed it. But... I picked on tool to suck a color from one place and put it in another. I was confused for a long time b/c I was so used to the mouse pointer changing to represent eye dropper thing but it was still the arrow. Maybe they're new, and maybe this can be done through a browser but it brought home the feeling that I was on a camping trip carving meat with a swiss army knife. Take gmail, amazing interface, amazing search but how do I sync the contacts w/ my iPhone? I'm sure there is a 3rd party app that does it but you'll still use the desktop crutch.
I think that the tendancy toward web apps is more of a move away from microsoft than toward something better. But ironically you actually don't avoid the x-platform problem b/c browsers are all different.
The thing that's great about web apps is that you get:
1) automatic updates.
2) no install.
3) works from any machine.
4) access to reams of data.
5) collaberation.
But:
1) no iPod.
2) no graphics card.
3) no digital camera.
4) no phone.
5) no clipboard for anything but text.
6) if I want to email my image from fauxto or flickr to someone via gmail I have to download them it upload it. (Nobody ever mentions this elephant in the web 2.0 living room. How do you get data from one web app to another? An un-started startup perhaps?)
7) Half ass interfaces. I really give props to the fauxto guys for pushing the limits but only half ass users like me will ever see it as a worthy replacement for photoshop.
8) No OS integration. I like how Address Book, iPhoto and iCal can talk to Mail.app.
The tack we're taking is having the desktop richness along w/ a web component that allows publishing and sharing of data as well as intrinsic backups. A user can log in from another machine (w/ our app installed) and see all of his data as if he was on his own box. He can also access loads of data that other users have generated and made public. We use Qt for easy x-platform w/ native feel. We don't touch the registry. Users don't even need to be admin to install. The only thing we don't get is auto-updates. But we're taking the firefox tack and having them download in the background and install on the next app boot.
Much of my direction was inspired by a number of Steve Jobs speeches. Once my phone is a computer, when am I gonna need "my apps" on another person's computer? I'll never touch another person's computer. Thus partially negating the need for web apps.