Feedback

Game developer loses £10,000 on Windows RT

BusinessNews
, 07 Dec 2012News
Game developer loses £10,000 on Windows RT

Paul Johnson, a high level executive of UK games developer Rubicon, has criticised Microsoft for not supporting a Windows RT port of the successful mobile title, the Great Big War Game. Rubicon saw a return of just £52 from an estimated R&D spend of £10,000.

Johnson went on to a post a blog which lamented on the lack of cooperation his company received from the software giant.

“Microsoft has confirmed they will not give us any promotional features or help us with visibility in any way,” wrote Johnson.

“If you're familiar with their new store, this means our app is forever consigned to the garbage bin, presumably earning us less than £52 a week in future. Even if that rate is sustained, it will take just under two years before we recoup the salary paid to the guy who did the port.”

He also stated that greater support is available from Microsoft’s competitors.

“Apple regularly promote our apps, Android regularly promote our apps. Even RIM (Blackberry) regularly promote our apps,” he added

“Firms our size need a bit of a leg up, and we go out of our way to show our gratitude to the above for helping us out in this way from time to time… even whilst there's almost nothing to promote, they will not feature our title for bizarre admin reasons.”

The Redmond-based company has since reached out to Rubicon, according to a blog update, with Microsoft now showing keen interest in the developer’s future endeavours.

“Microsoft has graciously decided work with us to iron out the problems and get us past this incident,” concluded Johnson.

The Windows RT platform is currently restricted to a handful of tablet devices including the Microsoft developed Surface, meaning that the port will cater to a small audience. However, an increase in dedicated apps production for the platform will be required to increase the Surfaces’ adoption rate which, according to Microsoft, has been moderate at best. 

Topics
blog comments powered by Disqus