Application and Module
In Lowgile documentation, app is the preferred user-facing term for the functional solution that people use. A Module is the technical object and context used to create and organize that application in Lowgile Studio.
App and Module relationship
Section titled “App and Module relationship”In Lowgile, an application is created as a Module. The Module provides a technical boundary for the application objects configured in its context, such as Screens, Entities, Processes, and User-Defined Configurations.
The distinction describes two views of the same solution:
- App describes the application as users experience it.
- Module describes the application’s technical implementation in Lowgile Studio.
The Module name also identifies the context used when referencing application objects. For example, when the Purchasing Module is the current context, This.PurchaseRequest refers to the PurchaseRequest object in that Module.
When to use app and when to use Module
Section titled “When to use app and when to use Module”Use app when describing the overall solution, its purpose, or what users interact with. Use Module when working with the technical implementation in Lowgile Studio, selecting a Module context, or discussing Module-specific configuration.
When both terms are needed, introduce their relationship once. Then prefer app unless the technical distinction matters.
Purchasing example
Section titled “Purchasing example”You build the Purchasing app by creating and configuring the Purchasing Module. As you continue through the tutorial, you create the Purchasing app’s Screens, Entities, Processes, and User-Defined Configurations in that Module context.