Developer Checklist

App Developer Checklist

Download & Print:
Checklist |  Testing plans
  • User Experience: Built for Form Factor
    Criteria Apps
    Required for Apps
    Efficient Ergonomics:
    • Most common actions can be done with one hand
     
    Content Occupies Full Screen:
    • App must be developed for full screen real estate
      • 720 x 1280 pixels (all-touch inputs); (16:9 aspect ratio)
      • 768 x 1280 pixels (all-touch inputs); (15:9 aspect ratio)
      • 720 x 720 pixels (physical keyboard input): (1:1 aspect ratio)
    • No black bars appear; Letterboxing permitted to maintain design optimization for screen resolution of 720 x 1280 pixels (16:9) on Z10 (768 x 1280 pixels; 15:9) - multimedia apps only
     
  • User Experience: Focus on Content
    Criteria Apps
    Required for Apps
    In-app Icons:
    • Style integrity: maintain BlackBerry 10 style across menus and tabs; themes, colors, in-app sizes
    • Design: pictorial and convey meaning through a resemblance to a physical object or function, without any explanatory text
     
    No Empty States:
    • Instances where list view contains no data or user needs to create content, app uses empty space to promote content creation (e.g., pictures app tells user they can take pictures and videos with the camera, and prompts user to launch camera)
     
    Sheets:
    • Sheets are full-screen views used for sub-tasks
    • Position: Constructive actions (right); Destructive (left)
     
    Dialogue:
    • No intrusive dialogue: no pop-ups that unnecessarily interrupt user experience
    • Critical content or time-sensitive information display dialogue is permitted
     
    Forms:
    • Ensure virtual keyboard is active based on form type. If a number field is active, the virtual keyboard should have the number view visible to user. The same is true for letter based forms
     
  • User Experience: Gestures and Flow
    Criteria Apps
    Required for Apps
    Gesture Support:
    • Support content gestures applicable to app:
      • Zoom in/out - for images and text
      • Infuse app or game with sweeping interactions/gestures
      • Contextual and reversible
     
    Exiting Application:
    • Always use swipe up action to exit; no buttons to close
     
    Minimization Behavior:
    • Minimization screen shows relevant content
     
    Notifications:
    • If using notifications, must enable toggle for ability to turn off and on
    • Position: in Settings menu (in Application Menu)
     
    Highlight Behavior:
    • For binary interactions, highlight the component when users touch it. Remove the highlight once the user moves their finger off the control. The highlight should return when the control is touched again, unless the control scrolls with the view.
    • If users scroll through a list or view (for example, a grid view), don't highlight individual items.
    • If an item requires continuous interaction (for example, a slider), highlight the item until users release their finger. In this case, you might need to lock other items that allow scrolling, such as lists
    • Don't let users highlight items they can't act on; disable (or dim) components or remove them from the screen
     
  • User Experience: Application Navigation
    Criteria Apps
    Required for Apps
    Action Bar/Action Menu:
    • Position: Bottom of Screen
    • Contents: one action other than 'back'
    • All actions must sit in Action Bar or Action Menu
    • Size: Action Bar - 81 x 81 pixels
    • Size: Action Menu - Large 81 x 81 pixels; Small 71 x 71 pixels
     
    Application Menu:
    • Position: Top of Screen; Swipe Down
    • Contents: Settings (right), Info, Help (left)
    • Size: 81 x 81 pixels
     
    Context Menus:(if used)
    • Include an unique icon and label for each item
    • Long press always invokes a context menu
    • Size: 81 x 81 pixels
     
    Additional Menu & Button Specifications:
    • Component and small buttons: Large 71 x 71 pixels; Small 61 x 61 pixels
     
    Tabs:
    • Use up to 4 tabs in an Action Bar (Z10, Q10)
     
    Deleting:
    • If deleting within an app, must be verification toast
    • Exempt if this is provided as an option in the Settings menu
    • Delete should never be in the Action Bar
    • Delete is the bottom item in the Action Menu
     
    Progress Feedback:
    • Progress and Activity Indicators to be used if longer than 3 seconds to load
    • Activity Indicator: used if functioning but cannot indicate a specific time frame for action
    • Progress Indicator: used if functioning and can indicate the specific time frame for action
    • Global Indicator: used if functioning and can continue with other actions (modal)
     
    Integrity of View:
    • When user returns to a view, show content from last filtered state
     
    Virtual Keyboard:
    • Where main task is typing, put focus on correct field for virtual keyboard and have it appear when screen opens
    • When using static keyboard layout, ensure users can still reach important parts of UI
     
    Physical Keyboard:
    • If using shortcut keys to promote one-handed use, include mapping of shortcut keys in Help menu
     
    Active Frames:
    • When using an active frame, follow guidelines below:
    • Header:
      Grid:
      List:
     
  • Service Integration
  • Performance
    Criteria Apps
    Required for Apps
    Uses:
    • All core features of app must function as designed; bug free
    • Design: experience is smooth and effortless
     
    CPU:
    • Manage CPU use intelligently
     
    Memory:
    • No memory leaks permitted
     
    Network:
    • Network traffic is minimized
     
    Battery:
    • Minimize negative impact on battery life
     
  • Security
    Criteria Apps
    Required for Apps
    Free of Malicious Intent  
    Provide a Privacy Policy  
    No luring activity to entice transactions (i.e., related to in-app advertising and payments)  
    Login Credential Recovery Option  
    Private Information:
    • Do not pass clear text passwords, contact lists, confidential information
     
    Permission Handling:
    • If permissions are denied, app gracefully handles the denial and does not crash, or prompts the user to set the required permissions to enable full functionality
     
    Transactions:
    • Make all transactions (i.e., monetary) known to user
     
  • Localization
    Criteria Apps
    Required for Apps
    (1 must apply)  
    Arabic  
    Bahasa  
    Brazilian Portuguese  
    Czech  
    Danish  
    Dutch  
    English  
    Estonian  
    Finnish  
    French  
    German  
    Greek  
    Hebrew  
    Hungarian  
    Italian  
    Japanese  
    Kazakh  
    Korean  
    Latvian  
    Lithuanian  
    Malay  
    Modern Chinese  
    Norwegian  
    Polish  
    Portugal Portuguese  
    Romanian  
    Russian  
    Slovak  
    Slovenian  
    Spanish  
    Thai  
    Turkish  
    Ukrainian  
    Vietnamese  

