Angular Material Toolkit for Building Beautiful Apps

No, BuilderKit doesn't include any custom primitive Angular components. Instead, it provides refined styles for the standard Angular Material components. These styles enhance the appearance of the existing components you already use, giving them a more modern and polished design without requiring any changes to the components themselves.

BuilderKit comes with its own theming system that is separate from Angular Material’s built-in theming. It supports both light and dark modes out of the box and can be customized to fit your brand colors. However, it does not integrate directly with Angular Material’s theming API, so you cannot use Material themes to change the appearance of BuilderKit components.

BuilderKit's theming system also allows changing colors at runtime, enabling dynamic theme switching in your application.

Not without significant effort. BuilderKit is built around its own opinionated styling system, which is a core part of the product. While you can customize and extend many aspects, replacing the design system entirely is not supported. The visual identity and consistency provided by BuilderKit’s styles are what make it work as a cohesive, ready-to-use frontend foundation.

Yes, Advanced Components are custom Angular components created specifically for BuilderKit. Some are written entirely from scratch and others are built on top of Angular CDK and Angular Aria. They provide real UI patterns such as sidebars, collapsible content and structured navigation that do not exist in Angular Material.

Advanced Components follow the same design system as the rest of BuilderKit. Colors, spacing and typography are fully aligned with BuilderKit’s theme. They do not use Angular Material’s theming API but instead rely on BuilderKit’s own tokens. Both light and dark modes are supported and theme changes work at runtime.

Yes, Advanced Components are more flexible than the styled Angular Material components. They are built in a composable way, so you can apply Tailwind classes, replace primitive parts and change spacing or structure where needed. They still follow a consistent design language but give you more room to adjust details or shape the layout for your app.

Blocks are pre-built, reusable UI sections that can be combined to create complete pages. They are designed to be flexible and adaptable, allowing you to mix and match different blocks to build the layout and structure of your application quickly.

Blocks are provided as standalone, single-file Angular components. You can copy the code for a block directly from the BuilderKit website and paste it into your project. Each block includes all necessary HTML, CSS, and TypeScript code, making it easy to integrate into your application.

Yes, blocks are designed to be easily customizable. You can modify the HTML structure, CSS styles, and TypeScript logic to fit your specific needs. Each block is built using standard Angular practices, so you can leverage your existing Angular knowledge to make changes.

Templates are complete application starters that include a set of pre-built pages and layouts. They provide a solid foundation for building specific types of applications, such as dashboards, admin panels, or e-commerce sites.

They do NOT come with any functionality or data integration. Instead, they focus on the frontend structure and design, allowing you to quickly get started with a well-organized codebase that you can then customize and extend to fit your specific needs.

Templates are provided as full Angular projects in the same private GitHub repository as the rest of BuilderKit. After purchasing, you can clone the repository and copy the template project into your local development environment. From there, you can run the project, explore the code, and start customizing it to build your application.

Yes, templates are designed to be used as starting points for real-world applications. They provide a solid foundation with a well-organized codebase and a cohesive design system. However, they do not include any functionality or data integration, so you will need to implement those aspects yourself based on your specific requirements.

Templates are regularly updated to ensure compatibility with the latest version of Angular and Angular Material. Updates may include bug fixes, performance improvements, and enhancements to the design system.

As part of your BuilderKit license, you will receive all future updates to the templates at no additional cost.

After purchasing BuilderKit, you can use the email address you used for the purchase to log in to the BuilderKit website. From there, you can connect your GitHub account and request access to the private repository. Once you accept the invitation, you will have full access to everything BuilderKit offers plus all future updates.

You can also access Blocks directly from the website, where you can browse, preview, and copy the code snippets you need.

Lifetime access means that with a single purchase, you receive ongoing access to BuilderKit, including all components, blocks, and templates. All future updates, improvements, and new features are included at no additional cost. Your GitHub repository access remains active indefinitely, so you can always pull the latest version as BuilderKit continues to grow.

Yes, BuilderKit can be used to build applications for clients or freelance projects. As long as you hold a valid license, you are free to use it across commercial work, including SaaS products, internal tools, and client deliverables. Each developer using BuilderKit must have their own license, unless covered by a team license.

No, a single purchase of BuilderKit grants lifetime access to all components, blocks, and future updates for unlimited projects. You can use BuilderKit across as many personal or commercial projects as you like. There are no project-based restrictions.

No, BuilderKit cannot be used in open source projects or public repositories. While it can be used in private or commercial client work, the license does not allow redistributing BuilderKit components, source code, or styles in any public, freely accessible, or open source form.

Yes, you can sell products you build with BuilderKit, such as SaaS applications, client projects, or commercial tools. However, you may not sell or distribute BuilderKit itself, or any parts of it, as a standalone product. This includes themes, templates, UI kits, or anything that exposes the source code, components, or styles for reuse outside your own application.

Yes, BuilderKit support is available through GitHub Discussions, where you can ask questions, report issues, and get help using the kit. We are actively involved, so you will receive direct responses alongside input from the community.

Support covers usage guidance and troubleshooting, but it does not include custom development or feature implementation.

All sales are final and non-refundable due to the nature of digital products and the instant access granted to BuilderKit’s private repositories.

Once access is provided, the full source code and assets become available, and access cannot be revoked. If you experience any issues or need help, our support team is here to assist and make sure you get the most out of BuilderKit.

Yes, we welcome feature requests and feedback. When reviewing requests, we focus on whether a feature provides broad value and aligns with BuilderKit’s overall vision. While we’re always open to ideas, we do not accept one-off or highly project-specific features that do not benefit the wider user base.

After a bug report is reviewed and confirmed, we prioritize it based on impact. Critical or app-breaking issues are addressed immediately. Other bugs are typically scheduled into the next release cycle and delivered alongside new features or improvements. This helps keep updates consistent while ensuring important issues are resolved without delay.

BuilderKit is built for long-term support. As the developer behind Fuse Angular, a project maintained for over a decade and trusted by more than 25,000 customers, I’m committed to bringing that same level of care and consistency to BuilderKit. The goal is to create a reliable, evolving toolkit that stays current with Angular and continues to grow over time.