Kirin is a chimera. It is a combination of the native and the web.

Its promise is to reduce the cost of cross-platform app development, while not skimping on production quality.

It does this by re-using your app’s business logic, written in Javascript, which drives a native UI for each platform you target.

It is being used in several apps on Android, iPhone and Nokia, and is battle tested by both native and web developers.

Outline

This is essentially a “What’s new in Kirin”. Since it was first published last year, it has been enormously refactored and extensively worked on, for developer usability and extensibility.

This session goes into that new development.

Although this is a “What’s new” it does not need any prior knowledge of Kirin.

There will be some codez (but not a lot).

Requirements

Projector.

Speaker bio

James is the principle architect and beneficial dictator for life of the Kirin project. He has been developing mobile apps for four years, and loves the constraints that small screens and small machines bring.

He conceived of the idea when everyone thought it was just crazy talk, but he went ahead anyway. Now the approach is hailed as “Obvious” and “Merely evolutionary”.