In our system, apps and modules play crucial roles, but they serve distinct purposes and have unique functionalities. Below, we will explore the core differences between the two and what they mean for software development.
Purpose and use case
Apps are designed primarily for backend operations and administrative use, serving internal needs like appointment handling, resource management, customer data handling, and business process configuration. They target employees and internal users of a business, providing deeper administrative capabilities, such as configuring business operations and detailed reporting. Access to apps requires authenticated permissions, ensuring that only employees with these permissions can access and modify sensitive business information, apps and modules. In this context, apps are integral to maintaining and managing the internal infrastructure of a business.
On the other hand, modules are oriented towards frontend use, directly interacting with end customers. They provide booking functionalities, enabling customers to engage with the business, and schedule appointments or view available time slots. Unlike apps, modules target external users, focusing on intuitive and seamless interactions. Modules are lightweight, making them easy to use for customers, and they generally have an optional authentication process, centered around customer data and booking actions.
Installation and permissions
Apps
When an app is installed in an organization (via an appConfig creation), it gains access to that organization and bequests the same permissions across all its sub-organizations.
Employees who are granted access to the app will see it in the navigation and can interact with its functionalities. These permissions are managed through employeeGroup objects.
Modules
In comparison to apps, modules can be installed multiple times in the same organization, by creating a new moduleConfig. Different appointmentTemplate objects can be linked per moduleConfig, which can also have settings to be customized for multiple use cases.
Employees who are granted access to the module are able to change settings like the color of the background or the headline text color.
Modules have a simpler permissions structure and most interactions require no authentication. There is generally less complexity involved in accessing the module API compared to the app API.
Summary
In essence, Apps and Modules are both vital components in our ecosystem. Apps focus on internal processes and administrative functionalities, while Modules concentrate on customer interaction and external service delivery. With these distinctions, developers can make decisions on how to extend, integrate, or customize the system based on specific use cases.
Comments
0 comments
Please sign in to leave a comment.