Is BYOD really a developer problem?

Is it fair to refer to the term Bring Your Own Device (BOYD) as “hackneyed” or even over-used, already?

Given the inexorable rise of consumer-driven IT adoption, there really isn’t much getting away from this phrase — not today, not next week and not next year.

But who’s problem is BYOD? Purchasing managers, security managers, networking managers or other.

Gartner has stepped aside from its dogged focus on Magical Quadrangles for just a moment and said that BYOD is a developer issue.

So is this worthy comment, or worthless spin of the (no doubt distinguished) analyst variety?

Gartner says the key decision about BYOD is one of applications architecture and solutions design.

“Designing your applications to meet the demands of BYOD is not the same as setting usage policies or having strategic sourcing plans that mandate a particular platform,” said Darryl Carlton, research director at Gartner.

“BYOD should be a design principle that provides you with a vendor neutral applications portfolio and a flexible future-proof architecture. If the applications exhibit technical constraints that limit choice and limit deployment, then the purchasing policy is irrelevant.”

If software application developers are no longer developing applications for deployment to an exclusive user base over which (in theory) it can exert standards and control, perhaps BYOD should indeed form part of the architectural programming consideration.

This development (if it is real) is leading to what the analyst firm has called “global class” computing — an approach to designing systems and architectures that extends computing processes outside the business and into the cultures of the consumer, mobile worker and business partners.

It’s not a bad suggestion — certainly better than a Magic Roundabout or Quadrant any day of the week.