Google has built a prototype Android smartphone that can learn and map the world around it. The device comes from a new initiative called Project Tango, and it’s ready to get the phone into developers’ hands to see what the technology is capable of. Google says that the phone will learn the dimension of rooms and spaces just by being moved around inside of them — walking around your bedroom, for example, would help the phone learn the shape of your home. The hope is that by creating a robust map of the world, Google’s phone could eventually give precise directions to any given point that needs to be reached.
via The Verge.
The vitriol spews on a daily basis. HTML5 or native apps? Each side is well armed with arguments and data to prove their points. This fight, destined to go on for a long while, masks some of the real problems that enterprises are facing when it comes to mobile applications. Do you have the right backend architecture for a mobile world? The right business analytics? Enterprises, brands and developers need to put their houses well in order before even beginning to answer what type of code an app will be built in.
HTML5 Or Native? Wrong Question
Most mobile discussions to-date have focused on the explosion in devices and operating systems, and the challenge of building great apps for a multi-platform world. This has given rise to the latest round of techno-religious wars, with the HTML5ers on one side and Nativists on the other.
Lost in all the shouting is a much bigger challenge—in fact, two challenges. First, the traditional Web architecture that undergirds most enterprises is rusting. Mobile is stressing the way these architectures feed data to applications, as well as their mechanisms for performance and scale—the technical equivalent of a bridge collapse waiting to happen.
The debate actually precedes the first app store to hit volume.
Should you build mobile apps in native code on each platform, or should you build them in cross-platform code, such as HTML5? Increasingly, however, developers are side-stepping that debate and just voting for whatever makes sense in each individual circumstance, according to a survey of 3,500 developers, CIOs, and CTOs. That’s a bit of a change from last year, when 94 percent of developers were betting on HTML5 to win.
In fact, 40 percent of developers have started building native, only to switch to HTML5, and 31 percent have started building cross-platform, only to switch to native.
“Developers … are quickly realizing that there is no ‘one-size-fits-all’ solution for their mobile development process,” Todd Anglin, a EVP at cross-platform development toolmaker Telerik said in a statement. “The choice between native and hybrid approaches is dependent on business needs, app requirements, developer skill, development timeline, and other factors.”