I’m pleased to announce the BlackBerry 10 Experience App Framework for AIR. If you’re an AIR developer and you’re looking for an easier way to create applications that follow the BlackBerry 10 UI Guidelines, then this is the framework for you. The BlackBerry 10 Experience App Framework for AIR sets up all of the necessities to make it a lot easier to get up and running. Julian Dolce, our AIR SDK team lead did an excellent job creating samples that are chock-full of comments to help guide you in the right direction. This framework is the perfect way to make it easier for you to achieve Built For BlackBerry status when developing with the AIR SDK for BlackBerry 10.

All of the source code for the framework is on GitHub and it includes four samples. One thing to note is that FDT was used to create the samples. If you use Flash Builder instead of FDT I have created a video that will show you how to get everything converted from FDT 5.6 to Flash Builder 4.7.

The four included samples cover how to create:

So what is a Built for BlackBerry app? In a nutshell, a BFB app is an application which is designed from start-to-finish to be awesome in performance, looks, and functionality. Apps which apply for, and pass, the Built For BlackBerry program tell users that this app meets BlackBerry’s high standards for quality and performance.

My latest sample app was created to give you a head start in achieving the BFB designation, allowing you to focus more of your time on the functionality of your app, rather than the actual UI and setup. It’s simply a starting point/blank slate for you to work with and customize.

I’ve incorporated all of the features we look for in a Built For BlackBerry app. Right out of the box you’ll have an application that meets the BlackBerry 10 UI guidelines, connects to BlackBerry Messenger and to the Share Framework. There are also several other features including: App Menu (swipe down), Toasts, Window Covers, and device specific Splash Screens. I’ve even included CSS media queries to show you how to style your app on a Z10 vs. Q10 with CSS!. This will allow you to quickly customize this “boiler-plate” to meet your own needs and focus on the content of your app rather than getting the “right” look.

Check-out the application over at GitHub.

If you find this sample useful, have any questions, or just want to keep up-to-date on the world of BlackBerry WebWorks and HTML5, follow me on Twitter!

On a recent chore weekend, I found myself with a list of things to fix, pictures to hang, stereo components to rewire, and spaces to measure. I thought about digging through my garage for all the necessary tools, then I decided to have another cup of coffee and check my sports’ scores. I pulled out my BlackBerry Z10 to load my sports app when it hit me: is there an app to help me with my weekend chores? That’s when I found Gadget Box.

Gadget Box is the handyman’s dream. In one application you have a flashlight, speedometer, protractor, level, compass, ruler, Morse Code generator, height estimator, and units converter.  First on my list was to hook up a cables to my TV box for my upstairs TV.

Of course, the TV box was inside a very dark cabinet. No worries. Using the transform hard shell on my BlackBerry Z10, I could prop up the device, turn on the Flashlight and have a steady source of light on my subject. I connected the cables and was done. Since Gadget Box is a Built for BlackBerry application I knew that it followed the BlackBerry UI/UX guidelines for gestures. A simple swipe with my thumb and the flashlight was gone and I was back at the main screen.

Next on the list: hang a new antique, land-line phone on my wall. This chore required me to put two screws in the wall that were in line with each other. I’m told they need to be “plumb”. I guess I need something other than a hammer. So with a couple of self-drilling screws and my BlackBerry Z10, I was ready to go. I put the first screw into the wall, then used the app’s ruler to measure to where the next screw would go. A really groovy thing about Gadget Box’s ruler is that it slides. So I could put my finger on the app’s ruler to “hold it in place” and then slide the Z10. This allows you to measure distances greater than the height of the phone. Very handy.  To make sure the hole was plumb with the other screw; I used the level in Gadget Box. The initial screen had a typical bubble level that I wasn’t too keen to use in this situation. No worries, I clicked the overflow menu where I could select a Plumb Bob and I was all set. Made the mark on the wall, set the screw, and the new land-line phone was hung perfectly straight. Kind of ironic, I used a mobile phone to help hang a land-line phone.

