Billions without Buzz
ericsink.com
ericsink.com
That being said, those same markets have never heard of Haskell, Rails, Erlang, Backbone and the latter, which could in fact drive real solutions for their problems. This is really (IMHO) where real economic value can be had, and the potential is in the trillions of dollars. I like patio's sentiment (not verbatim) of "99% of the businesses out there still don't have web solutions".
Far more of the world's wealth is flowing between companies than between consumers and companies; but those flows are only visible to those close to them. But every journalist is a consumer, so they are all "experts" on whatever the final consumer-facing products are. Hence, those products get the attention and we overestimate their importance.
[1] http://chester.id.au/2013/01/05/on-selling-to-consumers/
Not true - India has ~800+ million mobile subscribers and only ~100+ million of them currently have smartphones. So there is a huge market waiting to be tapped - although Apple may still be distressed as 90%+ of these 700 million potential customers are probably going to buy a sub-$100 smartphone made by the likes of Micromax and running Android...
As an example, Salesforce.com, the "standard" in SaaS CRM has a mobile app, but the majority of the time users are in front of a laptop or computer during the day. They may use the mobile app on the go, but people are not walking around our office using these apps - they're at their desks where they've got a keyboard.
This obviously varies by industry - I'm sure people can provide examples where it would make a big difference (thought of one: services businesses with a lot of remote/scheduled workers ala lawncare).
Cloud infrastructure has been disrupting both in the delivery of SaaS applications and lowering the cost of developing and delivering a service. I'm just not seeing mobile having the same level of impact. The fact that most mobile apps that support SaaS applications are thrown in with the service may show that they don't add huge value to overall revenue a SaaS company may see.
I agree that much of the enterprise focused work out there draws less attention today, but I expect that to change. As these businesses reinvent the way they run using mobile that's going to drive big changes to how most people do their jobs. That's also going to mean better ways of connecting consumers directly with organizations (the power of mobile goes beyond connect people to information and really lies in connecting people to each other).
As we see industries change the way they do business it'll be more apparent. With leaders like Sonic Automotive changing the car buying process with iPads in the hands of all sales people so that one person can find you a car, appraise the trade in, work the finances and sign the deal -- without bringing anyone else into the discussion -- that takes a lot of pain we all have felt out of the process.
Terrible example. Apple in fact has a very low P/E for this sector (it's 1/2 that of Google). Apple could have zero growth and remain highly profitable for years.
Sure they could. But Wall Street would punish their stock price anyway.
Not everything about the way AAPL fluctuates is rational. Maybe NOTHING about it is rational. :-)
But the concerns about Apple's ability to sustain its ridiculous growth ARE quite real. Their growth IS slowing.
as of today (numbers from yahoo finance):
tick p/e
amzn 506
fb 87.6
goog 30.25
csco 16.67
intc 16.55
hp 16.29
msft 15.83
appl 15.4
ibm 12.4
twtr n/a (<0)
(sorted descending)Databases. When you have 500 million users, you can't afford unique constraints and foreign keys in the db layer anymore.
Is he just saying that fully featured RMDBs don't have the performance to handle that scale? It seems like in some applications those checks will be necessary, and often the db will be the most efficient place for them. Not everything makes sense as nosql. Maybe I'm missing the point though.
But it's actually a little more complicated than I make it sound above. By removing things like unique constraints and foreign keys from the database layer, you also end up with a design that can much more easily scale out instead of up. Distributed database. Lots and lots of nodes. etc.
NoSQL databases have their place.
Traditional SQL databases do too.
Is that claiming that Foxconn has the largest (by size) manufacturing facility in the world? I would expect that the Boeing Everett Factory still claims that title by a long shot.
But sensors on everything in their supply chain are where the growth is. How many items per day does Walmart transport?
If I weren't trying to keep the wording of my blog entry so tight, I would have more clearly distinguished the following three cases:
(1) B2B apps that do not challenge our notion of scale like the B2C wave did. (stuff that doesn't need something like Couchbase)
(2) B2B apps that are of similar scale to the B2C wave (stuff that does need something like Couchbase)
(3) B2B apps that challenge our notion of scale in a whole new way (stuff that will disrupt Couchbase)
I was trying to say that:
(a) There will be a lot of case (1)
(b) There will also be plenty of case (2)
(c) I'm not sure we will see any of case (3) in this wave. We're probably not going to see much NEW disruption that didn't already happen in the B2C wave. And that's part of why there won't be a lot of buzz.
-- E