You know what rocks, and which doesn't get nearly as much attention these days, vis a vis mobile app development? Using a single game engine for real business

You know what rocks, and which doesn't get nearly as much attention these days, vis a vis mobile app development? Using a single game engine for real business apps, and then shipping those apps on every platform the game engine supports. Sure, you maybe have to do a bit more work to get a data entry field up on the screen - but you only have to do it once and you've got the same, consistent, agreeable (assuming you design it right) interface across all supported platforms. This isn't the same as using browser-based frameworks to accomplish the same thing. What I mean is, a game engine that provides equal access to the rendering and input event pipeline across the board. Its the native-framework dance that is killing mobile apps. The time spent grok'ing one Android SDK release, only to have to do it all over again just to keep your app current and constant on the platform. To a lesser degree its the same with iOS. But, if you take sufficient responsibility for the engine such that you're really targeting GLES and an event queue, you can produce amazing apps that run everywhere. This is the promise that needs to be fulfilled going forward. We don't need more apps that just look the same, yet take up infinite resources and attention just to stay in place. With a game-engine approach, app developers can actually differentiate themselves again - and the good ones, the really good ones, produce really good apps. Think about this some time: the most-shipped, most-used apps on any of the mobile platforms are those that, pretty much, eschew tight integration with the vendor-provided frameworks and instead bring their own to the party. This will get traction as more and more devs start to understand just how far you can take your modern engine these days .. and those engines are becoming their own OS in their own right, anyway ...