Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Your App Developers and Designers Could Be At War

DZone's Guide to

Your App Developers and Designers Could Be At War

Here's how to identify the signs and keep the peace.

· Mobile Zone
Free Resource

Download this comprehensive Mobile Testing Reference Guide to help prioritize which mobile devices and OSs to test against, brought to you in partnership with Sauce Labs.

Front-end app development has turned into a battle zone between back-end developers in technology groups, and designers in marketing and user experience groups, warns a recent report by Forrester analyst Anjali Yakkundi. But it needn’t be that way — the report has solid advice for simple steps you can take to make peace, and improve your apps’ usability.

The report, titled Brief: The Latest Battleground Between Designers And Developers Is Front-End Development says that the problem has gotten worse in recent years because an increasing number of designers have development skills, and more developers have design training.

There’s another reason the issue has come to the forefront recently: low-code mobile application development platforms make it easier for non-programmers to make changes to an app’s presentation layer. That makes it simple for not just designers, but other non-developers to make changes to apps.

On the one hand, having designers and developers fight over control of an app’s interface is a good thing. It means that the groups are highly engaged, care about the app’s success, and that design and development expertise has become spread throughout an organization. But that kind of in-fighting can also sap an organization’s energy, hurt productivity, and lead to poorly designed apps that represent too many compromises between groups, instead of apps built well for the specific jobs they are supposed to do.

Solving the Problem

The report has solid advice for solving the problem. For a start, it says that the design and development groups should each be responsible for different parts of front-end design, depending upon the groups’ expertise and the apps’ requirements. For example, it suggests, “If the business starts off with designers well versed in modern front-end languages, they should take the lion’s share until technology management staffs up on front-end devs trained in design thinking.”

Ultimately, the development group should be in charge of those elements of the design that are primarily transactional and interactive, and typically require a knowledge of standards, performance, and testing. The design and marketing group should be in charge of elements that are more time-sensitive, such as for campaign launches, where performance isn’t a concern, and that require a deeper understanding of design techniques. Overall, developers should be in charge of apps with higher technical needs.

Beyond that, enterprises should work to bridge cultural divides between the groups; and they should look to hire new talent well-versed in both development and design so they’re able to take on new roles within the organization, such as creative technologists or design engineers. The report also recommends building cross-functional product teams composed of both designers and developers. Also important is using highly agile development tools that can be used by both developers and designers.

To read more Forrester analysis of mobile app development trends, click here.

To read a recent Solutions Review article about agile development, click here.

To access the full report on the Forrester website, click here.

Analysts agree that a mix of emulators/simulators and real devices are necessary to optimize your mobile app testing - learn more in this white paper, brought to you in partnership with Sauce Labs.

Topics:
design ,develop

Published at DZone with permission of Amy Groden-Morrison, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}