Tag Archives: rim

mobile

Last minute offer: attend BlackBerry Jam Europe in Amsterdam for half price or even free

At the end of January RIM is launching BlackBerry 10 in a now-or-never moment for the company. The new smartphone, based on the QNX embedded operating system, has distinctive features that just might win it a foothold in a crowded market dominated by Apple iOS and Google Android.

image

If you are developing for BlackBerry or thinking of doing so, it is worth attending one of RIMs developer events, and coming up in a couple of weeks is BlackBerry Jam Europe, which I imagine will be buzzing thanks to the launch of new devices. The event is in Amsterdam and runs on 5th-6th February.

The normal cost for new attendees is €300 but if you use the following code you can register for half price:

DJEGYX

This is limited to 20 registrations so be quick! I am not sure if it also works on the alumni registration offer price but it is worth a try.

If even that is a stretch, we also have a pair of free passes to give away. Email me tim (at) itwriting . com today 23 Jan with a paragraph on “Why bother with BlackBerry” and the best entry gets the code at the end of today. Only condition is that you give permission to have your comments posted here.

google, microsoft, professional, software development, windows

Mobile: Windows Phone appeal growing, iOS and Android secure say Titanium developers

Appcelerator and IDC have released their latest mobile developer report, in which nearly 3,000 users of the cross-platform development tool Titanium report on their views and intentions.

These reports are always interesting but experience suggests that they are poor predictors. A year ago, the Q4 2011 report told us:

Amazon’s new Kindle Fire ignites developer interest. When surveyed among 15 Android tablets, the lowcost, content-rich eReader was second only to the Samsung Galaxy Tab globally in developer interest. A regional breakdown shows Amazon edging Samsung in North America for the top slot. At 49% very interested in North America, the Kindle Fire is just 4 points less than interest in the iPad (53%) prior to its launch in April 2010.

Now, the Q4 2012 report says:

Amazon’s Kindle continues to struggle for developers’ interest. With less than 22% of mobile application developers “very interested” in building mobile apps for the device, the Kindle just barely breaks into developers’ top 10 app targets.

This is one example; a glance back through previous editions shows plenty of others, showing that developers struggle as much as the rest of us when it comes to guessing the value of future markets.

The report is still useful as a snapshot of how things look now, for cross-platform mobile developers. One question which is always asked, and therefore can be compared easily from one report to another, is the proportion of developers who are “very interested” in developing for each platform.

image

The top 5 contenders here are relatively stable, with Apple iOS top (iPhone and iPad), Android next (phone and tablet), and HTML5 Mobile Web also strong at about 65%.

The lower ranges are more interesting, as developers change their minds about prospects for the minority players. Windows Phone dived to around 22% in August 2012 but grew strongly to 36% in this report. Windows tablets, which we should probably take to mean the new Windows 8 app platform, is about the same. BlackBerry has declined from over 40% in March 2010 to 9% today, though I would suggest this will inevitably increase in the next report which will be after the launch of BlackBerry 10.

What else is interesting? One thing is Apple “fragmentation”. The problem here is that Apple iOS now has six screen sizes, once you add iPad mini and iPhone and iPad with or without high-res Retina displays. This gives me pause for thought. The challenge of mobile apps is now closer to that of desktop apps, where you do not know what display will be used or how users will choose to  size the application window. Intelligent layout and scaling is key.

Apple is also increasingly awkward to work with:

More generally, 90% of developers believe that Apple has become more difficult, or about the same, to deal with over the past three years when it comes to application
submission, fragmentation, and monetization.

Part of the report concerns Microsoft Surface. This focus is puzzling, in that it is the Windows 8 app platform which really matters, rather than Surface itself. Another oddity is the questions put, with no option to say “Surface is great”. The most positive option was:

It is a nice piece of hardware, but Windows 8 needs a lot more than that to be successful

A rather obvious statement which apparently won the agreement of 36% of developers.

The report gets even sillier when it comes to market disruption:

The top three companies that developers perceive to be ripe for disruption are a veritable who’s-who of the biggest tech darlings

say Appcelerator and IDC. It is true; but the figures are tiny:

Microsoft (8% of respondents), Google (7% of respondents), and Facebook (7% of respondents).

In other words, over 90% of developers believe these three companies are not likely to be disrupted soon; a figure that strikes me as conservative, especially for Microsoft.

More impressive is that over 60% of developers believe Facebook will lose out in future to a mobile-first social startup. This was also true last time round; 66% in Q3 2012 and 62% in Q4 2012.

