Life by Bits & Numbers

The next version of the BlackBerry Eclipse plugin will fix most of the annoying things about blackberry development.

Some of the most important things are:

1) No need to restart emulator for new build to be loaded to the emulator (Hallelujah!!!)

The new build should be just loaded onto the already started simulator, pretty much as on Android and iPhone.

2) Ability to add external libraries i.e. *.jar files to the project

This is actually pretty peculiar since RIM was pushing hard 3-d party (external library) integration as one of important concepts and obviously it would be very beneficial for the BlackBerry ecosystem but if you did not want to use JDE, there was pretty much no clean way to add external library. That is until the 1.1 plugin comes out from beta, or at least that what was promised at the New England BlackBerry developers meetup.

3) The BlackBerry plugin would follow the “Eclipse way”

The 1.1 plugin is very different from previous version. Instead of following the “JDE way” it will be much more the natural “Eclipse way”. This is both good and bad. This is very good for developers that have experience with Eclipse and just now start to develop for BlackBerry. This will however be somewhat painful for the seasoned developers who got used to the old plugin and will need to discover many things from scratch. (I personally felt quite lost with the new 1.1 plugin and decided to stick with the old one until 1.1 comes out of beta).

You can download the beta of 1.1 from here (you would need to have BlackBerry developer account which is free and can be obtained with simple sign up immediately)

During the Super App webcast Mike Kirkup covered many questions from the attendees. I have gathered many of those in the webcast summary. He did not get through all of the questions and promised to answer all of the questions on blackberry development forum. He did just that and here is the Q&A extracted:

[Q] The problem I found with a super app that was tightly integrated with the address book is that people were looking to see an icon and not something that was just part of the existing BlackBerry UI.

[A] A good point.  Many users will still expect a simple icon for the application whether only to provide information on how to leverage the application or how to manipulate settings.  Fixmo is a really good example of this point.

[Q] Is there a way for my app to get notified when new notifications are shown on the device?

[A] Unfortunately, no.  But this sounds like a great feature request you should log via the BlackBerry Issue Tracker.

[Q] Is there a way to include full camera control in the application?

[A] Yes.  Check out JSR 135 (MMAPI) for more information on how to include the camera field within your application including the ability to modify zoom and flash settings.

[Q] With the definition of a “Super App” being one that you cannot live without, can a game be a super app?

[A] Great question!  Yes, a game definitely can be a “Super App” or take on many of the characteristics of a Super App including being notification driven, contextual (even location based), integrated with other applications and so on.  It isn’t hard to imagine having a game that you love so much that you can’t live without it.

[Q] Can I make a Super App by developing a BlackBerry Widget?

[A] Yes, definitely.  One of the most important attributes of the our Widget technology is that you can fully integrate your Widget into all of the same APIs that are available to Java applications whether exposed already through Javascript APIs or through your ability to write Javascript to Java APIs.

[Q] Do you plan on setting up a program to certify applications as Super Apps?

[A] No, we do not currently have any plans for certifying applications as a Super App today.  The concept here is to help people really understand not only the capabilities of the BlackBerry platform but also the possibilities on better engaging your users.

[Q] We have developed a collaboration application which works on a “pull” basis.  How can we leverage push?

[A] Check out our newly launched Push Services page for more information on how you can start leveraging push in your application whether for the enterprise or consumers.

[Q] Is it possible to add a custom menu item in any third party application?

[A] Yes, although not in a granular fashion today.  As part of the ApplicationMenuItem API you can specify that you want your menu item included in all applications on the device but you do not get to pick which applications if you don’t want all apps.  Can you submit a feature request in the Developer Issue Tracker if you think this is a good use case.

[Q] Suppose the application flow is such that screen 1 pushes screen 2, screen 2 pushes screen 3 and from screen 3 the user needs to go to screen 1.  Should the application push screen 1 again or pop screens to get to screen1?

[A] You should definitely maintain the proper ordering of the screens on the stack for the user such that your application will automatically pop off the top screen on the stack when the user presses the escape key.  So, in this case, it depends on your ultimate goal of the screens.

[Q] This is a great presentation but it gives very little to seasoned developers.  Will you have additional presentations with more details and more code samples? (Editor: this, I think is actually my question slightly rephrased)

[A] Yes, definitely.  This is the introduction to the concept of Super Apps and you will see additional webinar presentations that go into substantially more detail on all of the key aspects of bringing Super Apps characteristics to your application.  The Big Ideas, Little Screens UI Webinar from Brian this month is a perfect example of more involved webinars.

[Q] What are the OS or device requirements for the Javascript examples provided?

[A] These are part of the new BlackBerry Widget technology and require v5.0 handheld software.

[Q] You mentioned the Super Apps website.  Where is that?

[A] www.blackberry.com/developers/superapps

He also promised to keep posting answers so see the original forum thread here for more information

