Stump the BlackBerry Devs!



I recently had the pleasure of chatting with Derek Konigsberg, who some of you may know better as @dkonigs.  For those of you who may not know Derek, he’s been developing apps for the BlackBerry® platform since 2006 (starting with BlackBerry handheld software version 4.1), so he’s seen quite the overhaul to the platform.  Long story short, my conversation with Derek about his questions on BlackBerry® 10 development inspired a really neat idea: Stump the BlackBerry Devs.

How do I stump someone and who am I stumping?  Provide us with a design or mock-up that you think would be difficult to be implemented using our Cascades™ UI framework. The Cascades tools development team will try to implement your submission in a flexible manner that involves no hardcoding of values and that is flexible enough to handle multiple screen resolutions and multiple form factors.

Here are the details:

Mock up a design for a screen, making it as beautiful or as ugly as you like.

  • It doesn’t matter how you create it – use a professional design tool or draw it on a napkin.
  • Don’t worry about a data source, we’ll be using dummy data anyway.

Throughout the month of August, submit an image of your mock-up to the @BlackBerryDev Twitter® account using the hashtag #StumpTheBlackBerryDevs.

  • Final day for submissions will be August 31, 2012.
  • If an image isn’t worth a thousand words and you feel the need to describe your design with more than the 140 characters of Twitter will allow, feel free to submit multiple tweets to explain your design.

We’ll choose three of the most difficult or creative submissions and throughout the month of September, and then we’ll get to work implementing them using the R8 SDK beta release that Tim Neil talked about here.

At BlackBerry Jam Americas, we’ll host a session during the Unconference Day where we’ll reveal the chosen designs, explain how we implemented them, and walk you through the reasoning behind the approach taken. For any features of the design which could not be elegantly implemented, we’ll do a few things:

  1. Implement the solution per the design using hardcoded values.
  2. Provide an alternative solution that is consistent with Cascades design principles.
  3. Explain the design decisions behind Cascades for why the solution could not be delivered per what you’d submitted.
  4. If applicable, add new features to the roadmap which would allow this design to be implemented in future and publicly share the tracking of those features via the BlackBerry Developer Issue Tracker.

In parallel to the activities at BlackBerry Jam Americas, we’ll also post the code for the solutions to our open source repo at and will share a detailed walkthrough of the solution to this blog.

Sound like a fun challenge?  I hope so.  Now let’s see what you’re made of…can you stump the Cascades R&D team?

Join the conversation

Show comments Hide comments
+ -