The length of time it took Facebook to release just a single native iOS app, coupled with the fact that a corresponding native Android app is still MIA, has proven that the company does not yet have a viable cross-platform mobile strategy.

say Appcelerator and IDC. A fair point; but Facebook’s primary asset is its network of relationships rather than its software and it is not easy to disrupt. I would also guess that disruption is more likely to come from Google as it promotes Google+ and builds it more aggressively, perhaps, into Android, along with apps for iOS and other platforms as needed, than from a startup. But like the developers in this survey, I am guessing.

mobile, rim, software development

RIM BlackBerry 10 SDK is now gold

 

BlackBerry 10 developers can now download the release version of the various SDKs.

 

image

There are three primary SDKs: native C/C++, Cascades which includes a C++ app and user interface framework, and WebWorks for HTML5 and JavaScript.

If that is not enough, there is also an Adobe AIR SDK, and a Java SDK which is compatible with the Android Runtime.

RIM has made a huge effort to attract developers to its new platform, though how it will fare versus iOS, Android, and a somewhat reinvigorated Windows Phone is open to speculation.

mobile, professional, rim, software development

BlackBerry 10: key dates for developers announced, $10,000 incentive dangled

RIM has announced key dates for developers in the run up to launch on January 30 2013.

The schedule looks like this:

  • November 29: SDK update
  • December 11: Gold SDK available
  • January 21: Deadline for app submission to qualify for the $10,000 giveaway
  • January 30: BlackBerry 10 Launch

Following the release of Microsoft’s Windows Phone 8 this month, RIM’s BlackBerry 10 is next up in the category of smartphone platforms trying not to drown in the Android and iOS tide (more Android than iOS of late).

RIM’s strategy includes an element of “if you can’t beat ‘em, buy ‘em”. The company is offering a $10,000 guarantee to developers who achieve at least $1000 revenue from their BlackBerry 10 app in the first year.

image

There are terms of conditions, of course, including the performance, design, security and usefulness of the app.

It will be fascinating to see if RIM is successful in this attempt to fill its store at launch with high quality apps – something Microsoft failed to do for the Windows 8 App Store.

The offer is a no-brainer for developers who already intended to make a commercial app for BlackBerry 10. For others it is a nice incentive but perhaps not the easy money that it first appears, presuming no cheating of course. The majority of apps do not achieve even $1000 revenue. Creating an app that is good enough to do so, without that costing so much that the $10,000 loses its significance, is not trivial.

mobile, software development

RIM hints at move to license BlackBerry 10 OS to third parties

RIM chief Thorsten Heins says in an interview that his company may license the forthcoming BlackBerry 10 mobile operating system to third parties. Here is the key quote:

We don’t have the economy of scale to compete against the guys who crank out 60 handsets a year. We have to differentiate and have a focused platform. To deliver BB10 we may need to look at licensing it to someone who can do this at a way better cost proposition than I can do it. There’s different options we could do that we’re currently investigating.

He goes on to talk about:

… us building a reference system, and then basically licensing that reference design, have others build the hardware around it – either it’s a BlackBerry or it’s something else being built on the BlackBerry platform

The big question: would the likes of Samsung and Sony leap to manufacture BlackBerry OS smartphones when they can offer Android for free?

A more nuanced question: even if OEMs were to license BlackBerry OS, to what extent would they really get behind it, as opposed to cranking out a few devices to see how they went? The latter is what happened to Windows Phone 7, with the exception of Nokia late in the day.

Samsung manufactures Windows Phone 7 devices, but you would hardly know it, since it is the Android-based Galaxy range that gets all its attention.

Another problem for RIM is negotiating the tricky waters of both manufacturing devices and licensing the OS to others. Apple did not enjoy having third-party manufacturers like Power Computing, Radius and Motorola release Mac clones. Here is what Walter Isaacson writes in his biography of Steve Jobs:

Apple got an $80 fee for each computer sold, but instead of expanding the market, the cloners cannibalized the sales of Apple’s own high-end computers on which it made up to $500 in profit.

Microsoft is now coming at this from the opposite end, going into hardware manufacturing with the Surface, which is another interesting experiment.

Still, listen carefully to what Heins is saying. “We don’t have the economy of scale to compete against the guys who crank out 60 handsets a year.” It is not just a matter of coming up with a fantastic mobile operating system or even a fantastic device; it is all about ecosystem, as Nokia boss Stephen Elop stated 18 months ago. RIM’s ecosystem is in decline, and the company will explore every avenue in trying to turn that around.

development, mobile, professional, software development

BlackBerry 10: QNX multitasking goodness

2 Comments

