4 ms·
Add directory services and it becomes the way to communicate at a company replacing Outlook/Exchange, MSN, Twitter, Skype. I plan on using it at my company. T
by jamesk2 17y ago
Add directory services and it becomes the way to communicate at a company replacing Outlook/Exchange, MSN, Twitter, Skype.
I plan on using it at my company.
The only wish feature is directory services with administrative controls.
- windsurfer 17y agoHow can you be planning to use it without trying it out?
- qeorge 17y agoUse what where? There's no product here. I don't mean to be rude, but are you comfortable making Wave a big part of your organization's process and culture? What will you do if Google stops developing Wave?
- dave_au 17y agoThey're releasing the spec and large chunk of the code openly - if it's a good idea and google stop developing it I'm sure someone else will step in.
- qeorge 17y agoThat's not how B2B services work though. Dependability trumps everything. If your organization depends on a niche product who's provider exits the business you've got a big problem. Lets say Google releases Wave, it doesn't gain a lot of traction, and they Jaiku it. For someone to pick up where they left off a lot of things would need to happen: - Google would have to enable exporting your data capital into a standard format - The new provider would have to match Google's now defunct service feature-for-feature - The new provider would have to have the infrastructure to handle this demanding XMPP app, which has real-time editing to the nth degree, and store all of the associated rich media assets - The new provider would have to find a business model which would sustain such expenses, succeeding where Google had failed On top of this, the new developers would be expected to iterate the product, provide customer support, and solve whatever problems caused the app to fail under Google's tenure. If you're sure Google will stick with Wave then none of this matters. But that's not a bet I'd take.