Development Principles

In addition to the rules laid down in this section, all apps developed for Bayer must conform to the relevant regulations and additional specific guidelines. You must also check whether there are any legal regulations relating to apps in your country that must be complied with. 


Apps must conform to strict security and data protection requirements.


Apps must have a clear release and update cycle that includes bug fixes and updates.


It is recommended that apps with a lot of content have a two-stage installation process with the app downloading additional resources as required.


If access to particular features of a mobile device (e.g., camera, address book or network) is required, then the user must be informed.


If you are intending to compile usage statistics, then you will need to integrate relevant packages within the development process.


All apps must be submitted to the Business Services Mobility Engineering for publication.



If your application requires access to Bayer informational systems then consideration must be given to connectivity: secure, reliable and fast backend connections from mobile devices cannot be taken for granted. There are two main approaches: direct connections and middleware.


Direct connections

Direct connections are suitable for simple access to single systems using existing APIs but can quickly become complicated if several systems or services such as logging are required.



Middleware is suitable where robust connections to multiple systems are required. For internal apps you can use either the existing Kony or SAP SMP solutions or develop your own custom middleware.