Game Developer Checklist

Download & Print:
Checklist |  Testing plans
  • Games
    Criteria Games
    Required for Games
    Game Engine:
    • If Game Engine is used, must be designed/tested for BlackBerry 10:
      • GamePlay
      • Unity
      • Marmalade
      • Shiva
      • Cocos2d-x
    • Note that if you use a proprietary game engine, further testing to evaluate the user experience will be performed
     
    Competitor port analysis:
    • If your app has been previously released on a competitive platform, it needs at least a 4 out of 5 star rating or equivalent
     
    Settings:
    • Must remember audio settings (i.e., mute setting)
     
    Menus:
    • Must have help or instructions menu
     
    Minimization Behavior:
    • On minimization of game - must pause
    • With exception of multiplayer service integration
     
    Interruption Behavior:
    • On phone call interruption - must pause
    • With exception of multiplayer service integration
     
  • User Experience: Built for Form Factor
    Criteria Games
    Required for Games
    Content Occupies Full Screen:
    • Game must be developed for full screen real estate
    • Games must support all touch input devices with a 16:9 aspect ratio on codeline and/or all physical keyboard input devices with a 1:1 aspect ratio on codeline in order to earn the designation for that respective class of device
    • No black bars appear; Letterboxing permitted to maintain design optimization for screen resolution of 720 x 1280 pixels (16:9) on Z10 (768 x 1280 pixels; 15:9)
     
  • User Experience: Focus on Content
    Criteria Games
    Required for Games
    No Empty States:
    • Instances where list view contains no data or user needs to create content, app uses empty space to promote content creation (e.g., pictures app tells user they can take pictures and videos with the camera, and prompts user to launch camera)
     
    Sheets:
    • Sheets are full-screen views used for sub-tasks
    • Position: Constructive actions (right); Destructive (left)




    (If using BlackBerry 10 UI)
    Dialogue:
    • No intrusive dialogue: no pop-ups that unnecessarily interrupt user experience
    • Critical content or time-sensitive information display dialogue is permitted
     
  • User Experience: Gestures and Flow
    Criteria Games
    Required for Games
    Gesture Support:
    • Support content gestures applicable to app:
      • Zoom in/out - for images and text
      • Infuse app or game with sweeping interactions/gestures
      • Contextual and reversible
     
    Exiting Application:
    • Always use swipe up action to exit; no buttons to close
     
    Minimization Behavior:
    • Minimization screen shows relevant content
     
    Notifications:
    • If using notifications, must enable toggle for ability to turn off and on
    • Position: in Settings menu (in Application Menu)
     
  • User Experience: Application Navigation
    Criteria Games
    Required for Games
    Action Bar/Action Menu:
    • Position: Bottom of Screen
    • Contents: one action other than 'back'
    • All actions must sit in Action Bar or Action Menu
    • Size: Action Bar - 81 x 81 pixels
    • Size: Action Menu - Large 81 x 81 pixels; Small 71 x 71 pixels






    (If using BlackBerry 10 UI)
    Application Menu:
    • Position: Top of Screen; Swipe Down
    • Contents: Settings (right), Info, Help (left)
    • Size: 81 x 81 pixels





    (If using BlackBerry 10 UI)
    Context Menus:(if used)
    • Include an unique icon and label for each item
    • Long press always invokes a context menu
    • Size: 81 x 81 pixels





    (If using BlackBerry 10 UI)
    Additional Menu & Button Specifications:
    • Component and small buttons: Large 71 x 71 pixels; Small 61 x 61 pixels





    (If using BlackBerry 10 UI)
    Tabs:
    • Use up to 4 tabs in an Action Bar (Z10, Q10)





    (If using BlackBerry 10 UI)
    Progress Feedback:
    • Progress and Activity Indicators to be used if longer than 3 seconds to load
    • Activity Indicator: used if functioning but cannot indicate a specific time frame for action
    • Progress Indicator: used if functioning and can indicate the specific time frame for action
    • Global Indicator: used if functioning and can continue with other actions (modal)
     
    Integrity of View:
    • When user returns to a view, show content from last filtered state
     
    Virtual Keyboard:
    • Where main task is typing, put focus on correct field for virtual keyboard and have it appear when screen opens
    • When using static keyboard layout, ensure users can still reach important parts of UI
     
    Physical Keyboard:
    • If using shortcut keys to promote one-handed use, include mapping of shortcut keys in Help menu
     
    Active Frames:
    • When using an active frame, follow guidelines below:
    • Header:
      Grid:
      List:
     
  • Service Integration
  • Performance
    Criteria Games
    Required for Games
    Uses:
    • All core features of app must function as designed; bug free
    • Design: experience is smooth and effortless
     
    CPU:
    • Manage CPU use intelligently
     
    Memory:
    • No memory leaks permitted
     
    Network:
    • Network traffic is minimized
     
    Battery:
    • Minimize negative impact on battery life
     
  • Security
    Criteria Games
    Required for Games
    Free of Malicious Intent  
    Provide a Privacy Policy  
    No luring activity to entice transactions (i.e., related to in-app advertising and payments)  
    Login Credential Recovery Option  
    Private Information:
    • Do not pass clear text passwords, contact lists, confidential information
     
    Permission Handling:
    • If permissions are denied, app gracefully handles the denial and does not crash, or prompts the user to set the required permissions to enable full functionality
     
    Transactions:
    • Make all transactions (i.e., monetary) known to user
     
  • Localization
    Criteria Apps
    Required for Apps
    (1 must apply)  
    Arabic  
    Bahasa  
    Brazilian Portuguese  
    Czech  
    Danish  
    Dutch  
    English  
    Estonian  
    Finnish  
    French  
    German  
    Greek  
    Hebrew  
    Hungarian  
    Italian  
    Japanese  
    Kazakh  
    Korean  
    Latvian  
    Lithuanian  
    Malay  
    Modern Chinese  
    Norwegian  
    Polish  
    Portugal Portuguese  
    Romanian  
    Russian  
    Slovak  
    Slovenian  
    Spanish  
    Thai  
    Turkish  
    Ukrainian  
    Vietnamese