General FAQs

What is mBooster?

mBooster is a fully automated optimizer for J2ME applications. It targets the key technological barrier facing mobile game and application developer today. By alleviating the size constraints imposed by handsets, it allows mobile game developers and publishers to develop and port better content for more handsets in a cost and time efficient manner.

What competitive advantages does mBooster deliver?

Please see mBooster for details.

We are using an obfuscator, why do we need mBooster?

mBooster works with all existing obfuscators. mBooster compacts the applications much further, and provides additional performance optimization through advanced compiler-based optimizations unavailable to an obfuscator. If you are developing mobile content for constrained devices, you will appreciate a competitive advantage through the extra space and performance mBooster delivers.

What is the licensing model of mBooster?

Please contact our sales team for further details.

Technical FAQs

System requirements

  • Windows XP or Windows 2000
  • Pentium 4 2GHz CPU or equivalent
  • 512 MB free memory (Recommended 1G memory)
  • 60MB free hard disk

mBooster is currently available only on Windows XP or Windows 2000 platforms. If you require support for other operating systems, please contact Innaworks mbooster-support@innaworks.com

How is mBooster different from an obfuscator?

The core functions of an obfuscator are:

  • Removing methods and fields that are not required
  • Renaming methods, fields and classes to shorter names.

At the core of mBooster is an optimizing compiler. It is designed to support complex optimizations that you would expect in an optimizing compiler for a non-java platform, such as GCC. mBooster therefore is capable of performing a much greater range of optimizations that goes way beyond renaming. Some of the optimizations include automatic class hierarchy refactoring, method inlining, instruction scheduling and redundancy elimination. The optimizing compiler is complemented by a custom-built preverifier, designed to minimize the size of stackmap.

mBooster optimization suite also includes mBoosterZip and mBoosterPng. mBoosterZip is a ZIP/JAR deflater delivering the highest compression ratio and the smallest JAR file. mBoosterPng squeezes the last byte out of PNG files, and is complementary to all standard PNG optimizers.

What optimizations does mBooster perform?

mBooster mobile game edition provides a range of advanced optimizations, including

  • Automatic class hierarcy refactoring, i.e. class merging
  • Method inlining
  • Low level optimizations
  • Instruction scheduling
  • Stack map optimizations
  • Declarative resource packing
  • High performance JAR compression
  • PNG file recompression
  • M3G file recompression

We also perform a number of optimizations which cannot be replicated by hand.

Could mBooster optimize DoJa or CLDC 1.0/1.1 or MIDP 1.0/2.0 applications?

mBooster is agnostic with respect to the system libraries. mBooster equally well with DoJa applications, CLDC 1.0/1.1 applications and MIDP 1.0/2.0 applications.

Our application requires a vendor specific/handset specific API, could we use mBooster?

mBooster is agnostic with respect to the system libraries. mBooster works with any vendor specific/handset specific libraries.

We use third-party libraries, could we use mBooster?

mBooster works with any third party libraries. mBooster does not require the source code of the third party libraries. Through whole program optimizations, mBooster will deliver size and performance advantages by analysing and optimizing the interactions between the third party libraries and your proprietary classes.

Could mBooster optimize non-game mobile applications?

Yes it does. mBooster is able to optimize any J2ME CLDC applications. mBooster works equally well on business applications, embedded applications and advertising contents. However a different software licensing model applies to non-game content. Please contact us on mbooster-sales@innaworks.com

Could mBooster optimize interactive TV (DHB) applications?

Yes it does. The new DHB standard is based on Java J2ME CLDC. mBooster would significantly improve the development process for interactive TV (DHB) content.

Could mBooster optimize J2ME CDC applications?

mBooster mobile game edition works with J2ME CDC applications, with a few minor limitations. For more information please contact us on mbooster-sales@innaworks.com