I attended the London BlackBerry Jam, one of around 500 developers (the event was sold out) who showed up to learn about developing for Blackberry 10 and in the hope of snagging a prototype of RIM’s next smartphone, the BlackBerry 10 Dev Alpha. The event is part of a tour of 26 cities worldwide. I also spoke to Vivek Bhardwaj, Head of Software Portfolio EMEA for RIM. Does BlackBerry 10 have what it takes to  compete against Apple iPhone and Google Android?

A few quick observations. The event was split into native and web tracks, with the native track focusing on  C/C++ development and the Cascades UI framework, and the web track covering WebWorks, the HTML 5 developer tools which you can use to target mobiles as far back as BlackBerry 5, or to create apps that share code between BlackBerry and other mobile platforms.

There was also a tour of various mobile JavaScript libraries. One that caught my attention was Zepto.js, which implements most of the jQuery API in just 8.4k of compressed code, around 25% of the size of jQuery. The trade-off, aside from some missing features, is lack of support for Internet Explorer, though support for IE 10 is under consideration. Thought-provoking: the price of legacy platforms?

It turned out that the device Bhardwaj was holding, though pretty much the same hardware as the Dev Alpha giveaway, was more revealing as a glimpse of the next-generation BlackBerry. The Dev Alpha, which has an impressive 1280 x 768 screen, comes with no applications other than the web browser and its user interface is pretty much that of the PlayBook. Bhardwaj’s demo device on the other hand is a complete early version of BlackBerry 10 though there were parts that he would not demonstrate. I went to compose an email and he said, “we are not ready to show that yet.”

image

So what is distinctive about BlackBerry 10? One of its key features is multitasking, thanks to the processor scheduling capabilities of QNX, the embedded operating system which underlies both PlayBook and BlackBerry 10. According to Bhardwaj, this enables up to 8 apps to run at once. “Applications all run simultaneously. We don’t need to pause them,” he said. “It’s much more about flow.”

Although apps do run full screen, you can take advantage of the multitasking by “peeking” at a background app. This means holding your finger towards the corner of an app and dragging it left to see a little of what is underneath. In the pic below this is another image.

image

Talking to developers at the event I picked up considerable enthusiasm for BlackBerry 10, though compatibility is a headache. If your customer asks you to support all versions of BlackBerry back to the 5.0 series, you are stuck with WebWorks and the pre-WebKit browser in 5.0. If you can convince your customer to forget 5.0, then you can develop for WebKit. If you want to use Cascades then you are restricted to PlayBook and BlackBerry 10.

BlackBerry 10 also supports Adobe AIR, for Flash-based apps, and an Android runtime for repackaged Android apps.

The prototype BlackBerry 10 phone looks good, but as a brand new platform is it sufficiently exciting to revive RIM’s fortunes? “I don’t believe that in a trillion-dollar plus industry there can only be two players. I think there is more than enough space for four or five platforms. It’s very short-sighted if we think there can only be three ecosystems,” said Bhardwaj.  

adobe, mobile, software development

On BlackBerry 10, Cascades UI and Adobe AIR

I spoke to Jeff Lejeune, RIM’s Advanced User Interface Director, here at BlackBerry DevCon Europe in Amsterdam.

He is part of the team responsible for the Cascades UI, a native code UI framework for the forthcoming BlackBerry 10 OS. One of the things he told me is that the Cascades name is actually being used for parts of the API beyond the user interface. It is a major part of the new operating system.

I had not appreciated until today the extent of the likely difference between BlackBerry 10 and the current Tablet OS 1.0 or Playbook OS 2.0. Since the PlayBook OS is already based on QNX, I had assumed that BlackBerry 10 would be an incremental update rather than a radical new direction.

Certainly there is less difference between PlayBook OS 2.0 and BlackBerry 10 then there is between BlackBerry 7.0 and the PlayBook OS, so my assumption was not completely wrong. That said, the introduction of the Cascades UI acquired with The Astonishing Tribe is a major change. Lejune told me that Cascades UI will be in effect the native UI of BlackBerry 10, and the built-in apps will use it.

The first version of the PlayBook uses both native code and Adobe AIR for its built-in apps.

RIM has given full backing to Adobe AIR at this event, presenting it as one of the supported development platforms and saying that it will support AIR for as long as Adobe does and maybe even longer. Even so, it would be fair to say that RIM is moving away from AIR and towards native code and Cascades UI in BlackBerry 10.

Further, Adobe itself has changed direction since the launch of the PlayBook last year. Adobe has made it clear that while Flash, Flex and AIR are still important, its strategic direction is HTML 5 when it comes to development platforms. Some aspects of Flex, the code-based approach to AIR authoring, are being wound down, including the visual designer in Flash Builder.

