Porting from BlackBerry to Series 40 - Revision history

Bloodredsky: Bloodredsky - /* Full touch devices */

2012-10-29T21:43:54Z

Bloodredsky - - Full touch devices

Kiran10182: Kiran10182 - FA templated added

2012-10-28T10:06:36Z

Kiran10182 - FA templated added

Mtron: Mtron - /* Devices especially interesting for porting projects */

2012-10-17T12:32:57Z

Mtron - - Devices especially interesting for porting projects

Mtron: Mtron - /* Full touch devices */

2012-10-17T12:32:02Z

Mtron - - Full touch devices

Mtron: Mtron - /* Full touch devices */

2012-10-17T12:24:04Z

Mtron - - Full touch devices

Mtron: Mtron - /* Full touch devices */

2012-10-17T11:26:49Z

Mtron - - Full touch devices

Mtron: Mtron - /* Full touch devices */

2012-10-17T11:23:33Z

Mtron - - Full touch devices

Mtron: Mtron - /* Full touch devices */

2012-10-17T11:17:07Z

Mtron - - Full touch devices

Mtron: Mtron - /* Devices especially interesting for porting projects */

2012-10-17T11:15:19Z

Mtron - - Devices especially interesting for porting projects

Mtron: Mtron - /* Porting considerations */

2012-10-17T11:09:17Z

Mtron - - Porting considerations

@@ Line 72: / Line 72: @@
 | Capacitive Touch Screen || QWERTY and Capacitive Touch Screen || Capacitive Touch Screen, Multipoint-touch (5 points) || Resistive Touch Screen, Multipoint-touch (2 points) || Capacitive Touch Screen, Multipoint-touch
 |-
-| ROM/RAM 4GB/768MB, 32 GB Micro SD || ROM/RAM 8GB/768MB, 32 GB Micro SD || ROM/RAM 256MB/128MB, 32 GB Micro SD || ROM/RAM 64MB/32MB, 32 GB Micro SD || ROM/RAM 64MB/32MB, 32 GB Micro SD
+| ROM/RAM 4GB/768MB, 32 GB Micro SD || ROM/RAM 8GB/768MB, 32 GB Micro SD || ROM/RAM 256MB/128MB, 32 GB Micro SD || ROM/RAM 64MB/32MB, 32 GB Micro SD || ROM/RAM 128MB/64MB, 32 GB Micro SD
 |}

@@ Line 1: / Line 1: @@
-[[Category:Java ME]][[Category:Series 40]][[Category:Porting]][[Category:BlackBerry]][[Category:MIDP]][[Category:Nokia UI API]][[Category:Series 40 Developer Platform 2.0]][[Category:Tutorial]]
+[[Category:Java ME]][[Category:Series 40]][[Category:Porting]][[Category:BlackBerry]][[Category:MIDP]][[Category:Nokia UI API]][[Category:Series 40 Developer Platform 2.0]][[Category:Tutorial]][[Category:Java ME]]
 {{Abstract|This article explains what needs to be taken into account when porting BlackBerry apps to Series 40.}}
@@ Line 25: / Line 26: @@
 }}
-[[Category:Java ME]]
 == Porting considerations==

