Basic Components

Depending on your project, you will likely encounter some of the different types or componetents of a mos.configuration. All files within a configuration are of the file type JavaScript Object Notation or JSON for short.

The following pages contain the available components and a short description of their purpose. Each component is located within its own folder of you configuration and can hold one or multiple files. Please note that a component folder should be named accordingly for it to work correctly.

📄️ Asset

"A picture is worth a thousand words"

📄️ Client Template

The typicall mos. application consists of several views.

📄️ Config

There is a lot that your app can do, most of it can be set in the configuration. Despite the vast amount of actions, layers and

📄️ Database Tables

mos. offers a build-in SQLite based solution to persist data. Furthermore it allows you to define sources for tables that the app will automatically keep up to date.

📄️ Environment

You can define different environment variables depending on the environments you start your application in. These variables are replaced with their value at runtime. Typicall variables defined in environments are URLs for external third-party APIs (i.e. different environments could point towards the development and production API). Most of the time you will find an environment called default for production purposes and one called local for development on you local machine.

📄️ Event

Events are used to call actions from elsewhere in the app.

📄️ Font

The ./font directory can contain fonts which can be used in the configuration.

📄️ Layer Styles

There are some attributes that are repeated several times within a configuration, such as colors and fonts. To reduce redundancy, layer styles can be created. Their structure is based on CSS and they provide the possibility to set attributes to layers that meet certain criteria.

📄️ Layer Style Condition

As the name suggests layer style conditions apply to layer styles and can be used to control a layout and/or its behavior depending on different factors like device type or system settings (e.g. darkmode).

📄️ Layout

Understanding layouting is one of the first steps one needs to undertake, to create beautiful and functional mobile applications with mos.

📄️ Start Config

The start configuration is the starting point for the app. It tells the app which display type, layout, client template and named style to use on the app start.

📄️ Style

The ./style directory contains named styles that are used by the system to style views.

📄️ Translation

Translation files