My sense therefore is that AIR is not the best choice if you are considering how to develop for BlackBerry 10 – and BlackBerry 10 is the future of RIM’s platform. The primary choice should be between Cascades UI, for best performance and integration, or WebWorks (PhoneGap), for development in HTML and JavaScript and cross-platform code.

apple, mobile, smartphones, tablets

What is in BlackBerry PlayBook OS 2.0: new universal inbox and remote control

Here at BlackBerry Devcon Europe attendees were shown the key features of PlayBook 2.0, an update for the RIM tablet that will run on the existing hardware.

Aside from new runtimes for developers and some usability tweaks, the main changes users will notice are a new universal inbox and PIM (Personal Information Manager), and deeper integration between the PlayBook and BlackBerry smartphones.

The PlayBook 2.0 PIM offers a single inbox for Facebook, LinkedIn and Twitter as well as email.

image

The PIM includes an embedded web browser so that you can view HTML messages without leaving the application.

The application also covers calendar and contacts.

image

If you look in detail at a meeting, you can see the other attendees, presuming that the information is available.

image

One of the aims is to aggregate information drawn from social networks and from the internet. It is a compelling idea, and one that Microsoft has also used. For example, when you view an email the Outlook Social Connector automatically looks up status messages from FaceBook and LinkedIn from the author. Windows Phone also aggregates information from multiple social networks in its People hub.

RIM talked about adding web information. We were given the example of getting an email from someone and viewing recent press releases from their company within the PlayBook 2.0 PIM. If this is well implemented, it does make sense, giving you useful background without the need of a manual web search. A contact record is no longer just name, address and company, but a portal into that person’s story and current activity.

The other big new feature in PlayBook 2.0 is remote control. You can use your BlackBerry SmartPhone as a controller and input device for the PlayBook.

What is the point of this? A good question, to which the most obvious answer is that you can use the physical keypad on a BlackBerry to type on the PlayBook. This drew applause when demonstrated.

I asked for other use cases on Twitter. The main other suggestion was using a BlackBerry as a remote when your PlayBook is plugged into a screen as a media player or presenter.

The concept goes beyond this though. Here is new CEO Thorsten Heins speaking in the keynote:

Just take this idea a step further. Think about BlackBerry 10 being a platform, for mobile computing, for smartphones, so it really shows the deep integration of the BlackBerry platform. Think about having your PlayBook somewhere on your desk at your home, and you can control everything just from your BlackBerry, I think that is fantastic

Incidentally, RIM’s operating system naming is confusing. This is how it goes. BlackBerry OS up to and including 7.0 is the old smartphone OS that is being phased out. The new OS is based on QNX and first seen in the PlayBook, which runs Tablet OS 1.0. Version 2.0 of this OS, due out later this month with the features mentioned above, is called PlayBook OS 2.0.

BlackBerry 10 is the next iteration of this QNX-based OS and will run on SmartPhones as well as on the PlayBook. BlackBerry 10 is expected later in 2012, probably towards the end of the year.

RIM’s future depends on wide acceptance of BlackBerry 10. The uncomfortable question: how many mobile operating systems can succeed? It seems that Apple iOS and Google Android are well established, but the future prospects of new entrants such as BlackBerry 10 and Windows 8 is open to speculation.

Update: I visited the exhibition here and spent some time hands-on with the version of the PIM that is installed on the PlayBook devices. It is disappointing, though bear in mind that it is not, I was told, the final version (though if the final version is coming this month you would have thought it is not far off).

Some key points:

  • The embedded HTML rendering in the email client is just for the message itself. If you tap a link, it takes you into the separate web browser app.
  • In order to get social network status updates from the author of an email message, you have to be logged into that social network and the author must already be one of your “friends”, or so I was told. I hope this is incorrect, as it seems largely to defeat the purpose of this kind of integration. Outlook’s social connector retrieves status updates from anyone irrespective of whether you are logged into that network or have them on your friends list.
  • I asked about SharePoint integration and received the vaguest of answers. A SharePoint app is in preparation but there is no word on when it might appear, and it may be dependent on some sort of Microsoft input.
  • There is no official cloud storage service from RIM. You can use third-party services like Dropbox. Enterprises are expected to use internal file shares, via VPN if necessary.

It seems to me that RIM is in danger of missing an important market for PlayBook here. Many RIM customers use Microsoft’s platform because of the link with Exchange. A tablet with excellent support for SharePoint and Office 365 would have obvious value, and Microsoft can be expected to tap into this with Windows 8. BlackBerry could get there first with PlayBook but it looks like this will not be the case.

