Master templates allow for the speedy development of powerful single-scope applications while keeping maintenance efforts centralized and transparent. This quintessential feature of the Betty Blocks platform enables organizations, vendors, and platforms to rapidly deploy custom versions while ensuring consistency, security, and efficiency across the board.
Benefits of using master templates:
Create custom app versions derived from a master template
Centralize maintenance and security efforts
Deploy, merge, and edit changes from a single source
The goal of master templates is for organizations to balance out their need for customization while maintaining the strength of their core product offerings. Development teams are encouraged to utilize the master templates to create bespoke solutions rapidly while retaining the ability to add custom features such as branding, integrations, workflows, or other capabilities. By standardizing application design and logic to one single source, maintenance efforts are entirely centralized.
Duplicate a master template to create instant child applications. Changes can be pushed to child applications from the master template.
Child applications can sport custom themes created from the Theme builder without overriding the master template.
Add custom features, branding, actions, workflows, and integrations to child applications to create tailor-made solutions.
Be able to assign user roles, permissions, and access controls as needed per child application in line with organizational structures.
Changes can be deployed across all child applications. Import/Export options allow for seamless sandbox merging and cloud deployment.
Standardized master templates allow for speedy and cost-efficient maintenance and updates across all linked products.
When creating child applications, developers can duplicate the assigned feature traits contained within the master template. These commonly include front-end-facing components, such as interfaces and input fields, as well as pre-built application logic and back-office functionalities. Depending on end-user requirements, custom connectors can be added to the application to communicate with data from the desired source.
Moreover, default permissions and access controls can be configured per child application to align with an organization’s security policies. By eliminating the need to write boilerplate code on a foundational level, skilled developers spend less time on repetitive tasks and can focus more on customization and improvements to their products.
With master templates, both security and compliance are cemented into any application from the get-go. By implementing pre-defining the required security within the master template, any child applications will bear the same configurations. This is especially helpful when citizen developers wish to create an application that is compliant with industry standards. Access controls such as SSO and 2FA can also be standardized so that they apply to all subsequent applications made from the master template, significantly reducing the risk of data breaches or unauthorized access.