@@ Line 43: / Line 43: @@
 {| class="wikitable"
 |-
-| BlackBerry Bold 9900 || BlackBerry Curve 9350 || [https://www.developer.nokia.com/Devices/Device_specifications/Asha_303/ Nokia Asha 303] || [https://www.developer.nokia.com/Devices/Device_specifications/Asha_302/ Nokia Asha 302]
+| BlackBerry Bold 9900 || BlackBerry Curve 9350 || [http://www.developer.nokia.com/Devices/Device_specifications/Asha_303/ Nokia Asha 303] || [http://www.developer.nokia.com/Devices/Device_specifications/Asha_302/ Nokia Asha 302]
 |-
 | [[File:bb2s40_t1p1.png]] || [[File:bb2s40_t1p2.png]] || [[File:bb2s40_t1p3.png]] || [[File:bb2s40_t1p4.png]]

@@ Line 63: / Line 63: @@
 {| class="wikitable"
 |-
-| BlackBerry Torch 9860 || BlackBerry Torch 9810 || Nokia Asha 311 || Nokia Asha 305/306 || Nokia Asha 308/309
+| BlackBerry Torch 9860 || BlackBerry Torch 9810 || [http://www.developer.nokia.com/Devices/Device_specifications/Asha_311/ Nokia Asha 311] || [http://www.developer.nokia.com/Devices/Device_specifications/Asha_305/ Nokia Asha 305]/[http://www.developer.nokia.com/Devices/Device_specifications/Asha_306/ 306] || [http://www.developer.nokia.com/Devices/Device_specifications/Nokia_Asha_308/ Nokia Asha 308]/[http://www.developer.nokia.com/Devices/Device_specifications/Nokia_Asha_309 309]
 |-
 | [[File:bb2s40_t2p1.png]] || [[File:bb2s40_t2p2.png]] || [[File:bb2s40_t2p3.png]] || [[File:bb2s40_t2p4.png]] || [[File:bb2s40_t2p5.png]]

@@ Line 74: / Line 74: @@
 |}
-Nokia Asha 311 is an especially interesting device, giving that the performance is significantly faster than the performance of the more budget-oriented Nokia Asha 305 and Nokia Asha 306.
+CPU clock speed for full touch Asha devices is in the range 200 MHz - 1 GHz. Nokia Asha 311 with 1 GHz CPU is an especially interesting device, giving that the performance is significantly faster than the performance of the more budget-oriented Nokia Asha 305/306 and Nokia Asha 308/309.
 == Portability of different application types ==

← Older revision		Revision as of 11:17, 17 October 2012
Line 58:		Line 58:
	== Full touch devices ==		== Full touch devices ==

−	With the announcement of Nokia Asha 305, Nokia Asha 306, and especially Nokia Asha 311, BlackBerry developers targeting the full touch experience should also consider porting to these devices.	+	With the announcement of Nokia Asha 305, Nokia Asha 306, and especially Nokia Asha 311, BlackBerry developers targeting the full touch experience should also consider porting to these devices. In October 2012, this family of full touch devices was extended with two new members Asha 308 and Asha 309.

@@ Line 54: / Line 54: @@
 |}
-Nokia Asha 302 and Nokia Asha 303 are the fastest QWERTY Series 40 devices with 4 MB of Java Heap space available for 3rd party applications. The expected user base is very similar to BlackBerry Bold and Curve users, especially for the messaging and business types of apps. Nokia Asha 302 supports landscape orientation and integration with Mail for Exchange, which makes it one of the primary porting targets for traditional BlackBerry apps.
+Nokia Asha 302 and Nokia Asha 303 are the fastest QWERTY Series 40 devices with 1 GHz CPU, 4 MB of Java Heap space available for 3rd party applications. The expected user base is very similar to BlackBerry Bold and Curve users, especially for the messaging and business types of apps. Nokia Asha 302 supports landscape orientation and integration with Mail for Exchange, which makes it one of the primary porting targets for traditional BlackBerry apps.
 == Full touch devices ==

@@ Line 25: / Line 25: @@
 }}
 == Porting considerations==
 BlackBerry devices (up to BlackBerry OS 7.1) and Series 40 devices share the same development platform - Java ME. This makes porting from BlackBerry to Series 40 quite straightforward and transparent, especially when compared to other mobile platforms. Generic Java ME MIDlets that use the standard set of LCDUI controls, Canvas, GameCanvas, and the basic set of optional JSRs, should be possible to deploy to both BlackBerry and Series 40 after platform-specific repackaging. Of course, the behavior of LCDUI Commands and the default UI look & feel varies significantly between platforms but from the development perspective optimising a standard Java ME MIDlet for a specific platform is a trivial task. The familiarity of the programming language, Java, also plays a significant role in simplifying the porting process. Many generic Java ME libraries can be reused on both platforms “as is”.
-At the same time, most of the benefits that developers used to get from BlackBerry devices are specific platform integration APIs, which allow deeper utilisation of device services when compared to generic MIDlets. On top of that, the BlackBerry UI frameworks are different from the traditional Java ME architecture and much closer to the Java Swing ideology when compared to the classic LCDUI which is, with some Nokia extensions, the basis of Series 40. This means that the estimated difficulty of porting “BlackBerry Application” types (which is the term used in the BlackBerry Application Descriptor XML) is probably on the same level in as Android to Series 40 porting projects. Developers targeting both platforms might consider using the LWUIT library, which provides enough UI abstraction between platforms but also a rich set of UI components. This approach can definitely be an interesting choice especially for new projects because the Nokia release of LWUIT has been tailored for Series 40.
+At the same time, most of the benefits that developers used to get from BlackBerry devices are specific platform integration APIs, which allow deeper utilisation of device services when compared to generic MIDlets. On top of that, the BlackBerry UI frameworks are different from the traditional Java ME architecture and much closer to the Java Swing ideology when compared to the classic LCDUI which is, with some Nokia extensions, the basis of Series 40. This means that the estimated difficulty of porting “BlackBerry Application” types (which is the term used in the BlackBerry Application Descriptor XML) is probably on the same level in as Android to Series 40 porting projects. Developers might also consider using the LWUIT library on Series 40, which provides rich set of UI components and Java Swing inspired architecture. This approach can definitely be an interesting choice especially for new projects because the Nokia release of LWUIT has been tailored for Series 40.
 [http://projects.developer.nokia.com/LWUIT_for_Series_40 LWUIT for Series 40]
 And finally, developers should recognise the major differences between the platforms: BlackBerry devices are full smartphones with multitasking capabilities, and Series 40 devices are feature phones with much more limited resources and device capabilities. However, with the right approach and creativity, you should be able to achieve high standards of user experience for ported applications in several categories and benefit from the giant marketplace of Series 40 devices in consumer hands.
 == Devices especially interesting for porting projects ==