I could go on about my day and how I used Gadget Box, but that probably wouldn’t be the best use of your time. The important take away from this story is that Gadget Box is a Built for BlackBerry application. And because it is, I knew how to use it before I even installed it. The application felt familiar to me from the very first swipe to the last interaction. I also knew that it would provide me more functionality than just a simple single function application. Instead of one app for a flashlight, another for the level, and third for measuring, I had a multi-function application that provided me with enhanced productivity; another key criteria for a Built for BlackBerry application.

The only thing Gadget Box is missing is a duct tape application and a hammer – the two tools I already have. (I don’t recommend using your BlackBerry Z10 as a hammer). So if you’re like me, a weekend handyman, check out Gadget Box and discover the enhanced productivity it can bring to your BlackBerry Z10.

What’s the Difference Between Appeal and Re-Submit?

Currently, you have the ability to re-submit your application if does not pass Built for BlackBerry. So when should you consider re-submitting your app versus using your one appeal? Only use the Built for BlackBerry Appeals process If you have received a Built for BlackBerry rejection and you believe the current version of your app is Built for BlackBerry worthy. For example, if you have submitted a “single-function” app of significant quality to be reconsidered as part of the Built for BlackBerry program, you may want to appeal. However, you may only appeal one time.

However, if you have received a Built for BlackBerry rejection and have made changes to the application to better align with the criteria necessary to be designated as Built for BlackBerry, then you should re-submit the application since you can have up to three attempts for a positive vetting decision.

Bottom line: if you rework the application, you re-submit. If you think the application should be reconsidered as is, then use your one appeal.

How to Appeal

If you choose not to make any changes to your application and want to enter into the one-time appeal process:

1. Go to the Built for BlackBerry website.
2. Click on Appeals
3. Complete the Built for BlackBerry Appeals Wizard.

Your appeal will be sent to the Built for BlackBerry Appeals Team where the special panel of Built for BlackBerry Appeals Experts will vet the appeal and record their decision. You will be notified of the decision by the Built for BlackBerry Appeals Team. The decision of the Built for BlackBerry Appeals Team is final.

We’re adjusting the Built for BlackBerry program to include an appeals process, to both respond to requests from you, our developer community, while remaining committed to the goal of Built for BlackBerry: to recognize high-quality applications that showcase the power of the new BlackBerry 10 platform. Thank you for your interest in the Built for BlackBerry program and your feedback. Keep those posts and tweets coming!

Helex, a BlackBerry 10 developer, submitted his application – one that was originally rejected because it was missing some key criteria – for the Built For BlackBerry program. His application was ClipMan – according to Helex, it’s “a small clipboard manager. That’s it. It watches for changes in the Clipboard while opened and stores every text that appears in a small database. Such a clipboard history can be very handy while texting.”

ClipMan was a well-built and useful application; however, as per the Built For BlackBerry guidelines, it did not meet the criteria as it stood. In Helex’s words: “This single useful aspect is not enough for the Built for BlackBerry certificate. I tried, trust me. You will get: ‘basically only a single core function’.” In order to qualify for the Built For BlackBerry program, Helex had to update various aspects of his app to get approved.

Here’s a quick snapshot at some of the updates to the original version of the app that made ClipMan Built For BlackBerry certified:

