Talko
talko.com
talko.com
Communications applications have to be extremely hard to pull off successfully, and God bless Ozzie for trying again.
I'm tempted to spout off on how one would do this thing "right", but I think that would make me the astronaut pot calling the architect kettle black.
“Nobody cared then and nobody cares now, because synchronizing files is just not a killer application. I'm sorry. It seems like it should be. But it's not.”
Joel assumes the reason why synchronization apps didn't succeed was because there was no market, whereas the success of Dropbox proved the market was there alright, it just waited for the right app at the right time.
I've needed file synchronization for my whole professional life, which started in 1991. At first there was no Internet; then there was Internet but you couldn't connect to it at work (imagine that!) and the rate at home was so slow it wouldn't have made any sense to try to exchange files over the network (even when most Excel files weighted 20k).
I used floppies, and Zip discs (remember those?) and removable hard drives, with bizarre synchronization and copying applications that never worked properly and with which you could very easily erase your own files if used in the wrong way.
The day I found Dropbox was like the Second Coming. It was the day I stopped worrying.
I very much disagree with Joel about architecture astronauts; contrary to what we hear sometimes, being early is not the same as being wrong.
> The people? They love twitter. And flickr and delicious and picasa and tripit and ebay and a million other fun things
I would trade a million Twitters for one Dropbox, and I bet I'm not alone. Dropbox we need; Twitter? not so much.
People were using file syncing for asynchronous collaborative editing. File syncing is not such a big deal now that we have synchronous collaborative editors.
With less double negatives: File syncing has actually turned out to be a pretty big thing, it just took (and this might be a bad list, but off the top of my head) 1. mobile adoption, 2. higher avg bandwidth and 3. someone getting it right. GDrive/Evernote/… does not negate that there is a demand for Dropbox.
If I had the resources this is something I'd try to fix. It's 2014 for crying out loud. Live Mesh got me excited at the time, but it just never went as far as it needed to.
Heck, I'm up and working at 4am today because of an AA and his stupid "elegant" data design that is "set in stone" that requires me to provide reams of documentation. I have to make up for the fact that my data is wholly incomprehensible without all kinds of independent documentation. This is all work the AA should have done himself, but instead all he shares are these idyllic, sophomoric examples that NEVER appear in the real world.
It's rich that the system is thought to be "elegant" because one major aspect is simple (there are only something like 8 fundamental data types in the file format to describe the whole system). Elegant? No, perhaps "convoluted" describes it better, maybe "rambling". Data files tend to be veeeery tall and veeeery skinny. Sigh.
So I'm working up to a huge real-world demo and I'm looking forward to canvasing the team in order to create a crisis. "Looking at this realistic example and seeing how much work it took me to get here, what are your impressions of the file format?"
Play a movie on your laptop, resume on your device when you leave (given there is an app for it)
The future is gonna be AWESOME.
Come on, that's how to have SUPER ADVANCED technology.
While the UI for Talko might be slick, there are already very similar and competitive offerings to Talko that operate on multiple platforms (e.g. Voxer) that have failed to take any market share the way Talko apparently hopes to.
If they're going to be successful, it will boil down to marketing more than anything.
Talko is arguably a better interface than most professionals use for many aspects of communications, so they have at least a reasonable chance of success.
I'll chuck it in as an appendix to the spec. Not that anyone will ever use it! I'll have to limit it to 160 characters though because I've only got 140 bytes to play with.
It's not like you can write anything meaningful with 160 chars anyway! When the hardware gets better we'll write a proper text messaging implementation. Lol!
I'd suggest the opposite - that's it's slow, unclear and probably the worst form of digital communication. There's no good log, it's not silent, you can't link to other information (or copy it) and it requires one person to stop talking before another can start.
This all aside, iOS 8 now let's you send voice messages in the default messages app - seems like this company has no market?
Converting voice to text solves a lot of these problems, but this app doesn't do that.
By digital I meant communicating with some sort of digital device and not face to face or through a letter.
From the first block:
Amazing things can happen when we talk with each other. Thoughts are shared, ideas formed and problems solved. Talko is the best way to use your voice to get things done.
The first sentence doesn't bring me any information, it's just a bland statement. The second is an expansion of the first. The third says this Talko thing is a way to do things with your voice.
I felt like loo¥sing my time reading nonsense, when I could be learning about a new app and see demos of cool features.
Granted, that was before FaceTime audio and the audio features of iMessage, but at the time I was basically ready to bury everything on my iPhone's dock and replace it with this as soon as it launched.
It has a ton of really slick touches that I think make it a really compelling app, well beyond the sum of it's core features.
- Text, check.
- Pictures and videos, check.
- Group messaging, check.
- Voice messaging, check.
It sounds like they recreated the iMessage core features, other than the ability to fall back to SMS for text. I wonder about privacy protection. Maybe there are some other bells and whistles on top?
iMessage doesn't have that.
Plus convenient and easy?
Is that right?
First impression is it's a nice, professional and polished application but it's an application that makes noise. Which means (on my iPhone):
* When I'm listening to music with my headphones on and some communication comes in from this app, it's going to be via voice and my music will fade out.
* When I open the app it's going to initialise the sound device even though it doesn't need to make sound just yet and my music will fade out just by opening the app. (Not guaranteed: a lot of apps do this, this one could too.)
* When this app starts playing instead of my music it's going to confuse my car's entertainment system and my music won't start again. (This problem is specific to my car.)
Basically this app is going to be annoying in ways that iMessage and email are not.
And actually, I like the idea.
Sometimes I find email and SMS a chore, but would love to leave my partner a 5 second "Hey I'm picking up milk, do you need anything else?" message that was auto-transcribed, and if I were on the tube (unavailable) she could leave a message for me "Yeah, some of those star-shaped veg, you know the ones next to the beans down the end of the second aisle".
She'd never have typed that into an SMS, and I probably would've just winged trying to think if there was anything she needed.
Metropolis transportation and living makes communication broken and fractured. Real-time mobile communication works only when both people are online... so a near real-time thing that overcomes the flaws of mobile coverage in cityscapes and their transport (cycling, underground metro systems, etc) and still retain a personal touch would be great.
I really think he hit the nail on the head with his memo when leaving MSFT...
Stopped reading after this.
That it failed to really adapt to a changing technological landscape and failed to meet user expectations is more an indictment of the management at Lotus/IBM than an indictment of the initial creator.