4) Integrate with "BlackBerry Experience:" The best BlackBerry applications take advantage of the standard features and default applications that ship with the devices, according to Yach. For instance, a mobile social networking app that can invoke the BlackBerry camera, snap an image and then tag it with location information based on the device's GPS is a much more valuable piece of software than an app that doesn't utilize any of the built-in BlackBerry tools.

3) Anticipate User Actions: This tip relates to how developers create the UI for their applications. Yach says that apps with clean layouts and intuitive icon placement make it simpler and faster for users to employ them. Users shouldn't even have to think about what they're doing when using the application; it should come naturally, he says.

2) "One Minute Work Items:" Yach referred to this tip as his "red light test." Users should be able to employ some an app's features in the time it takes for a red light to turn green agai--though he cautions that driving and using a BlackBerry simultaneously is never a good idea.

As an example, Yach cites the default BlackBerry messaging application. He says he can scan at least a few short messages and even type a quick response if necessary in a matter of minutes.

1) It Just Works: Even if applications are complex and their performance is dependent upon a variety of technologies, users shouldn't ever have to deal with those intricacies. Great BlackBerry applications "just work" the way they're supposed to, Yach says. If fact, users should be able to open an application and employ the basic functionality without ever having to open a manual or check a user forum.

Bonus Tip: Make the App FREE

This tip doesn't come from Yach; it comes directly from me. If developers really want to expose their applications to a wide variety of BlackBerry users--and they have some sort of revenue stream to support the apps--disturbing the software free of charge is a great way to start. Loyal users will likely dole out the cash for a paid version of the app in the future if the developer decides to go that route.