1. Have a clear, functional design from the start. “The old version was for me, as the developer of the app, clear and understandable. The color was indicative enough, and all features worked. But as I learned in a session about good design in Amsterdam, the application should work for everyone, including color-blind people. Those user groups had an obvious handicap at the old version of ClipMan.”
2. Share app details. “The old version was very rudimentary. The new version is clear in the beginning and more detailed in the long text.”
3. Provide a context menu. “It was not really needed since in the old version, every function was available by simply opening an item. But if I understadd the design guidelines correctly, every List View should have a context Menu. The user expects this behavior.”
4. Make it easily searchable. “I added a search function to the list. Personally, I have the list only filled with the stuff I’m currently using, but others may use this application in a different way. So, a search function was needed.”
5. Integrate to BlackBerry 10. “Built for BlackBerry means built especially for BlackBerry 10, and so the application should integrate itself in every aspect into the BlackBerry 10 system. I would say now that we’ve got the BlackBerry 10 flow.”
6. Make sure that it is shareable. “Since the share functionality was a selection criterion at the BFB checklist, ClipMan had a share button even at the first version.”
7. Create a positive store experience. “I had two versions of ClipMan in the store: a free version, and a paid version. Sadly, this is also a bad design. I got this explained at several places so I guess it played a role in it being rejected: ‘Bad store experience.’”
8. Make sure to check for bugs. “My app was unable to handle different text encoding correctly. I found the bug, and it is now able to store and handle Arabic, Chinese, Cyrillic, Greek, Japanese and many other character encoding.”

To read Helex’s full explanation (with screenshots) of how he got ClipMan accepted for the Built For BlackBerry program, click here.

What does this mean for you? It means that you can also build an app that is Built for BlackBerry certified. We’re here to help you achieve it, so please contact us if you have questions about your app. We want you to Build for BlackBerry!

Developers submitted tens of thousands of applications for the BlackBerry 10 OS.  Many developers were working very hard to meet our January 21 deadline for BlackBerry World approval, Built for BlackBerry approval and ultimately to qualify for the BlackBerry Developer 10K Developer Commitment (“10K Program”).  This created a bit of a queue. You know that. I know that. In fact, I’ve read about it before, right here on the Inside BlackBerry Developer Blog http://devblog.blackberry.com/2013/02/built-for-blackberry-update-2/.

That backlog of applications in review had many people concerned that they would not meet the requirements and deadlines for the 10K Program, since apps must be approved in BlackBerry World and approved as Built for BlackBerry before they are eligible to apply for the 10K program.  So, here’s the scoop – if you submitted your app before the January 21 deadline, and your app was approved by BlackBerry World, you are still eligible for the 10K program; even if your approval notice came after the February 18 deadline to apply for the 10K program.  We will reach out to all vendors this applies to within the next week with further information and instructions.

Please note that you must, however, obtain your Built for BlackBerry approval sometime before March 3, 2014 to be eligible for the $10k Developer Commitment program in any fashion.

And if your app isn’t already up for sale on BlackBerry World, now is the time to publish it. Why? Because that is the date your app must be up for sale in BlackBerry World to qualify for the 10K program – even if you have not yet obtained Built for BlackBerry approval by March 4. Any earnings (as defined in the 10K program Terms and Conditions) acquired from March 4 on will be counted toward your total earnings for the $10k Developer Commitment program. The sales period will end as of March 3, 2014, so you would want to have every sale count!

So here’s the calendar of important dates you need to keep in mind:

• January 21 – Submission Deadline – (yes, it’s in the past, but still important to note) Your BlackBerry 10 app needed to be submitted to BlackBerry World by this date. As long as it was submitted, you met the first qualifier for the $10k Developer Commitment program.
• March 4 – Sale Period Start Date – Your BlackBerry World-approved app must be up for sale in BlackBerry World on or before this date. All earnings from this date, whether your app has been Built for BlackBerry approved yet or not, will be considered in calculating your total earnings for any payout under the $10k Developer Commitment program.
• March 3, 2014 – Sale Period End Date – Your app must have received Built for BlackBerry approval before this date to be eligible for the $10k Developer Commitment program.

Aside from the changes noted above, all other provisions of the $10k Developer Commitment program Terms and Conditions still apply.

Sound off below on my clarifying post! My team and I will work to help answer any questions.

