What are the six key areas for enterprise mobile architects in 2014?

A report published today by enterprise software provider Verivo has revealed the six big considerations enterprise architects need to take into account when developing apps.

The survey, which was conducted in the first quarter of this year and spoke with enterprise architects at Global 2000 companies, came to the conclusion that the enterprise mobility space is growing and, as a result, influencing what architects and developers are doing.

The report’s advice was part pragmatism, part common sense:

  1. Leverage data from back-end systems as efficiently as possible: Verivo notes that the mobile landscape is becoming increasingly strategic – with multiple devices, apps and systems, integration with back-end data sources is key. “As mobile needs evolve, organisations need the flexibility to combine data and transactions coming from constantly changing back-end systems,” the report notes.

  2. There’s more and more requirement for working offline apps: The report notes that adding offline capabilities to an app can more than triple its development complexity, while four in five (78%) of survey respondents say they’re planning to build apps with offline support in 2014. Verivo sagely adds: “As the requirement to have more data locally expands, the need to have a hardened mobile client infrastructure expands as well.”

  3. An open mobile infrastructure is key: An open infrastructure is indeed vital, especially if you’re building on top of your existing IT software, the report warns. 86% of those polled said they plan to do just that. “With the growing strategic role of mobile, IT has recognised the need to build out an open mobile infrastructure that leverages its existing investments while providing for the unique needs that mobile apps demand,” the report states.

  4. Plan for a wide array of multi device and multi OS apps: Four in five (78%) survey respondents claim they are “committed to supporting a wide range of employee, partner, and customer-owned apps that run across multiple operating systems.” The report says that, despite the deploy once, run anywhere nature of HTML5, it’s only exacerbated this problem for enterprise architects.

  5. Move beyond the traditional MEAP with an open and flexible platform: This one feels like a summation of the other four, but it’s worth repeating. As mobile technology becomes mainstream, developers are proficient and there is plenty of support available, the last thing enterprises want is a closed platform.

  6. Don’t make companies jump as the price points jump: “The majority of enterprises require predictability in their infrastructure costs,” the report advises, adding that pricing structures based on the type of app – B2C v B2E – is just vendors being greedy.

“The emergence of BYOD policies, coupled with enterprise-grade security requirements and ‘always-on’ user expectations require today’s enterprise architects to plan for and develop apps that account for the rapidly evolving enterprise mobility space,” the report concludes.

But do you agree with its verdict?

Related Stories

Leave a comment


This will only be used to quickly provide signup information and will not allow us to post to your account or appear on your timeline.