Blackberry development: best practices and architecture patterns

As Blackberry developers, we start the day with a much smaller set of tools than your daily mobile developer. In addition, the J2ME restriction means that we cannot take advantage of one of the main features of Java: many third-party frameworks, including Guice.

In this case, what are the best practices in the application architecture for the Blackberry platform?

I am looking for basic structures and / or principles that answer many years of architectural questions like:

  • How do we do dependency injection?
  • How do we work on testing?
  • How do we manage multiple versions of the API?
  • How do we sneak or imitate our favorite features from other versions of Java?

Please highlight one principle or best practice for each answer.

+3
source share
2 answers

I made a presentation in which I covered some of these topics in BlackBerry DevCon'10:

API , . , API BlackBerry Screen. , , J2MEUnit ( ) GUI, .

+1

Retrotranslator .

AtomicObject Blackberry.

, , .

0

Source: https://habr.com/ru/post/1795602/


All Articles