The Built for BlackBerry program is very near and dear to my heart. If you have heard me talk about apps at our recent global BlackBerry Jam conferences, you have heard me say that the best chance an app has for success is to be an app of good quality that provides good value to users. Built for BlackBerry is a program to help developers be recognized for delivering a level of quality in their applications, while also giving customers a sense of assurance that the apps they are investing in will be of good quality.

There’s been a great deal of contention lately around the qualification process.

We have seen feedback that many well-built, well designed apps are not qualifying for our Built for BlackBerry program – specifically we are looking at the apps that have been rejected for being “single function” apps. I’ve personally gone through the forum posts on this topic.  I’ve looked at many of the apps, and I’ve seen that some of the apps that have been rejected have greater utility than the reviewer initially thought. So, based on the feedback from you, our developers,  we’re making some changes on how we address these apps in Built for BlackBerry review.

First, we’re going to re-review all the applications that were failed solely on the basis of being a single function app. This re-review has already begun and will continue until we’ve reviewed and communicated back to the developers of these apps. I should note that if an app failed as a single function and failed another portion of the criteria such as lack of BlackBerry 10 UI or Service Integration, then these apps will not be re-reviewed.  Developers of apps that failed on multiple criteria, including simple application, will need to correct the other reasons for failure first, and then resubmit the app for evaluation.  It’s also important to understand that very simple applications will still not be qualified to earn the Built for BlackBerry designation.

This new level of review may take us beyond March 4th – which is the start date for the $10k Developer Commitment revenue period. Because of this, any apps submitted before prior deadlines, but approved for Built for BlackBerry after March 4th will have their revenue retroactively tracked back to March 4, 2013.

Second, we’re going to institute an appeals process.  If you feel that your app has been misunderstood or unfairly rejected, there will be a mechanism by which you can submit your reasoning to us, and a group of senior reviewers at BlackBerry will take your feedback under consideration.

Third, we’re re-working rejection mails in order to provide better clarity and guidance. This is a delicate balancing act, however.  One trap we don’t want to fall into is designing apps for our developers – only you know the functionality you want to deliver, and in most cases you will be better qualified to understand your customer than our reviewers will.

And finally, Built for BlackBerry is designed to showcase the best than can be built for the BlackBerry 10 platform.  To help you understand the acceptance criteria,  we’ll be publishing case studies on these apps to help guide your app development.

We remain committed to the goals of Built for BlackBerry – recognizing high quality applications that deliver on the promise of BlackBerry 10 by creating experiences that showcase the power of the platform.  We’re adjusting the program today, in the spirit of the partnership that we’ve forged over the last year with you, our developer community.

And on behalf of everyone at BlackBerry I want to thank you for your continued feedback, good will, and support for the BlackBerry platform.
If you have any questions – I’m available – alec.saunders@blackberry.com

Keep jamming!

Alec

The goal of Sparkle is to “embark on an extraordinary journey to uncover the secrets of Crowberry Woods. Banish the darkness with your Orb Slinger and reclaim your land!” The game play is brilliant in its simplicity; you use your Orb Slinger to throw colored orbs at a line of moving orbs. When your orb hits the line, if it makes a string of at least three of the same color, those orbs are banished. You keep throwing orbs until all the moving orbs are banished or until an orb falls in the hole at the end.

There is also a fun storyline, power-ups, and secret amulets that keeps the game interesting and engaging. Another big feature of the game is it is also a Built For BlackBerry game.

What is Built For BlackBerry?

If you’re a frequent follower of this blog or BlackBerry development in general, then you probably already know about Built For BlackBerry and can skip to the next section. If not, here’s a quick overview of Built For BlackBerry:

The Built For BlackBerry program was designed to allow end users of BlackBerry 10 applications to identify the truly high-quality, cream of the crop application and games. These applications and games went above and beyond just developing for the platform – they embraced the ideas and philosophies behind the BlackBerry 10 platform. There are five key areas where the application must excel: User Benefits, User Experience, Performance, Service Integration, and Security. It is not easy to become a Built For BlackBerry application or game, so let’s look at how Sparkle did it.

