By using this site, you agree to our Privacy Policy and our Terms of Use. Close
padib said:
....

Last year we also started a project to integrate the architecture for our future platforms. What we mean by integrating platforms is not integrating handhelds devices and home consoles to make only one machine. What we are aiming at is to integrate the architecture to form a common basis for software development so that we can make software assets more transferrable, and operating systems and their build-in applications more portable, regardless of form factor or performance of each platform. They will also work to avoid software lineup shortages or software development delays which tend to happen just after the launch of new hardware.

Some time ago it was technologically impossible to have the same architecture for handheld devices and home consoles and what we did was therefore reasonable. Although it has not been long since we began to integrate the architecture and this will have no short-term result, we believe that it will provide a great benefit to our platform business in the long run. I am covering this topic as today is our Corporate Management Policy Briefing.

So basically a unified developer API and a unified OS with scalability built-in.

"more transferrable" and "more portable" doesn't mean no extra work. 

assets can be transferred so you aren't starting from scratch but that doesn't eliminate platform specific optimizations.  it doesn't eliminate platform specific QA.

engine scalablity != game scalability.