Skip to main content

 

 

 

 

Template:OutSystems/Documentation_KB/Breadcrumb_New_Layout

 

 

Template:OutSystems/OSLanguageSwitcher

 

 

 

OutSystems

Building mobile apps with multiple independent teams

Template:OutSystems/Documentation_KB/ContentCollaboration
  • Edit
    Collaborate with us
    Edit this page on GitHub
  • This series of articles helps you on providing guidelines and best practices on how you can leverage the power of having multiple independent development teams working on the same mobile apps, avoiding common mistakes and maximizing their productivity.

    What’s the challenge?

    As you know by now, there are several differences between developing a traditional web and a mobile application in OutSystems.

    First of all, the mobile application lifecycle is completely different. There is no preparation, but there are several events to fetch data or initialize variables. The mobile application has local storage to speed up common operations or to support offline navigation, which is an additional aspect to take into consideration.

    There are also several plugins to interact with device native capabilities as well as other user-developed functionalities.

    It has a dedicated JavaScript node that allows you not only to run any snippet you create, but also to use input and output parameters to send or receive information related with the code snippet.

    Several dedicated widgets are exclusive to the mobile version and were optimized for mobile usage.

    Also, the architecture of such applications must also be approached in a very different level.

    Having to deal with all this while having different teams developing, it's huge. That's why we recommend you to understand about:

    Besides this section we recommend checking the following resources:

    • Was this article helpful?