Tell-all explores the Wii U's development problems

[wraggster]

http://o.aolcdn.com/hss/storage/adam/1ea73899d25bdbe3541df58e918d4c23/nintendo-wii-u-new-logo.jpg (http://www.engadget.com/2014/01/12/tell-all-explores-wii-u-development-problems/)It's no secret that some game developers dislike the Wii U (http://www.engadget.com/wii-u-review/nintendo-wii-u-review/) -- performance issues (http://www.engadget.com/2013/05/08/ea-frostbite-nintendo-wii-u/), limited internet features and relatively slow console sales (http://www.engadget.com/2013/10/30/nintendo-2-million-3ds-sold-q2-2014/) have made it tough for companies to justify support. But have you ever wondered what, exactly, went wrong? Wonder no more, as an anonymous developer has just shared (http://www.eurogamer.net/articles/digitalfoundry-2014-secret-developers-wii-u-the-inside-story) many of the gritty details with Eurogamer. The insider claims that the sluggish CPU has been a concern since the beginning, and that the programming tools (not to mention feedback from Japan) have been sub-par. Nintendo's inexperience with online services is also very clear. The company created chaos for Wii U developers with network code that only arrived at the last minute (http://www.engadget.com/2012/11/17/psa-day-one-patch-wii-u/), and a key team hadn't even tried PlayStation Network or Xbox Live before the Wii U's launch. Price cuts (http://www.engadget.com/2013/08/28/nintendo-wii-u-price-drop/)and high-quality first-party games (http://www.engadget.com/2013/06/11/super-mario-3d-world-wii-u/) have helped Nintendo since then, but the source suggests that the firm can only do so much to court third-party developers entranced by more powerful (http://www.engadget.com/2013/11/14/sony-playstation-4-review/) hardware (http://www.engadget.com/2013/11/20/microsoft-xbox-one-review/).

http://www.engadget.com/2014/01/12/tell-all-explores-wii-u-development-problems/