Home | alcheMo | mBooster | Company | Partners | News | Contact Us |

This page last changed on Mar 28, 2008.

Benefits

Through its unique approach to handle mobile platform fragmentation, the alcheMo product family delivers significant benefits throughout the product lifecycle.

Reduced Time To Market

By eliminating a separate J2ME to native platforms porting process, time to market can be reduced by weeks and months. alcheMo provides the benefits of simultaneous development without the cost of running multiple development teams. J2ME, iPhone and BREW versions of your application are available at any stage of development, enabling QA early in the development cycle, improving project visibility and preventing project delays. Furthermore, the increased agility allows application developers to out-manoeuvre competitors through rapid product feature rollouts across multiple platforms throughout the product lifetime.

One code base

With alcheMo it is practical to have a single source base to target J2ME, iPhone and BREW devices. The software development process can be streamlined, significantly reducing development and maintenance costs. With alcheMo it is natural to release J2ME and native platform versions simultaneously, simplifying product and release management. alcheMo also helps to improve product quality and customer satisfaction; a defect fixed in the J2ME version is also a defect fixed in the iPhone and BREW versions.

One team

The same developers can now develop for both J2ME, iPhone and BREW platforms. Greater scheduling and task allocation flexibility results in more efficient use of their individual skills.

Leverage J2ME investments

With alcheMo you can take full advantage of your existing investments in your J2ME tool-chain. Your J2ME game engines, libraries, frameworks and tools are now available in BREW. alcheMo is designed to integrate with your in-house or third party J2ME porting solution. Furthermore, through alcheMo you are now able to utilise in your BREW application many powerful open source components (such as kXML and BouncyCastle), with suitable licenses, developed by an active J2ME community.

Reduced QA cost

By sharing a common code base between J2ME, iPhone and BREW, functional tests need be performed only once to cover both platforms. Furthermore, Java is an intrinsically safer language, eliminating entire classes of programming errors common in C/C++/ObjectiveC.