User Benefits

Clearly almost every application or game made must provide some level of user benefit; if it didn’t, you probably wouldn’t have made the application. To qualify for Built For BlackBerry, the bar is set higher. Your application or game has to provide genuine entertainment value, enhanced productivity, and/or enriched communication. Looking at Sparkle, it provides genuine entertainment value beyond a basic game. A basic game might just allow you clear the orbs level after level of monotonous orb banishing. But in Sparkle, there is genuine long-term entertainment with the addition of a storyline, power-ups, and mysterious quests.

User Experience

The User Experience area for Built For BlackBerry is about providing the user with a pleasing experience and an easy-to-navigate application or game. It is about taking advantage of the form factor and using it to your advantage. Sparkle runs in landscape mode only and it utilizes the maximum amount of screen real estate. The application navigation is simple and user friendly. Simple taps launch the orbs and swipes move the aim. There is also a nice background soundtrack and theme feedback sounds on button clicks. Familiar gestures are used, like swipe down from the top to pause the game and reach the options menu, and the animation is ridiculously smooth and pleasing.

Performance

The performance criteria are about how the application uses the system resources including CPU, memory, network, battery, etc. It is difficult to see this criterion when running the application except to know that I can play for a very, very, very long time before the battery dies.

Service Integration

To qualify for Built For BlackBerry, an application must integrate with the system in some way. Games are not required to integrate with the system, but are encouraged to do so. Sparkle integrates with Scoreloop, the social gaming component of BlackBerry 10. Scoreloop allows a game to post achievements, awards, leaderboards, and challenges.

Security

To qualify in the Security criteria, you need to do a couple things. First, you need to be good to your users. Don’t send passwords in clear text; don’t make any monetary transactions without asking permission; and don’t use the user’s data in a malicious way. You want your users to trust you so they will buy more of your applications or games. The second thing you must do is provide a link to your privacy policy in the vendor portal of BlackBerry World.

Conclusion

When building your application or game, I encourage you to utilize the guidelines and create a Built For BlackBerry application or game. It isn’t easy, as the Built For BlackBerry logo is not awarded to just any application or game – it must be earned. The Built For BlackBerry logo will identify your application or game as cream of the crop and that, I feel, will lead to more downloads and happier customers. And who knows, your application or game may get featured in a blog post like this one!

Now that the dust is settling from this weekend’s Last Chance Port-A-Thon, we’re excited to announce that over 19,000 applications were submitted to BlackBerry World over the weekend. This continues to show an overwhelming level of commitment from developers to the BlackBerry 10 platform.

We’ve heard your questions and concerns about the Built for BlackBerry deadline. The fact is, the volume of apps being submitted for review and entry into the program has been remarkable. Due to that large volume of apps, we are extending the deadline:

• Apps that have been submitted on or before 8pm EST on January 21^st,2013 may qualify for the $10k Developer Commitment if the developer agrees to the official terms and conditions and passes Built for BlackBerry testing.
• Developers may apply for Built for BlackBerry review and the $10k Developer Commitment offer in the BlackBerry World Vendor Portal by 8pm ET Feb 18^th
• The qualifying sale dates for the 10k Commitment is 12:01am ET, March 4 2013 to 11:59pm ET, March 3 2014

Don’t forget to review the Built for BlackBerry criteria before you apply and just a friendly reminder that BlackBerry App Generator and Android apps do not qualify for Built for BlackBerry or the $10k Commitment.

BlackBerry 10 Limited Edition Update
http://devblog.blackberry.com/2013/01/blackberry-10-limited-edition-update-2/

How to build an app in 10 minutes with the BlackBerry App Generator:
http://devblog.blackberry.com/2013/01/blackberry-app-generator/

CustomMapsView in your Cascades app
http://devblog.blackberry.com/2013/01/cascades-mapview/

Built for BlackBerry program update
http://devblog.blackberry.com/2013/01/built-for-blackberry-update/