It continues, down another 2% today as Heins has not been fired nor have his eyes been exposed to daylight.
I say again: Open the Playbook, and by extension BB10, to GAPPS here and now.
All the claims of RIMM having a "vibrant" developer community and ecosystems are immaterial. Seriously. They're lies too, but even if they weren't lies (and they are) it doesn't matter.
Let me explain a few things. RIMM recently "fixed" the lack of an integrated email application for the Playbook. That's good. The bad is that it can't handle PGP -- that is, encrypted email -- at all. It does do a credible job of working with SSL-secured IMAP accounts, which is good. That it can't handle encrypted transport, however, makes it worthless to me and millions of others.
I, and many others, need encrypted transport and storage or I may as well have nothing when it comes to business email.
There would be a solution to this in that on the Android market there is an application called "K9 Mail" which works perfectly well and is also available on the Playbook store. It also handles IMAP properly. All good, right?
Nope; this "solution" is worthless.
Why? Because PGP support requires AGP as an add-on which is not in the Playbook store.
Therefore unless you have a rooted device if you need fully-encrypted email support on your Playbook you're stuffed and done.
You want to claim this is irrelevant? Go right ahead. I need this. I can't have it on the Playbook. That makes the Playbook a TOY instead of a TOOL for my use and makes all the claims that the Playbook is a "solid device" in the world where SECURE email matters to the user -- which is a hell of a lot of corporate users -- an abject LIE.
That's the beginning and end of it folks, and this is not the only place this problem happens on the Playbook. It happens in a lot of other areas too, and all of them have exactly the same outcome -- the device is worthless to people with that particular set of requirements.
This is why iPADs and Android tablets are winning and the Playbook is not only losing it is utterly irrelevant.
Other examples? I have apps for Android (and IOS) for my various brokerage accounts. None are available on the Playbook and inquiries to the companies involved have resulted in a "no plans" response.
BB10 is going to have the same problem on the new phones. And despite what people want to claim BB10's audience is not just the government and large-enterprise customer -- if that's all RIMM cares about the company is finished.
The customer base and intended audience has to include the small and medium enterprise where these capabilities matter. They matter a lot. They're missing. And RIMM must address this, and address it right now, because the company simply does not have 2+ years to get their **** together in this regard nor can it play the game of "if we build it they will come."
No they won't -- they didn't with the Playbook and they won't with BB10 either.
Bribing developers didn't work with the Playbook (remember, they GAVE THEM AWAY) and it won't work with BB10 either. The market has called "bull****!" on that strategy and it's right on the money -- RIMM has lost a literal 20% of its market value in the last three days and I argue it is precisely because RIMM did not address this issue head-on at the conference.
Folks the differences here between the Playbook and Android tablets in terms of quality of execution at the base OS level and the resulting power budget issues are massive.
Really, seriously massive.
I have both here -- a Playbook and the "newest and best" of the small 7" Tablets, the Galaxy 2 7.0. These are both tablets with 7" form factors and similar feature sets; the Galaxy runs the newest version of Android, ICS. Both are dual-core processor devices and have similar internal specs.
Side by side, both starting with a 100% charge, the Playbook while idle lasts a workweek with light use before the red light starts flashing at me, telling me I have to plug it in.
The Galaxy tab lost 30% of its charge in 10 hours overnight sitting in a sleeve while asleep with nothing running in the background -- no apps, no push email, nothing.
Now take both on a trip and tell me this doesn't matter. If you whip it out to use it at a customer site and it's dead it sure as hell does matter. And this is exactly the sort of massive advantage that I was talking about when it comes to QNX .vs. Android (and IOS.) Oh yeah, and the Playbook has HDMI too and the better browser (by far.)
QNX has provided RIMM with an outrageous power budget advantage -- which is exactly what I expected it to do. If you remember I've been pounding the table on this now since QNX was first acquired by the company. But it's only recently -- with quality hardware and the newest Android releases -- that we've been able to quantify that I'm right when it comes to the advantage that I had every reason to believe would be there. I've had my detractors on this, who claimed that the differences would be small to non-existent and that Android and IOS would be "just as good" or damn close.
The verdict is in: The advantage I expected to see is real. It exists. And it's huge, exactly as I predicted it would be from my more than two decades of experience in this field.
Tight code matters and power budget is the issue for portable devices. Period. The BB10 phones, unless RIMM screws them up, will have similar advantages over iPhones and Android devices. Samsung just stuck a 2100mah battery in its new Galaxy III device to try to get acceptable battery life out out of the power-wasting pig called "Android" (previous devices were around 1500mah; this is a BIG change!) Batteries cost money, size and mass and sticking bigger ones in the case to solve a software architecture problem is stupid, but it's all you got when you're stuck with code that looks like spaghetti -- and Android does (I've ported it -- I know exactly what it looks like internally.) The problem isn't just in the application code (Android) either; it's an architecture thing. General-purpose Unix kernels, of which Linux and IOS's Berkley base both are simply are not and will never be optimized for mobile, power-restricted devices where every milliwatt-hour matters. QNX was built to be tight and efficient from the start and it remains so. It came from a different philosophy where performance-per-watt-spent and hard real-time response were the "prime directives."
But none of that will sell a single unit if you can't do what you need to do with it. Better hardware and a better operating system is immaterial if there is no application support. And the premise that RIMM has on trying to monetize the "app store" -- the "ecosystem razors and blades" bull**** -- is a loser.
In the Android world the manufacturers have given up on this; Google has their app store but none of the other manufacturers try to make money on this aspect of things.
RIMM is trying to be Apple.
They have and will continue to fail in doing so.
RIMM has to focus on making the best hardware and best operating system that consumes the least power for the task performed, has the widest application base you can manage to get to run well on the device and provide the best security for the native environment.
RIMM can do all of those things right now. It has the best operating system with the best power management and the differences there are not small. It can easily build quality hardware. And it can solve the problem of not having the app you need to make the device work for you in your environment by opening the system to GAPPS right now.
That's the winning path available to RIMM -- the only winning path.
I repeat: RIMM either opens BB10 and the Playbook to GAPPS or they die, and I will continue to pound the table on a regular basis until Heins either pulls his head out of his ass, he is fired and the board replaces him with someone who has an IQ greater than his shoe size, the shareholders revolt, tar and feather the board and boil them in oil, replacing them with people who have a clue, or the stock price goes to zero and the company folds -- and that's exactly what's going to happen if RIMM does not move on this point in the immediate future.
Stop the stupid Heins. Stop Heins, RIMM. Throw the jackass CEO into the street and open the damn devices to GAPPS this afternoon -- and by doing so save your company.
Where We Are, Where We're Heading (2013) - The annual 2013 Ticker
The content on this site is provided without any warranty, express or implied. All opinions expressed on this site are those of the author and may contain errors or omissions.
NO MATERIAL HERE CONSTITUTES "INVESTMENT ADVICE" NOR IS IT A RECOMMENDATION TO BUY OR SELL ANY FINANCIAL INSTRUMENT, INCLUDING BUT NOT LIMITED TO STOCKS, OPTIONS, BONDS OR FUTURES.
The author may have a position in any company or security mentioned herein. Actions you undertake as a consequence of any analysis, opinion or advertisement on this site are your sole responsibility.
Looking for "The Best of Market Ticker"? Check out Ticker Classics.
Market charts, when present, used with permission of TD Ameritrade/ThinkOrSwim Inc. Neither TD Ameritrade or ThinkOrSwim have reviewed, approved or disapproved any content herein.
The Market Ticker content may be reproduced or excerpted online for non-commercial purposes provided full attribution is given and the original article source is linked to. Please contact Karl Denninger for reprint permission in other media or for commercial use.
Submissions or tips on matters of economic or political interest may be sent "over the transom" to The Editor at any time. To be considered for publication your submission must include full and correct contact information and be related to an economic or political matter of the day. All submissions become the property of The Market Ticker.