OGDC 2014: Cross Platform Mobile Game Application Development

Copyright (c) 2014 Eqela Pte Ltd. All Rights reserved.

Cross Platform Mobile Game Application Development

Markku Kero / Eqela

July 2014 / OGDC


Cross platform development tools

One codebase; target multiple platforms

Many existing tools on the market


“Cross platform tools do not work. Writing

native code is the only way.”


Commonly encountered issues

Large installer size

Excessive memory use

Low performance

Limited API access


ANOTHER COMMON SENTIMENT


WHY?


Source codetargeting a

specificplatform

Tool

Source / bytecode and

interpreter orVM for iOS

Source / bytecode and

interpreter orVM for Android

Runtime /Virtual

machine

(Java, JavaScript,Lua, Ruby, C#, ..)

A common cross platform tool

BROWSER

“virtual machine”


Operating system

Language interpreter / runtime

APIs and libraries Application code

A common cross platform toolArchitecture


A common cross platform toolArchitecture

Operating system

Language interpreter / runtime

APIs and libraries Application code Makes applicationinstallers bigger

Increases memoryusage

Reduces runtimeperformance

Applications can onlyaccess selected

parts of the native API

= INCREASED BATTERY USAGE


(Source: http://docs.xamarin.com/Android/Guides/Advanced_Topics/Architecture)


Another popular architecture

SourceCode in

HTML, CSS,JavaScript

Tool

C codeThat opens aBrowser andDisplays the

program

Java codeThat opens aBrowser andDisplays the

program

AndroidSDK

iOSSDK

“embed a web browser”

BROWSER


Commonly encountered issues

Large installer size

Excessive memory use

Low performance

Limited API access


The C/C++ approach

C++application

code

Tool

C++ classlibrary

SWIFT

BROWSER


C++ / bytecode combination

C++ code


THE APPROACH CAN BE

IMPROVED


HOW?


Programming language conversion

(Source code)

Small Installers Optimal memory useNo API access limitationsNative performance


Comparison: A “hello world” application

First approach (virtual machine / interpreter)Appcelerator: 8MB installer

Xamarin / Mono (Unity): 4MB installer

The “embed a web browser” approach:Phonegap / Cordova: ~300KB installer

The “source code conversion” approach:96KB installer


Programming LanguageTranslator


2D / 3D GAMESMOBILE APPLICATIONS

BUSINESS SYSTEMSWEBSITES / WEB APPLICATIONS

BACKEND SERVERSDESKTOP TOOLS / UTILITIES

AUTOMATED QUALITY ASSURANCE


class Main : LayerWidget{ public void initialize() { base.initialize(); add(LabelWidget.instance().set_text(“Hello World”)); }}

EqelaCompiler

LayerWidgetLabelWidget

Main.javaLayerWidget.javaLabelWidget.java

AndroidSDK

A sample Eqela application

Main.eq


class Main : LayerWidget{ public void initialize() { base.initialize(); add(LabelWidget.instance().set_text(“Hello World”)); }}

package mk.test;public class Main extends eq.gui.LayerWidget{

@Overridepublic void initialize() {

super.initialize();((eq.gui.ContainerWidget)this).add(((eq.gui.Widget)eq.widget.LabelWidget.eq_widget_LabelWidget_instance().set_text(eq.api.StringStatic.eq_api_StringStatic_for_strptr("Hello world"))));

}

public Main() {}

}

(EQELA)

(JAVA)


class AndroidHTTPGet{

public static bool execute(String url) {embed “java” {{{

org.apache.http.client.methods.HttpUriRequest hur =new org.apache.http.client.methods.HttpGet(url.to_strptr());

android.net.http.AndroidHttpClient hc =android.net.http.AndroidHttpClient.newInstance(“testing”);

org.apache.http.HttpResponse resp = hc.execute(hur);if(resp == null) {

return(false);}

}}}return(true);

}}

→ All platform specific features / APIsare accessible

Embedding other languages


SpriteKit

Sprite Engine R3D

→ NO TECHNOLOGY LOCK-IN


Thank you

[email protected]

www.eqela.com

mailto:[email protected]

http://www.eqela.com/

OGDC 2014: Cross Platform Mobile Game Application Development

Documents

Transcript of OGDC 2014: Cross Platform Mobile Game Application Development