×
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 - Fix links)
hamishwillee (Talk | contribs)
 
(3 intermediate revisions by one user not shown)
Line 1: Line 1:
[[Category:Porting]][[Category:Qt]][[Category:Qt Quick]][[Category:MeeGo]][[Category:Symbian]]
+
{{Archived|timestamp=20120223034955|user=[[User:Hamishwillee|<br />----]]|}}[[Category:Porting]][[Category:Qt]][[Category:Qt Quick]][[Category:MeeGo Harmattan]][[Category:Symbian]]
 +
{{Abstract|This article has now been incorporated to the [http://www.developer.nokia.com/Resources/Library/Porting_to_Qt/android-to-qt.html Porting to Qt Library]}}
 
{{ArticleMetaData <!-- v1.2 -->
 
{{ArticleMetaData <!-- v1.2 -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
 
|sourcecode= <!-- Link to example source code e.g. [[Media:The Code Example ZIP.zip]] -->
Line 22: Line 23:
 
|author= [[User:Jros]]
 
|author= [[User:Jros]]
 
}}
 
}}
 
{{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]}}
 
 
{{SeeAlso|
 
'''Other porting-related articles'''
 
*[http://www.developer.nokia.com/Resources/Library/Porting_to_Qt/ Porting to Qt Library]
 
*[[Porting from iPhone to Nokia Platforms]]
 
*[[Porting from Android to Nokia Platforms]]
 
*[[Fundamental use cases for porting iPhone and Android applications to Qt]]
 
*[[Qt Quick examples for porting]]
 
*[[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.
 
}}
 
 
[[File:porting-android-to-qt.png|300px]]
 
 
The following article describes recommended ways to port different types of
 
Android applications to Nokia platforms, and also covers the most typical
 
special cases.
 
 
== Normal Android Java Apps ==
 
 
[[File:porting-java.png|300px]]
 
 
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 [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 [http://www.developer.nokia.com/Resources/Library/Porting_to_Qt/ Porting to Qt Library].
 
 
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]].
 
 
== User interface ==
 
 
[[File:porting-graphics-requirements.png|450px]]
 
 
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
 
[http://www.developer.nokia.com/Design/ 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.
 

Latest revision as of 07:36, 19 June 2012

Archived.pngArchived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

This article has now been incorporated to the Porting to Qt Library

Article Metadata
Compatibility
Platform(s):
Symbian
Article
Created: User:Jros (26 Apr 2010)
Last edited: hamishwillee (19 Jun 2012)
This page was last modified on 19 June 2012, at 07:36.
116 page views in the last 30 days.
×