apple, mobile, smartphones, tablets

What will it take to make RIM’s Playbook sell?

I am at RIM’s Blackberry DevCon in Amsterdam (where it is so cold that the canals have frozen). Attendees have been given a free Blackberry Playbook, the neat 7” tablet running an operating system based on QNX, acquired by RIM in 2010.

image

The Playbook was launched in spring 2011, and sales have disappointed. Exact numbers are hard to find; the Guardian estimated that RIM ordered 2.5m devices, while Crackberry.com says 5m. How many sold? In the three reported quarters, RIM said 500,000, 200,000 and 150,000 were shipped. Prices have been falling, naturally, but it seems that there are plenty left.

Nevertheless, this is an attractive device. The operating system is smooth and the size is convenient. Why has it failed?

One factor is that the device is designed as a companion to a Blackberry smartphone. Email does not work unless you have a Blackberry, or can get by with a web browser client. RIM thereby reduced the market to existing Blackberry owners, a mistake which should be rectified when version 2.0 of the operating system is released – expected later this month.

The second problem is the the extent to which Apple owns the tablet market. When you buy an iPad you know you are buying into a strong ecosystem and that every app vendor has to support it. That is not the case with the Playbook, making it a riskier choice. RIM’s fix is to introduce support for Android apps, though there are a few caveats here. Perhaps the biggest is this: if you want to run Android apps, why not just get an Android tablet and avoid any compromises?

The Playbook is a delightful device. The big question – for RIM and other new entrants into the tablet market – is what will make it sell, other than pricing it below cost?

Amazon found an answer for its Kindle Fire: low price, Kindle brand making it an e-book reader as well as a tablet, and a business model based on its retail business. Amazon can sell the device at a loss and still make a profit.

It is not yet clear to me what RIM’s answer can be. The most obvious one is to make it truly compelling for the large market of Blackberry smartphone users, but not if that means crippling it for everyone else as with the 1.0 release.

Another factor is that the device has to be nearly perfect. On the conference device, it took me 10 minutes to send a tweet. The reason was that the supplied twitter app is really a link to the twitter web site. That in itself is not so bad, but I found the soft keyboard unwilling to pop up reliably when twitter’s tweet authoring window was open. Making a correction was particularly frustrating. A small thing; but one or two frustrations like this are enough to make a good experience into a bad one.

Version 2.0 of the operating system does promise numerous improvements though, and watch this space for a detailed review as soon as I can get my hands on it.

adobe, java, professional, software development

RIM announces Java and Android runtimes for the Playbook, beta of native SDK

RIM has announced several new options for developing apps for its PlayBook tablet.

RIM will launch two optional “app players” that provide an application run-time environment for BlackBerry Java® apps and Android v2.3 apps. These new app players will allow users to download BlackBerry Java apps and Android apps from BlackBerry App World and run them on their BlackBerry PlayBook.

In addition, RIM will shortly release the native SDK for the BlackBerry PlayBook enabling C/C++ application development on the BlackBerry® Tablet OS. For game-specific developers, RIM is also announcing that it has gained support from two leading game development tooling companies, allowing developers to use the cross-platform game engines from Ideaworks Labs and Unity Technologies to bring their games to the BlackBerry PlayBook.

It sounds as if the Android runtime will not be perfectly compatible with real Android:

Developers currently building for the BlackBerry or Android platforms will be able to quickly and easily port their apps to run on the BlackBerry Tablet OS thanks to a high degree of API compatibility.

Nevertheless, this will be an attractive route for Android developers looking for a quick way to port to the Blackberry.

The native SDK is currently in “limited alpha release” but RIM is promising an open beta for this summer.

The BlackBerry Tablet OS NDK will allow developers to build high-performance, multi-threaded, native C/C++ applications with industry standard GNU toolchains. Developers can create advanced 2D and 3D applications and special effects by leveraging programmable shaders available in hardware-accelerated OpenGL ES 2.0.

The deal with Unity is important too. Unity is an increasingly popular toolkit for game development and adding the Blackberry to the list of supported platforms will boost its appeal. Ideaworks Labs makes the Airplay SDK, a cross-platform toolkit which already supports Apple iOS, Android, Symbian, Samsung Bada, HP webOS and Windows Mobile.

Note that the primary SDK for the Playbook has until now been Adobe AIR; and since the UI itself uses the Flash runtime this likely still makes sense for many applications.

RIM is doing a good job of opening up its platform. It is an interesting contrast to Microsoft’s “Silverlight, XNA or nothing” approach for Windows Phone.