Skip to main content

SAMO Mobile Implementation

Configuration specific for SAMO Mobile client application is included in metadata extension samo-mobile.xml. Other optional configurations can be included in light-forms.xml and protocols.xml.

If you want to upgrate your configuration from mobile.xml or mobile-workforce.xml to samo-mobile.xml, please, see Configuration migration to SAMO Mobile chapter.

⚠️ Warning: Configuration is common for both applications: SAMO Mobile for Android and LIDS Mobile for iOS. The applications are developed independently and are at different stages of development. It might happen, that particular functionality / configuration is valid only for one platform. Please, check the development plan for up-to-date information about finished / missing functionality. For LIDS Mobile for iOS there is still only mobile.xml configuration supported. It has common parts with samo-mobile.xml, but not all parts are supported in iOS app yet (you can see "Android only" warning at some chapters). light-forms.xml and protocols.xml are also not supported in iOS app yet.

Basic project definition of possible data used (feature types, attributes, codelists, relationships) is included in standard project model.

Privileges and access rights are controlled the same way as in LIDS by LIDS Security. Some types of LIDS Settings are also used in SAMO Mobile (e.g. templates for data layers, my places, etc.).

Displaying of feature attributes expects specific forms definitions:

  • light-forms.xml metadata extension can be used for defining mobile specific forms

  • model.xml - form definition can be used also in mobile app

    • assignedForm usage="mobileSimple"– form with a small number of attributes to be used mainly on the cards in the list of features

    • assignedForm usage="mobileFull" – form used to display attributes in detailed form - when no suitable light form definition for the particular feature type is found

See more about mobile forms logic in the Forms in mobile chapter.

Hint: There is a big usage of featureInfo in mobile app. There are many places in the application, where the featureInfo is displayed as a user readable feature identification. It is strongly recommended to define meaningful featureInfo in model.xml for all feature types that should be presented to the user in any feature list or feature detail in mobile app.

There are two main parts of the mobile implementation documentation: