Device proliferation has driven developers to seek alternatives to the high-performing but restrictive native app....
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
As devices continue to multiply and evolve, it has become increasingly problematic to build an app only supported by one operating system. Hervé Mischler, user experience designer with SAP, has been working on a responsive application design project for more than a year. "We tried to look at what's coming between all these platforms and we created our own visual language; our own UI [user interface], that will sit perfectly on any device."
Mischler offered advice to developers interested in breaking into responsive app design, discussed advantages and drawbacks, and recommended when it might be preferable to go native.
The approach to building a responsive application is very different from building a responsive website. It is, in fact, the opposite. Mischler explained that apps are designed for mobile first and then extended to tablets and computers. Since a mobile app is more precise and task-oriented, the original design is more complex, he added. "It's more work at the beginning because you have to anticipate all the use cases, all the different scenarios; but, on the other hand, you really have to simplify how the applications are working." The result, he said, is better apps for everyone, on every platform.
This backward approach to app building will likely be a challenge for developers accustomed to more practiced development methods, Mischler warned. "The traditional way to design websites is to design pages, but when it comes to responsive Web applications, you have to think in terms of components -- reusable components." He likened these components to bricks that operate as the application's building blocks, intended to become buttons, input fields and so on -- all adaptable to device specifications.
According to Mischler, many developers make the mistake of thinking in terms of pages and wind up with iPhone-sized interfaces on the computer screen or computer-sized input fields on the iPhone. "At the end it's very static whereas it should be really dynamic and change depending on the constraints of the screen."
It is also important to note that responsive apps' relative youth means a reliable set of best practices has not yet been implemented. "It's so new that nothing has been decided. The Web community spends a lot of time solving a lot of responsive Web design problems and there are some new HTML specifications coming out to solve those issues, but it's more complex when it comes to apps." However, Mischler predicted these issues are the result of immaturity and will sort themselves out over time as responsive apps become more widely adopted.
In any case, responsive app development is a valuable skill for designers and developers to acquire. Mischler's opinion on this point was succinct. "Platforms die." But the Web, he added, is sticking around for a long time. If developers want to build apps with staying power, they had better keep to HTML.