[PDF] Mobile Development Tools: Categorized and Compared

With the market for mobile application development still maturing, the plethora of mobile development tools available to help address your enterprise app portfolio needs can be overwhelming. So, we took some time to really understand what tools are available, what categories they fall into, what stage of the development cycle they address, and what functions they perform.

The resulting reference architecture matrix (below) shows that you’ll need a complex chain of interwoven point solutions to achieve enterprise mobility. It also illustrates how a rapid app delivery approach can offer dramatic speed improvements with streamlined full life cycle simplicity.

We also took this reference matrix one step further and built a complete architecture reference guide to help our community gain a better understanding of the mobile development tool landscape. I invite you to take a look at our matrix and download the full eBook to see all the options available for your development organization.

Mobile development tools life cycle matrix

Download the Mobile App Dev Landscape eBook

Embed this infographic on your site:

About the author

Miguel Lopes

A passionate product owner, Miguel is focused on creating value for enterprise customers through business-focused technology. After 20 years in software in the US, Europe and South America, he is currently crossing the chasm for RADically faster technology that revolutionizes the creation and delivery of enterprise applications for mobile or web.


May I know what makes OutSystems unique from other Mobility Platforms? As I can see they are using same approach as others. Also they are not even recognized by e.g; Gartner for Mobile App.


Muhammad, as you correctly point out, there are several companies that follow similar approaches of providing a platform that covers multiple phases of the mobile application life-cycle. Analysts all group these tools under the term Mobile Application Development Platforms and there are several reports out there that talk about the different vendors, their approaches, and how they differ from one another. One of them is from OVUM and you can get a copy of it at http://www.outsystems.com/1/madp-decision-matrix-ovum/

In terms of OutSystems approach, I believe there is a combination of “features” that make it stand out from the rest. I think the biggest one is the fact that the iteration/change cycles are dramatically reduced. You can make massive changes to your applications and redeploy a new working version very quickly. This is supported by a lot of automation in terms of impact analysis and self-healing (to ensure the application continues to work flawlessly no matter how much you have changed it), and also in terms of the deployment process (which is really simplified and extremely robust to ensure the final app is working well).

For mobile applications, where user experience will make or break an app, you need to be able to deliver a new version of your app as soon as humanly possible. Given what I described above, I think OutSystems gives you a big competitive edge when it comes to supporting these fast iterations.

Hope this helps

Disclaimer: I am an OutSystems employee.

Ann Conrad

Adding onto what Michel said… OutSystems is unique from other Mobility Platforms in that it is not limited to just Mobility apps. Our Platform takes a “Develop Once, Deploy Everywhere” approach, so an app is developed once in the Platform and then deploys across iOS, Android, Windows Phone, and Web. You can read more about this major difference here: http://www.outsystems.com/platform/multi-channel-development/

Leave Your Comment