Native Code is Dead AKA Cross Platform Development with Unity3D
•Transferir como PPTX, PDF•
2 gostaram•2,476 visualizações
Unity3D provides the best solution for cross-platform development by supporting the most critical platforms with a native-like performance. It has a wide community support and allows accessing platform-specific features through native plugins. Porting a game from iOS to Android with Unity3D only required a few days of refactoring code and swapping plugins. The business model is also advantageous with reasonable licensing fees and no revenue sharing requirements.
Recomendados
Recomendados
Mais conteúdo relacionado
Semelhante a Native Code is Dead AKA Cross Platform Development with Unity3D
Semelhante a Native Code is Dead AKA Cross Platform Development with Unity3D (20)
Último
Último (20)
Native Code is Dead AKA Cross Platform Development with Unity3D
- 2. Native Code is Dead AKA Cross Platform Development with Unity3D Ralph Barbagallo Founder, FLARB LLC
- 4. 2001
- 5. 2007
- 6. 2008
- 8. 20XX…
- 9. Choosing A Solution • Most Platforms With Least Code • Licensing Model That Won’t Eat Margins • Broad Community Support
- 10. HTML5 • HTML5 Frameworks • PhoneGap • GameSalad • Game Closure, AppMobi, Ludei • HTML5 Still Sucks • Horrible Performance • Gated by mobile browsers
- 12. Cocos2d • Cocos2d-X • Straight C++ version of Cocos2d • Great 2D library, widely used • Amazing updates and support • No web support
- 14. Flash / Adobe AIR • • • • Flash isn’t dead! Use Flash, FlashBuilder, etc. AIR Native Extensions Flash game engines • Starling • Stage3D
- 16. Unreal Developer’s Kit • • • • Don’t need a Mac! Top of the line renderer 25% of revenue to Epic Weak platform-specific support
- 18. Other Options • Titanium Studio • Corona • GameMaker • Stencyl • Marmalade
- 21. Why I Chose Unity3D: Tech • Best support for critical platforms • Mobile (iOS, Android, etc.) • Web (NaCL, Web Player, Flash) • Desktop (Steam, Mac App Store, Win8) • Console
- 22. Tech • Native Plug-ins • Can support any platform-specific functionality • Amazon App Store • Google Play Game Services • Write your own native plug-in
- 23. Support • Awesome forums • Awesome feedback from support • Twitter!
- 24. Asset Store
- 25. Business Model • Flat fee per-seat (‘perpetual’) • Monthly Subscription • No rev-share
- 26. Brick Buddies
- 27. Camera Birds
- 28. iOS to Android with Unity3D
- 29. Plug-ins • Used mostly cross-platform plug-ins • Access platform specific features (IAP, etc.)
- 30. Platform Specific Code • Only spent a few days of re-factoring • Swapped out iOS plug-ins for Android • Runtime platform checks and #IF compiler directives • AndroidJavaClass!
- 31. AndroidJavaClass AndroidJavaObject activity = new AndroidJavaClass("com.unity3d.player.UnityPlayer").GetStatic<AndroidJavaObject>("current Activity”) mWindowManager = activity.Call<AndroidJavaObject>("getSystemService","window"); mConfig = activity.Call<AndroidJavaObject>("getResources").Call<AndroidJavaObject>("getConfiguratio n");
- 32. Screen Sizes • iOS has 3 aspect ratios to deal with • Made interface work in “safe zone” • For Android’s common 16:10 ratio, scaled NGUI interface to fit
- 35. Cross Platform Export Tools • Per-Platform Asset Settings • Compression settings • Filtering • Cache Server • Multi-Platform Toolkit • Build-time asset changes
- 36. In Summary • Best Business Model • Widest Platform Support • Best Community Support • Dead Simple Porting Process
- 38. Thanks! Email: ralph@flarb.com Twitter: @flarb Blog: www.ralphbarbagallo.com Site: www.flarb.com WeChat: ralphbarbagallo
Notas do Editor
- Who in this room is writing native code? You are all doomed.
- JUST NOW on Android – over 6 months later.
- Writing directly for Stage3D (even if a 2D game) may have the best performance. Others have had success with Starling.CrossBridge C++ to Flash.