Last night I have attended local New England BlackBerry developer meetup group. It was a great event with nice turnout of about 50 developers with special guest – Mike Kirkup – director of developer relations at RIM.

Mike is a great speaker and a great guy in general. BlackBerry developers are truly blessed with Mike in that sense. So much has been done to ease up on the hurdles of BlackBerry development recently that it is becoming cool to be BlackBerry developer once again.

The meetup was hosted by a local software development company – SoftArtisans. They develop SharePoint solutions for BlackBerry.

Mike was give the stage and he went over the BlackBerry super app concept which was similar to the BlackBerry super app concept webcast he gave recently but a little different of course with some stuff oriented more towards developers.

The highlight was of course the free panel Q&A session which was afterwards. Mike, as usual, did a very nice job answering the questions of the many developers who brought up interesting questions.

Upcoming Products

• BES Express (or BESX) which is the free, striped down version of the BES server. This will allow smaller businesses to put their employees on BESX without hesitation which originated from the costs of licensing associated with putting employees on BES.
• Upcoming WebKit browser which will be blazing fast and super blazing fast for JavaScript.
• There will be no iPad like device.

“No iPad, no BlackPad, BluePad, RedPad etc…”

• Advertising APIs. Right now RIM is conducting a closed beta with their partners and should be soon available to all independent developers. There is no cap on the volume, meaning pretty much anyone would be able to integrate advertising in their apps.
• Push APIs (well this is not an upcoming event actually, it went live today at 9am). Push API is available to everyone now and is free!
• App World 2.0 will soon be launched. The next version of the app world will support not only the PayPal but also the carrier and credit cards. The share of developers will most likely be different across all the optios and across the different network operators as well. PayPal option will remain 20/80% split with 80% going to the developers.
• In a few weeks the new Eclipse plugin for BlackBerry development version 1.1 should be released, which will address many issues existing in the older 1.0 browser. The official release of 1.1 which should go out of beta will be fully supporting 64 bit systems.

Upcoming Events

• Very soon we would have “fast simulator experience” so painful to many developers that when announced, it was followed by applause storm. So fast simulator experience means no more restarting the simulator to load the newly compiled version. (Yey!)
• More aggressive promotion of the App World. Mike mentioned that RIM intentionally kept the App World low profile for the first year letting the carriers figure out their distribution strategies.
• Super App competition. The super app competition will be carried out with a different prize distribution model than previously. RIM decided instead of rewarding a few leading application with big bonuses, reward more developers with moderate bonuses. Mike mentioned that they expect 3000-4000 apps submitted to the contest (both new and existing apps can be submitted) and if your app passes the first criteria of actually being a super app, then you are already entitled to something. Mike threw out “a free device” in the air but I guess it is not yet decided. They may go with a free device or maybe discounted developer conference or maybe we could choose. Let us know in the comments what you would prefer. The prizes will be handed out at BB Dev Con in San-Francisco at fall and the submission deadline will most likely be July 1-st but this is not confirmed yet.

The painful question of over the air (OTA) OS upgrade was raised and Mike said that carriers feel  fairly confident with pushing OTA OS update starting with OS 4.6 since 4.5 being the first OS where OTA OS was introduced had some issues and bugs. He mentioned that from carrier’s experience OTA updates have a very high conversion rate. In the 80%-s while even the through browser+USB update is less than 20% conversion rate. Until most of the devices are 4.6 and up and carriers are more aggressive pushing updates to the devices, we will be stuck with the need to support older devices as old as 4.2.1. Which leads us to further interesting figures:

Update

You can read additional notes summary at Chris Wong’s blog

You can download the Super Apps slides by Mike Kirkup which were presented at the meetup.

RIM has unveiled the new upcoming BlackBerry browser based on the new WebKit engine.

At the New England BlackBerry meetup, Mike Kirkup mentioned that they are doing some neat tricks with precompiling JavaScript through MDS which makes the JavaScript blazing fast. You can see it for yourself in the embedded video.

The new WebKit browser will be available in the next OS release but the upgrade will be limited on per device manner since WebKit browser is quite resource demanding.

Anyways, it’s great news and good job RIM!

As I already wrote, BlackBerry development is not a lot of fun.  Not only you basically can not develop in Linux and OS X (although there are some workarounds, it makes the process even more painful than it already is). But you will also have problems with 64 bit operating systems. RIM is in a position that they do not officially support 64 bit systems.

The main problem with 64 bit Windows 7 for me was that I can not close the simulator (or actually the “fledge” application that runs the simulators). There are 2 possible solutions to this problem:

1. Kill the task through task manager
2. The simulator should close if you are in debug mode and you disconnect the debug session

There is also another inconvenience which is caused by your cautiously guarding Windows system. It will warn you every time that (Oh my!) fledge will change something on your computer. You know – the standard User Control Account message. To avoid that message always popping up, you will have to adjust your setting in User Control Account panel. Hit “Windows” then just type UCA, you will get it. Adjust it to the minimum and you’r good to go.

