Soundwave said:
Apple is apparently now going to put iOS and the same A8 processor in the iPhone/iPad into the next Apple TV ... which will then have hundreds of apps available for it quickly too. Apple could in this formula make 10 different devices. The whole point is this type of setup only works if you can share the apps. It doesn't mean shit if it was just an API that made programming a little more streamlined but developers still had to code specific apps for each platform every single time they wanted to make one app for the other. If Apple had done that, they wouldn't be as successful as they are now. Nintendo's current model of doing things is actually fairly insane ... they are trying to support two seperate hardware platforms with little/no third party support and are smaller than even companies like EA and Activision in work force. They can't continue to operate that way. Nintendo fans just can't see around that formula because they figure "well that's how its always been". Yeah that worked ... when games could be made by a staff of 10 people, and monster sized games like Mario 64 had maybe 40 person staff, and handheld market was nothing but cheap/watered down NES-SNES port jobs. Today even 3DS games have staff sizes of 80-100+ people and the 3DS is going to need replacing by something more in line with the Wii U/PS3 in power in short order. |
Again... None of what you have said really countered what I have said and what I gave as proof which always seems to be the issue everytime we talk... Iwata specifically said and gave those examples because having a common platform with various hardware on Apple and Android allows developers to program with common code... I even quoted him saying that... None of what he said on the other hand had anything to do with same games on both platforms
PC Specs: CPU: 7800X3D || GPU: Strix 4090 || RAM: 32GB DDR5 6000 || Main SSD: WD 2TB SN850







