•OpenGL ES 1.1 and OpenGL 2.0 (> iPhone 3GS, iPod touch third gen, iPad) support •Math library that supports floating-point calculations with an interface very similar to the D3D math library •Support for numerous texture formats including the PowerVR 2-bit, 4-bit and normal map compression formats •Support for PowerVR's POD (Scene and Meshes), .3DS and .blend file formats •Touch screen support •Accelerometer support •Text rendering to support a basic UI •Timing: several functions that can replace rdstc, QueryPerformance etc. •Profiler: industry proven in-game profiler •Resources streaming system •Bullet SDK support (for 3D Physics) •Audio engine with OpenAL support •Networking with the ENet library •Industry proven memory manager from http://www.fluidstudios.com

* Weinre reuses the user interface code from the Web Inspector project at WebKit * Weinre does not make use of any 'native' code in the browser, it's all plain old boring JavaScript. * Because weinre doesn't use 'native' code, its functionality is limited. For instance, source level debug of JavaScript is not easy. * Weinre supports 'remote' interaction, so you can run the debugger user interface on one machine and can debug a web page running on another machine. For instance, debug a web page displayed on your phone from your laptop. * Because weinre supports 'remote' interaction, multiple debug clients can be debugging the same debug target at the same time. * One thing not different from Web Inspector is that the debug client user interface only runs on WebKit-based browsers.