Today, many companies looking to enter the world of enterprise mobile app development seemingly face a difficult development strategy choice: DIY tools vs. traditional enterprise mobile app development platforms (MEAPs). Choosing the right strategy for your enterprise can be a daunting task, especially when complicated by the influx of many business users within enterprises that want to participate in mobile development. In that case, the lowered skills barrier would make DIY tools an attractive choice, but the results of such tools are not typically enterprise grade, due to their lack of flexibility.
With that in mind, let’s take a look at the two options. It’s important to remember that both options have pros and cons, and either choice requires compromise. The options become largely a choice between flexibility and efficiency.
Erik Shermam from TechBeacon published an article on four pitfalls to avoid when building enterprise mobile apps. They are:
Bad user experience (UX)
Erik and I chatted about one of the pitfalls: slow app development.Enterprises today must deliver apps fast. Build the first version of the app within weeks if not days, get feedback and repeat. The traditional 12-18 months application development cycle no longer works today.
There’s a huge demand for mobile apps, and many IT departments can’t keep up, says Max Katz, head of developer relations for custom enterprise app developer Appery.io. But not only are corporate technology groups understaffed, many IT departments lack expertise in Android and iOS development.
Enterprises also have to rethink their design cycles. “They’re used to delivering apps that take 12, 18 months, maybe two years,” Katz says. “With mobile you can’t do that. You need to deliver apps very fast, I mean weeks. Some of them, maybe a couple of days.” This is particularly challenging when a company needs native apps for multiple platforms, which can mean parallel development tracks and teams.