|
Katherine,
Great stuff!
The more I dig into Intent Casting the more complex it's becoming. The amount of data flowing around is enormous, let alone all the messaging (now I see why T.Rob is advocating a very lightweight notification/message scheme). Plus on top of this you have
to write yet even more apps to access all this data.
Wow – to me this is going to blow the consumers mind. Supporting all these apps, which invariably are free, is going to be really hard for the developers because they now have to pay for the API access that their customers are using. Guess we're going
to see even more advertising.
The VRM dependencies are now becoming very clear:
That's a tall ask. In fact just looking at companies in the VRM space (Thumbtack, and Singly, there's another one which is a reputation play) you can see that double digit millions are required to just host the backend infrastructure to tie this all together.
Thumbtack does an awesome job on mobile so you can just use a browser. However Singly is all about apps which is a different deal altogether.
Developers won't pay for APIs unless they can monetize their apps. As they have to support a minimum of two mobile platforms (Android and iPhone) that means they have to either give away the app for free and throw in advertising (there goes your data)
OR have a 'subscription' service that they can monetize.
Here's a question for you (and anybody else who can answer it). Here's Google's network effect which generates a ton of money. What does the VRM network effect look like? Anybody like to take a stab a diagramming it?
![]() Peter
_________________________Peter J. Cranstone CEO. 3PMobile Boulder,
CO USA
![]() Improving the Mobile Web Experience Cell:
720.663.1752
Web site: www.3pmobile.com
CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files or previous e-mail messages attached to it may contain information
that is confidential or legally privileged. Any unauthorized review, use, disclosure or distribution of such information is prohibited. If you are not the intended recipient, please notify the sender by telephone or return e-mail and delete the original transmission
and its attachments and destroy any copies thereof. Thank you.
From: Katherine Warman Kern <
">
>
Organization: COMRADITY Reply-To: " "> " < "> > Date: Wednesday, July 3, 2013 3:51 PM To: 'Doc Searls' < "> >, 'ProjectVRM list' < "> > Subject: RE: [projectvrm] Fwd: Introducing Singly Health Data Fabric Hmm. Started out as this:
http://lockerproject.org/ “A Locker is a container for personal data, which gives the owner the ability to control how it's protected and
shared. It retrieves and consolidates data from multiple sources, to create a single collection of the things you see and do online: the photos you take, the places you visit, the links you share, contact details for the people you communicate with, and much
more. It also provides flexible APIs for developers to build rich applications with access to all of this information.” But that last sentence, implying rich applications will access info and go in unforeseen directions with it, seems to have morphed into this: http://techcrunch.com/2012/12/10/singly-launches-app-fabric-platform-for-developers-to-speed-up-integrations-with-dozens-of-services/ “Singly offers to speed up the process of manually having to write code to authenticate users via third-party
services, pull in their friends list and other data (think photos, bios, etc.) from various social networks and other services, and then allow those users to share to social networks, as well.” Maybe that’s because the hitch is how to give consumers total control
and developers the freedom to build rich applications. Consumers may be willing to give developers that freedom
IF they get to decide who sees the “rich application” or know it is only published if they see it and “opt in”.
K- From: Doc Searls [
">mailto:
]
FYI. thoughts? hacks? Doc Begin forwarded message:
From:
Singly <
">
> Subject: Introducing Singly Health Data Fabric Date:
July 3, 2013 1:38:47 PM EDT To:
<
">
> Reply-To:
Singly <
">
>
|
Archive powered by MHonArc 2.6.19.