4 ms·
All kidding aside, Yo's use case is real. We just typically call it a ping. But implicit in a ping is a response. I assume that typical use of Yo also involves
by scott_s 12y ago
All kidding aside, Yo's use case is real. We just typically call it a ping. But implicit in a ping is a response. I assume that typical use of Yo also involves a response. So, someone please do the right thing and implement a "Ping" app which, upon receiving a ping, gives the user an explicit option to respond with "ACK".
- cliveowen 12y agoFrankly I don't get all the hate. I remember being in middle school and ringing my friends just once and wait for them to ring back, it was a common thing to do. This is the modern version, nothing more.
- pessimizer 12y agoping -> pong REQ -> ACK
- fookyong 12y agouse case is real but there's no business model behind it.
- krapp 12y agoThat doesn't make it a million dollar idea, though. I mean... ok, yes literally it does in Yo's case but... never mind.
- jarman 12y agoThis use case is covered by any instant messaging application.
- scott_s 12y agoIt is, but it's slower. You typically have to say something, and even typing "yo" takes more effort than using an app specialized for it - and when all of human language is available, people often aren't comfortable just saying "yo". Instead they may feel compelled to type out "Are you available now?" Using an app makes it okay to just send one bit of information. It can be done in two presses: one to open the app, one to ping the person. Please note I am not arguing that Yo is worth the money invested in them. I do, however, think that many of the comments went too far in the other direction to say the idea has no utility.
- coldtea 12y ago>All kidding aside, Yo's use case is real. We just typically call it a ping. And we can do it with any IM app, or even better with SMS or Messages without necessitating the other user download any BS app for that.