Android ndk for both arm and intel how to#
Android ndk for both arm and intel software#
Android ndk for both arm and intel code#

We need to build better tools and instruction sets so they can move over to parallel programming. So if developers are creating their applications in serial, it will be like having 50-lane freeways but only allowing one car on them at a time. At the recent Intel Developer Forum show, Intel Chief Technology Officer Justin Rattner talked about the coming of 50-plus core microprocessors. Increasingly we are seeing multicore chips on desktops and mobile devices. What can Intel and AMD do at the chip level to make it easier for developers to port and scale applications down to mobile devices?ī.D.: We can make things like threading applications easier.

Android ndk for both arm and intel code#

If developers are going from a 4-inch device to a 10-inch, to a 60-inch TV for their applications, they need to consider what core-based templates they need for the UI that they can easily code to. They should look for ways to write their code once and then get it packaged and compiled for each different form factor. What sorts of improvements are most needed in these tools?ī.D.: If you are looking at an IDE or SDK for a mobile platform, developers should look at ways to emulate applications across different devices.

Android ndk for both arm and intel software#

So the challenge for the application developers is now thinking about your software as sort of a utility application. But they don’t think about mobile users and how they are in and out of applications quickly.

Android ndk for both arm and intel how to#

If you are accustomed to developing applications on low-end Pentium-based computers all the way to a core i7, they know how to scale that type of application across the spectrum of hardware. Once legacy apps are ported over, how big of a problem is it to get them to scale well on mobile devices?ī.D.: Legacy application developers have an advantage in this regard, compared to mobile-applications developers. You are seeing advances in things like HTML5 that allow you to auto-build your experience based on the screen size of the device. Some development languages are getting better. I think there are tools that are well-designed for very specific platforms or languages, but you aren’t seeing the tools that make it easy to scale down an application for a particular form factor.

Are there enough adequate tools available to get this sort of job done, or are they still lacking?ī.D.: The tools have a way to go, to be honest. Mobile app developers have an advantage over the legacy software developer when it comes to designing apps that work well for mobile devices, as they have more experience and more of a focus on the mobile use-case experience. It may be more a user-experience challenge than an engineering one. Once you understand technically what it can do, you can scale the experience you want for that device. What is the most import thing for developers to keep in mind when porting legacy desktop apps to mobile devices?īob Duffy: First, you must understand what the capabilities are of the device you are porting to. We talked to Bob Duffy, the community manager for the Intel AppUp Developer Program, about what some of those technical factors are and what advice he has for those developers who commit to such projects. There are a number of technical factors to take into consideration before developers can even begin that process. With sales of smartphones and tablets growing at exponential rates, third-party and corporate developers are looking for ways to not only create new applications for these devices, but also port legacy applications over.īut porting applications and, as importantly, properly scaling legacy apps to work on these new platforms is easier said than done.