×
Namespaces

Variants
Actions
(Difference between revisions)

Archived:Porting from Android to Nokia Platforms

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Addition to article of: Category:MeeGo Category:Symbian. (Add platform categories))
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot update - Fix Article Metadata and other minor issues)
Line 1: Line 1:
 +
{{ArticleMetaData <!-- v1.2 -->
 +
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 +
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
 +
|devices= <!-- Devices tested against - e.g. ''devices=Nokia 6131 NFC, Nokia C7-00'') -->
 +
|sdk= <!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Qt SDK 1.1.4]) -->
 +
|platform= <!-- Compatible platforms - e.g. Symbian^1 and later, Qt 4.6 and later -->
 +
|devicecompatability= <!-- Compatible devices e.g.: All* (must have internal GPS) -->
 +
|dependencies= <!-- Any other/external dependencies e.g.: Google Maps Api v1.0 -->
 +
|signing= <!-- Signing requirements - empty or one of: Self-Signed, DevCert, Manufacturer -->
 +
|capabilities= <!-- Capabilities required by the article/code example (e.g. Location, NetworkServices. -->
 +
|keywords= <!-- APIs, classes and methods (e.g. QSystemScreenSaver, QList, CBase -->
 +
|language= <!-- Language category code for non-English topics - e.g. Lang-Chinese -->
 +
|translated-by= <!-- [[User:XXXX]] -->
 +
|translated-from-title= <!-- Title only -->
 +
|translated-from-id= <!-- Id of translated revision -->
 +
|review-by= <!-- After re-review: [[User:username]] -->
 +
|review-timestamp= <!-- After re-review: YYYYMMDD -->
 +
|update-by= <!-- After significant update: [[User:username]]-->
 +
|update-timestamp= <!-- After significant update: YYYYMMDD -->
 +
|creationdate= 20100426
 +
|author= [[User:Jros]]
 +
}}
 
[[Category:Porting]][[Category:Qt]][[Category:Qt Quick]]
 
[[Category:Porting]][[Category:Qt]][[Category:Qt Quick]]
 
{{Note| This article or its primary content has now been incorporated to the [http://www.developer.nokia.com/Resources/Library/Porting_to_Qt/android-to-qt.html Porting to Qt Library]}}
 
{{Note| This article or its primary content has now been incorporated to the [http://www.developer.nokia.com/Resources/Library/Porting_to_Qt/android-to-qt.html Porting to Qt Library]}}
Line 9: Line 31:
 
*[[Fundamental use cases for porting iPhone and Android applications to Qt]]
 
*[[Fundamental use cases for porting iPhone and Android applications to Qt]]
 
*[[Qt Quick examples for porting]]
 
*[[Qt Quick examples for porting]]
*[[Wordpress developer story]]
+
*[[Wordpress developer story]]
*[http://www.developer.nokia.com/Design/ Nokia Developer Design and User Experience Guide] for ideas on how to achieve the best possible user experience when porting your application for Nokia devices.
+
*[http://www.developer.nokia.com/Design/ Nokia Developer Design and User Experience Guide] for ideas on how to achieve the best possible user experience when porting your application for Nokia devices.
 
}}
 
}}
  
Line 45: Line 67:
 
Nowadays, in addition to developing Android applications directly in the Java language, several Android applications are also built as web applications using the WebKit approach with tools like [http://www.appcelerator.com/products/titanium-mobile-application-development/ Titanium Mobile] or by utilizing the LibWebCore in manual fashion from the Android application.
 
Nowadays, in addition to developing Android applications directly in the Java language, several Android applications are also built as web applications using the WebKit approach with tools like [http://www.appcelerator.com/products/titanium-mobile-application-development/ Titanium Mobile] or by utilizing the LibWebCore in manual fashion from the Android application.
  
For these types of web applications the recommended porting approach is to rewrite the application with Qt Quick, especially if the intention is to develop an impressive UI. For more information on Qt Quick, see [[Porting Mobile Applications to Qt#Qt Quick and QML Language|the section on Qt Quick in the porting introduction]].
+
For these types of web applications the recommended porting approach is to rewrite the application with Qt Quick, especially if the intention is to develop an impressive UI. For more information on Qt Quick, see [[Porting Mobile Applications to Qt#Qt Quick and QML Language|the section on Qt Quick in the porting introduction]].
  
 
Developers could also consider building a Qt Quick application and basing its functionality on embedded web views; for more information, see [[Fundamental use cases for porting iPhone and Android applications to Qt#Web View|the Fundamental porting use cases document]].
 
Developers could also consider building a Qt Quick application and basing its functionality on embedded web views; for more information, see [[Fundamental use cases for porting iPhone and Android applications to Qt#Web View|the Fundamental porting use cases document]].

Revision as of 03:32, 23 February 2012

Article Metadata
Compatibility
Platform(s):
Symbian
Article
Created: User:Jros (26 Apr 2010)
Last edited: hamishwillee (23 Feb 2012)

Note.pngNote: This article or its primary content has now been incorporated to the Porting to Qt Library

Porting-android-to-qt.png

The following article describes recommended ways to port different types of Android applications to Nokia platforms, and also covers the most typical special cases.

Contents

Normal Android Java Apps

Porting-java.png

Since Android applications are written in Java, direct code-level reuse is typically not possible when porting to Qt. Typically the application design and assets can be reused in a new QML UI, and the code rewritten.

Java Native Interface

A notable special case is where the Java Native Interface (JNI) is used in the Android application. JNI allows the use of C/C++ shared libraries from Android code.

Although this is not a recommended way to develop basic Android applications, it is very useful in some specific cases — for example, with games relying on existing game engines, which are often written in C/C++.

If the Android application uses these kinds of C/C++ shared libraries, code-level reuse is also often possible, especially towards the Maemo platform but also sometimes towards the Symbian platform.

WebKit

Nowadays, in addition to developing Android applications directly in the Java language, several Android applications are also built as web applications using the WebKit approach with tools like Titanium Mobile or by utilizing the LibWebCore in manual fashion from the Android application.

For these types of web applications the recommended porting approach is to rewrite the application with Qt Quick, especially if the intention is to develop an impressive UI. For more information on Qt Quick, see the section on Qt Quick in the porting introduction.

Developers could also consider building a Qt Quick application and basing its functionality on embedded web views; for more information, see the Fundamental porting use cases document.

User interface

Porting-graphics-requirements.png

Although code cannot typically be reused, the graphics and design of the application can often be reused to good effect. For example, in Qt Quick, scaling of the existing UI elements is very easy and may not require much rework from the UI designers.

Generally, however, your application will look best and be most usable if you take some time to redesign the application layout. An application layout that looks great on an Android device may not be very usable on a Nokia device, since the usage paradigm of user interface and available features affecting the user experience are different.

For more information on UI design for Nokia devices, see the Nokia Developer Design and User Experience Guide.


Copyright © 2010 Nokia Corporation. All rights reserved.

Nokia, Nokia Developer, and Maemo are registered trademarks of Nokia Corporation. Java and all Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. Apple, iPhone, iPod and MacBook are trademarks or registered trademarks of Apple Inc. Android is a trademark of Google Inc. Other product and company names mentioned herein may be trademarks or trade names of their respective owners.

127 page views in the last 30 days.