Prototyping VRM Mobile Social, iPhone: Difference between revisions
m (Reverted edits by Hiphopalemi (Talk) to last version by Joe.andrieu) |
|
(One intermediate revision by one other user not shown) | |
(No difference)
|
Latest revision as of 06:44, 13 January 2010
Stuart- Prototyping a mobile VRM that leverages Social Network fabric
iPhone is a good conduit
Phone SMS Email 3.0 notification Bluetooth
Stuart says that we have all these ways to contact people
iPhone adds location
Adds time
Presence â and what Iâm doing
Things that recognize that âstate has changedâ
Relationships provide context regarding âWho are you?â
The questions revolve around access control
âWe have this thing in our pocket that provides all these things to us, but we have no controlâ¦
â¦on the other side, the people have no idea whatâs happening on this end.â
It doesnât have to do with calls necessarily, but when it âescalatesâ from a message
Rules for Pre-call Information
Recipient only knows phone number if the caller is not in the directory
The originator really has no control over what information is provided
Using the rideshare use case⦠thereâs an issue surrounding the Buddylist
Using Google Voice you can treat each caller differently â¦
Right now Google Voice gives you a âflavorâ of all the rules you can attach to incoming calls
Ribbit could be a platform for all of these services
Voice mail treatment on an iPhone is an issue because the iPhone voice mail store is on the device, not on a shared host
Comment â originator may want to indicate a different originating phone
Originator may also want to send a pre-call alert â IM/SMS (the Can you talkâ message)
Caveat â you will pile all kinds of capabilities for the power users â but other people wonât use it.
So you need to monitor and analyze all that behavior and deliver
You can establish groups.
Another way to look at it is that you can have my GrandCentral # and it is related to all the ways that I can be reached and will be associated
Need to talk about the difference between synchronous/asynchronous
Is it that important to do a synchronous conversation.
So basically it gets down to hooking up a system where the caller is in control
âIn a VRM world, the phone owner is in controlâ and how you get there is to take away the possibility of the caller to control the terms and conditions
This could be the origination vehicle
The systemic smarts are much more interesting than the granular control
Because the granular stuff should be automated.
You can trick this⦠just get a fictitious number and point it where you want
- Stuart has an idea for a Craigâs list for Twitter (called Twitmark) instead of a phone number and address you put a Twitter handle, but whatâs missing is the escalation to a phone number. The other thing thatâs missing is that you have to do an abbreviated link to (e.g. a Craigâs list ad)â¦
Another idea that was brought up is the Farley File⦠whereby you keep track of all the people that you meet.
The phone gets it backwards, inbound now might be able to relate it to a record in the phone infrastructure⦠But what if you have a âWhoâs this?â button to relate other stuff in the social graph and CRM space to figure out whoâs calling.
Observation â thereâs probably a latency issue. Unless you preload some set of most likely callers and their might be other premapping.
People can more accustomed to âpromiscuous messagingâ â that is basically ads⦠âI need xâ or âIâm selling Yâ then you can also use location awareness to figure out whoâs twittering nearbyâ¦
Observation â youâre social graph and list of people youâre in touch with
One of the premises for this discussion is that if VRM is going to work, it will be on a mobile device.
Observation â there are a lot of interesting initiatives underway and we have to figure out how they will bolt together.
Some compete Some could augment each other.
Weâre talking a lot about the requester time. And not how you find relevant providers ⦠So you need to know âhow sees thisâ?
A: in the twitter example⦠Daycare companies might have a âbot monitoring peopleâs requests, determining where the person is. They can send a direct message⦠And they may have their own filter
Narrowcast exchangesâ¦
Which Phil Wolff â calls âsearchâ
E.g Rent-a-Coder O-Desk E-lance
Where you have not a job offer but a short gig. So you craft a message
- Capability goes in seek of a need and vice versa***
Thereâs an aggregation function to be served.
If youâre looking specifically for a pair of tennis shoes specifically⦠Itâs not readily apparent exactly how you get to there from here.
Angieâs list + ribbit exposes the latency issue
Stuart is saying that â as things âescalate toward a transactionâ and Darius is wondering how you get there from here⦠Can you make this a âcheck boxâ item in their lsting that âfor an extra $2 to add a phone numberâ for the duration of the interest.
Phweet demonstrates that the identity layer can be set up independent of other services.
It will work anywhere and it is initiated on the basis of a text exchange. The contract is a URL for that exchange.
You probably have it in your head⦠Thatâs a feature, not a product.
How do you make a product How do you build usage.
Phil â Talked to an eBay employee lately⦠Asked why do you think eBay never embraced Skype⦠He said that eBayâs attachment to keeping the conversation controlled so that they couldnât be cut out of the equation, so they made it harder
As market makers they are also getting a percentage of the transaction so they just put up barriers.
Buy in depends on âwhat their stake isâ if you think the transaction will go on outside their walled garden, they wonât buy in .
E.g. you can architect this so that an assigned, ephemeral URL can be a revenue opportunity for Twitter. The Tweet controls how long the thing stays nailed up. You can do it on Twitter or Identica or anywhere. You can set up a VRM like relationship. And thatâs what makes it interesting
Closing⦠align VRM with the core metrics of each of the service providers.