PUBLIC ALPHABiztraak is now in public alpha. Share feedback
Biztraak
Marketplace
Templates Federated Apps Contributor Guide Contributor Getting Started Creating a Store Item Contributor Templates Template Store Deployment Strategies Billing Versioning

Creating Templates as a Store Contributor in Biztraak

As a Biztraak Store Contributor, you can package reusable project foundations for other teams. A useful template explains its requirements clearly and matches the workflows it actually supports.

Understanding Templates in Biztraak

A template in Biztraak provides users with a basis for creating their own apps by providing a pre-designed set of files. The files include configurations, code skeletons, and other necessary resources for a certain type of app.

What should Be Included in a Template?

A template should be comprehensive and provide a strong foundation for the user to start developing their app. The resources included in a template can vary greatly depending on the type and needs of the app, however, some common inclusions are:

  • Core code files generated in a suitable language
  • Configuration files
  • README files with instructions
  • Design assets, such as layout designs or UI components
  • UI/API Builder assets
  • Admin Pages (Federated Apps)
  • Any other useful assets or resources related to the specific type of app

Deployment Options

To cater to varying needs, such as cost and scale infrastructure, it's a good idea to design your templates with different deployment options:

  • Monolithic architecture: This is best suited for simple, lightweight applications. All components run within the same process, therefore it is generally less expensive to deploy such applications.

  • Microservices architecture: This is recommended when designing complex, large-scale applications. Each component runs in a separate process, perfect for when different components require different resources or technologies.

You can offer anything in between (inclusive) as part of your templates, enabling users to choose the right architecture for their needs.

Integration with Store Items

Templates can also be designed with the integration of other store items in mind, such as federated apps or addons. This creates a complete solution, resulting in convenience for the user and potentially higher adoption for your template.

Conclusion

Creating and sharing templates as a Biztraak Store Contributor allows you to contribute reusable starting points to the platform’s ecosystem. Publishing, pricing, and revenue options depend on the Marketplace capabilities enabled for the account and asset type. Follow the current contributor workflow and document the template’s requirements clearly.