It’s not a secret that Eclipse plugin is very buggy and although it has improved a lot over the time, the blackberry plugin still has a lot of issues and quirks. One of the problems that have been bugging me a lot was that sometimes the *.jdp file gets corrupted. This is the file where BB plugin for Eclipse saves most of the meta data for the project, including the files that are included in the project and consequently need to be compiled. So, many times I had problems with SVN meta data files corrupting this project, or sometimes perfectly legitimate *.java files that get stuck in the *.jdp file, but do not exist anymore. The result of the *.jdp file being corrupted is that your application does no longer get compiled and redeployed when you run it. And the worst part, Eclipse would not explicitly let you know about this. It would silently fail and not re-deploy the app. So unless this is the first time you run the application, or the changes you made are not visually obvious, you would not know about this. But this is completely separate issue. One of the many issues with BB Eclipse plugin already covered. Each time I have been struggling (sometimes for significant amount of times). Couple times I was able to manually delete files from the *.jdp file (although this is not recommended by RIM) and this solved the problem, but mostly I had to recreate the whole project from scratch, which if your project is large and, which is more important has dependencies on libraries, may become painful if you need to do this every few days.

So the easiest way I found so far to solve this problem is:

1. Delete the *.jdp file (you can just rename it to *.jdp.OLD)
2. Delete the project from Eclipse (right click the project and choose delete). DO NOT however check the checkbox “delete the contents of the project from disk”
3. Create a new project and point it to the same place.

Since all the Eclipse project related files remain untouched, you should get your project exactly at the same state it was before it got corrupted, minus the corrupted part. Why – because when you re-create the project Eclipse plugin should re-create the *.jdp file.

If you need to pop up a dialog or any screen actually from a process that runs in background on BlackBerry, it is fairly easy to do, unfortunately it is (as pretty much everything with BlackBerry development)  easy to figure out how to do.

The following piece of code should do the trick:

		synchronized (Application.getEventLock())
		{
			Ui.getUiEngine().pushGlobalScreen(new CLAScreen(), 1, UiEngine.GLOBAL_QUEUE);
		}

There are also a few things you should be aware of when using this code:

1. Your backgroud process should implement UiEngine. Easy way is to extend Application.
2. If you change UiEngine.GLOBAL_QUEUE to UiEngine.GLOBAL_MODAL, the dialog will block your thread until it is closed

I was contemplating quite a lot about the title for this post. Originally I wanted to give it the title of “Why developing for Blackberry sucks” but then I thought it might be too harsh and does not really reflect the content of the post which is about comparing the experience of developing for Android and experience of developing for Blackberry and settled for the current title. There were other titles revolving in my head, but all of them were just variations of  the original “why developing for Blackberry sucks”

I have been developing for Android for some time and lately I have been working on developing for Blackberry and I must say development for Android wins hands down in all aspects. Many times, especially frustrated with Blackberry buggy IDE or other cumbersome experience I wanted to write this post, but I had to find the time for it.

So what is so bad about Blackberry development? It starts at the very basics – development environment. Google has developed a very nice plugin for Eclipse which works very well and even has the basics of support for visual editing of user iterface screens. RIM – the company behind Blackberry for a long time had their own development environment – JDE. Written using basic SWING components, there’s no need to mention how bare boned and outdated it looked. They have recently introduced Eclipse plugin as well, but it is pretty buggy and half baked. It is hundreds times better than the first version of the plugin, but it is still from being stable and feature rich.

Then we have the emulators – gosh, why do I have to restart the emulator everytime I want to test a new build? It can take up to a few minutes to restart the emulators for the more advanced models. To feel the pain, just imagine the nightmare of programming the UI for Blackberry in that setup. And no, there is no visual helper that can show the layout quickly, not to mention visual builder.

The compiler, or more exactly the packager – “rapc” has many times weird problems and behaves like a whiny child with lots of attitude problems. Same goes for the MDS server emulator.

Compared to Android, this can be nightmare. Yes I’ve had some issues and observed buggy behavior with aapt while developing for Android, but it was quite easy to resolve. For the UI part of the development, Android beats Blackberry as well. Constructing layout using XML is much easier than writing actual Java code. (Apple had actually went one step furthergiving the developers visual tools.)

Localization is much easier in Android as well. Besides conceptually being easy, the support of the Eclipse plugin for localization is half baked and buggy and what’s most important, it is not that easy to find documentation on how to implement localization for Blackberry in Eclipse.

The last but not the least (and in fact probably most important) is the vibrant, enthusiastic and active community of the Android platform. It is so much easier to find answers to any problems you have while developing for Android. I was a little considered about Android being all open source in a sense that there is no central authority with central responsibility for certain things, and Blackberry has all this and it turns out that what many enthusiasts can do, easily outweighs any size company organized or not.