Help Center
Local Navigation
- Understanding BlackBerry and programming for BlackBerry devices
- BlackBerry Java Application design
- Standalone applications
- Applications with desktop synchronization
- Applications with wireless access, wireless synchronization, or wireless alerting
- MIDlet applications
- CLDC applications
- API control and code signing
- Object modeling
- Multithreading
- Best practices for writing an efficient BlackBerry Java Application
- Best practice: Writing efficient code
- Using local variables
- Using shorthand for evaluating Boolean conditions
- Making classes final
- Using int instead of long
- Avoiding garbage collection
- Using static variables for Strings
- Avoiding the String(String) constructor
- Writing efficient loops
- Optimizing subexpressions
- Optimizing division operations
- Avoiding java.util.Enumeration
- Performing casts using instanceof
- Evaluating conditions using instanceof
- Avoiding StringBuffer.append (StringBuffer)
- Avoiding returning null
- Avoiding passing null into methods
- Using caution when passing null into a constructor
- Using longs for unique identifiers
- Exiting applications correctly
- Printing the stack trace
- Best practice: Using objects judiciously
- Best practice: Reducing the size of compiled code
- Best practice: Writing efficient code
- Multilanguage support
- Multimedia support
- UI and navigation design
- Memory management
- Data management
- Wireless data transport
- BlackBerry application integration
- Security considerations
- Test a BlackBerry Java Application
- Making applications available
- Glossary
- Legal notice
BlackBerry Manuals & Help
>
Developer Documentation
>
Java Development Guides and API Reference
>
Fundamentals Guide
BlackBerry Java Development Environment - 4.6.0
Setting appropriate access
When you create code libraries, you can significantly reduce the size of your compiled code by using the appropriate access modifiers for fields and methods. Declare fields as private whenever possible. In addition to being good coding practice, this allows the compiler to optimize the .cod file. When possible, use the default (package) access instead of public access (that is, omit the public and protected keywords).
Parent topic: Best practice: Reducing the size of compiled code