Codename One
 | This article may rely excessively on sources too closely associated with the subject, potentially preventing the article from being verifiable and neutral. (June 2013) |
| File:Codenameone New Logo.png | |
 Codename One Hello World App Screenshot | |
| Original author(s) | Shai Almog, Chen Fisben |
|---|---|
| Developer(s) | Shai Almog, Chen Fisben, Steve Hannah |
| Stable release | 3.2.5
/ December 7, 2015 |
| Written in | Java |
| Operating system | Android, BlackBerry, iOS, Windows Phone, Windows 8, Mac OS |
| Available in | English |
| Type | Application software |
| License | Open Source |
| Website | www |
Codename One was created by the co-founders of the LWUIT project (Chen Fishbein and Shai Almog) and first announced January 13, 2012.[1][2] It was described at the time by the authors as "a cross device platform allowing you to write your code once in Java and have it work on all devices specifically: iPhone/iPad, Android, Blackberry, Windows Phone 7 & 8, J2ME devices, Windows Desktop, Mac OS, and Web. The biggest goals for the project are ease of use/RAD (rapid application development), deep integration with the native platform & native speed."
Codename One took the LWUIT platform abstraction and extended it by adding a simulator and a set of cloud based build servers that build the actual native applications from the Java bytecode.[3]
Architecture
Developers using Codename One build their app using Eclipse, NetBeans or IntelliJ IDEA, they need the Codename One plugin to be installed on either IDE.[4] Applications can be created either via the GUI builder tool or via code using standard Java 5, running/debugging the application is possible via the standard IDE tools and the Codename One simulator.[5][6]
To build a native application developers sign in/register to the Codename One build server and send a build to the cloud based build server. Then they can download the native app from the build server to run on the device/submit to the store.[7] Since the build server performs static translation of the code into a native application, it is no longer required after the application has been compiled.[8][9]
Codename One also supports the ability to use an offline "in house" build cloud which removes the usage of Codename One build servers completely.[10] This is important for governments and agencies which have anti-cloud policies.
Native
The developers of Codename One define it as a native platform but clarify that native widgets are usually not used to render the user interfaces of Codename One applications, this allows for great portability but has also come under fire by some critics of the lightweight approach.[11]
Open Source
The Codename One project is a combination of Open Source and SaaS. Most of the client side code is open source including the iOS, Android, Windows, JavaScript, RIM & J2ME ports.[12] The server build code and the Codename One LIVE! tool are proprietary.[13]
Community
Codename One claimed 200,000 downloads of its SDK as of release 1.1 in May 20, 2013.[14] It has since released version 2.0 and is claiming 50MM applications installed on devices.[15]
References
- ^ http://codenameone.blogspot.com/2012/01/what-is-codename-one.html
- ^ http://www.scribd.com/doc/95684851/Codename-One-Developers-Guide
- ^ http://stackoverflow.com/questions/10639766/how-codename-one-works
- ^ http://www.codenameone.com/download.html
- ^ http://www.codenameone.com/how-do-i.html
- ^ http://stackoverflow.com/a/10646336/756809
- ^ http://www.codenameone.com/build-server.html
- ^ http://codenameone.com/faq.html
- ^ http://stackoverflow.com/tags/codenameone/info
- ^ http://www.codenameone.com/corporate-server.html
- ^ http://www.codenameone.com/blog/understanding-peer-native-components-why-codename-one-is-so-portable
- ^ http://codenameone.com/faq.html
- ^ https://github.com/codenameone/CodenameOne
- ^ http://www.sbwire.com/press-releases/with-200000-sdk-downloads-mobile-development-platform-codename-one-announces-version-11-253990.htm
- ^ http://www.codenameone.com/