- Assume that no matter how amazing your new tech is, people are going to adopt it slowly.
- Give your early adopters every chance you can to use your offering together with the existing tools that they will continue to need in order to work with people who haven’t caught up yet.
- And if you’re building a communication tool, make it as simple as possible for others to build compatible tools, because they will expand the network of people your users can communicate with to populations you haven’t thought of and probably don’t understand.
On the death of Google/Apache Wave (and the lessons we can learn from it)
This article is entitled ‘How not to replace email’ and details both the demise of Google Wave and it’s open source continuation, Apache Wave:
As of a month ago, the Apache Wave project is “retired”. Few people noticed; in the seven years that Wave was an Apache Incubator open source project, it never had an official release, and was stuck at version 0.4-rc10 for the last three years.Yes, I know! There's been a couple of times over the last few years when I've thought that Wave would have been perfect for a project I was working on. But the open source version never seemed to be 'ready'.
The world want ready for it in 2010, but now would seem to be the perfect time for something like Wave:
2017 was a year of rapidly growing interest in federated communications tools such as Mastodon, which is an alternative to Twitter that doesn’t rely on a single central corporation. So this seems like a good time to revisit an early federated attempt to reinvent how we use the internet to communicate with each other.As the author notes, the problem was the overblown hype around it, causing Google to pull it after just three months. He quoted a friend of his who at one time was an active user:
We’d start sending messages with lots of diagrams, sketches, and stuff cribbed from Google Images, and then be able to turn those sort of longer-than-IM-shorter-than-email messages into actual design documents gradually.I feel this too, and it’s actually something we’ve been talking about for internal communications at Moodle. Telegram, (which we use kind of like Slack) is good for short, sharp communication, but there’s a gulf between that and, say, an email conversation or threaded forum discussion.In fact, I’d argue that even having a system that’s a messaging system designed for “a paragraph or two” was on its own worthwhile: even Slack isn’t quite geared toward that, and contrariwise, email […] felt more heavyweight than that. Wave felt like it encouraged the right amount of information per message.
Perhaps this is the sweet spot for the ‘social networking’ aspect of Project MoodleNet?
Wave’s failure didn’t have anything to do with the ideas that went into it.Helpfully, the author outlines some projects he’s been part of, after stating (my emphasis):Those ideas and goals are sound, and this failure even provided good evidence that there’s a real need for something kind of like Wave: fifty thousand people signed a petition to “Save Google Wave” after Google announced they were shutting Wave down. Like so many petitions, it didn’t help (obviously), but if a mediocre implementation got tens of thousands of passionate fans, what could a good implementation do?
I’d say the single most important lesson to take away here, for a technology project at least, is that interoperability is key.It's a really useful article with many practical applications (well, for me at least...)
Source: Jamey Sharp
Does the world need interactive emails?
I’m on the fence on this as, on the one hand, email is an absolute bedrock of the internet, a common federated standard that we can rely upon independent of technological factionalism. On the other hand, so long as it’s built into a standard others can adopt, it could be pretty cool.
The author of this article really doesn’t like Google’s idea of extending AMP (Accelerated Mobile Pages) to the inbox:
See, email belongs to a special class. Nobody really likes it, but it’s the way nobody really likes sidewalks, or electrical outlets, or forks. It not that there’s something wrong with them. It’s that they’re mature, useful items that do exactly what they need to do. They’ve transcended the world of likes and dislikes.Fair enough, but as a total convert to Google's 'Inbox' app both on the web and on mobile, I don't think we can stop innovation in this area:
Emails are static because messages are meant to be static. The entire concept of communication via the internet is based around the telegraphic model of exchanging one-way packets with static payloads, the way the entire concept of a fork is based around piercing a piece of food and allowing friction to hold it in place during transit.Are messages 'meant to be static'? I'm not so sure. Books were 'meant to' be paper-based until ebooks came along, and now there's all kinds of things we can do with ebooks that we can't do with their dead-tree equivalents.
Why do this? Are we running out of tabs? Were people complaining that clicking “yes” on an RSVP email took them to the invitation site? Were they asking to have a video chat window open inside the email with the link? No. No one cares. No one is being inconvenienced by this aspect of email (inbox overload is a different problem), and no one will gain anything by changing it.Although it's an entertaining read, if 'why do this?' is the only argument the author, Devin Coldewey, has got against an attempted innovation in this space, then my answer would be why not? Although Coldewey points to the shutdown of Google Reader as an example of Google 'forcing' everyone to move to algorithmic news feeds, I'm not sure things are, and were, as simple as that.
It sounds a little simplistic to say so, but people either like and value something and therefore use it, or they don’t. We who like and uphold standards need to remember that, instead of thinking about what people and organisations should and shouldn’t do.
Source: TechCrunch
Does the world need interactive emails?
I’m on the fence on this as, on the one hand, email is an absolute bedrock of the internet, a common federated standard that we can rely upon independent of technological factionalism. On the other hand, so long as it’s built into a standard others can adopt, it could be pretty cool.
The author of this article really doesn’t like Google’s idea of extending AMP (Accelerated Mobile Pages) to the inbox:
See, email belongs to a special class. Nobody really likes it, but it’s the way nobody really likes sidewalks, or electrical outlets, or forks. It not that there’s something wrong with them. It’s that they’re mature, useful items that do exactly what they need to do. They’ve transcended the world of likes and dislikes.Fair enough, but as a total convert to Google's 'Inbox' app both on the web and on mobile, I don't think we can stop innovation in this area:
Emails are static because messages are meant to be static. The entire concept of communication via the internet is based around the telegraphic model of exchanging one-way packets with static payloads, the way the entire concept of a fork is based around piercing a piece of food and allowing friction to hold it in place during transit.Are messages 'meant to be static'? I'm not so sure. Books were 'meant to' be paper-based until ebooks came along, and now there's all kinds of things we can do with ebooks that we can't do with their dead-tree equivalents.
Why do this? Are we running out of tabs? Were people complaining that clicking “yes” on an RSVP email took them to the invitation site? Were they asking to have a video chat window open inside the email with the link? No. No one cares. No one is being inconvenienced by this aspect of email (inbox overload is a different problem), and no one will gain anything by changing it.Although it's an entertaining read, if 'why do this?' is the only argument the author, Devin Coldewey, has got against an attempted innovation in this space, then my answer would be why not? Although Coldewey points to the shutdown of Google Reader as an example of Google 'forcing' everyone to move to algorithmic news feeds, I'm not sure things are, and were, as simple as that.
It sounds a little simplistic to say so, but people either like and value something and therefore use it, or they don’t. We who like and uphold standards need to remember that, instead of thinking about what people and organisations should and shouldn’t do.
Source: TechCrunch