Myths: FeedHenry on enterprise app development


FeedHenry debunks false beliefs and provides viable solutions regarding mobile development across the enterprise

Enterprise mobile app platform provider, FeedHenry, has analysed customer data and industry RFPs from organisations with more than 1,000 employees and identified five myths surrounding the building of enterprise mobile apps in today’s mobile-first world.

FeedHenry identified the following common pain points:

Myth #1: Enterprise apps take at least six months to develop and deploy

Industry received wisdom dictates that apps, especially those designed for enterprise, can take at least half a year to build and launch. With some organisations requiring anywhere from 10 to 100 apps to serve different business units, the time required to build apps can appear prohibitive. However, the right mobile platform can halve app development time to just 60 to 90 days. The key is to reuse code and backend services where possible in order to speed integration.

Myth #2: Data is king, but it’s too complicated for apps to access legacy systems

Enterprise organisations that have already made large investments in systems, such as ERP, are hesitant to develop mobile apps that cannot seamlessly plug into existing mission critical technologies. On average, a suite of enterprise apps connects to between two and six backend systems and APIs, including Sharepoint, Oracle, MySQL and SAP. Because two in three of these backend systems do not have accessible APIs, this can slow down the development process or make mobile apps unusable. Using an enterprise-grade mobile backend as a service (MBaaS) with an API infrastructure solves this issue by enabling legacy systems to be easily accessed by mobile devices.

Myth #3: Mobile app developers must keep up with a myriad of coding languages and frameworks – it’s impossible

Learning new development languages in order to build individual apps for each device platform can be tedious, and for some enterprises entails constantly hiring fresh developers with different skill sets. According to Forrester, when creating hybrid cross-platform apps, developers often employ as many as 10 different coding languages for enterprise app development projects. Common coding languages required include HTML5, JavaScript, Objective C, C#, Sencha Touch and Node.js. and these don’t even include languages proprietary to traditional MEAP platforms. To simplify development, developers can use mobile app platforms using a ‘Bring Your Own Toolkit’ approach that allows them to use the languages and toolkits they are most comfortable with.

Myth #4: Enterprise apps are always data-heavy, placing high loads on handsets and backend systems

The best mobile app platforms take large amounts of data from the backend and transmit a small filtered set of data to the handset, reducing overall demands. For each enterprise app session, the size of data transferred for each app should be less than 1MB.

Myth #5: Having a Chief of Mobility is the best way to handle company-wide app development

This myth assumes that one central figure will successfully oversee app development and deployment across the enterprise. In reality, the average enterprise mobile app development project requires at least 20 personnel, including business heads, developers, project managers, IT and employees. By collaborating and using the same technology standards and requirements, a Mobile Centre of Excellence or Mobile Steering Committee can guide mobile projects across multiple business units without creating new silos.

Commented Cathal McGloin, CEO of FeedHenry: ‘Today’s technology allows for the swift creation of apps without vendor lock-in. Businesses should take advantage of the new technologies at their disposal. Agile, open, collaborative and powerful cloud-based mobile application platforms now render obsolete long-held notions around lengthy and complex app development and deployment.’


About Author

Comments are closed.