BricksFly

BricksFly is easier to understand as a complete Bricks production toolkit than as a normal addon pack. It combines extra Bricks elements, workflow extensions, a no-code GSAP animation layer, full-site templates, hundreds of reusable sections, and copy/import tools. The appeal is consolidation: one product can cover several things a Bricks agency would otherwise solve with separate plugins and libraries.

Quick take

After going through the current elements library, section workflow, GSAP features, pricing documentation, FAQ, public repository history, and current vendor pages, the product feels most useful for a team building new Bricks sites rather than an agency that already has a mature stack of specialist addons.

The strongest parts are the animation-ready section library and the fact that the extra elements, extensions, templates, and GSAP controls are designed around the same Bricks workflow. The main risks are overlap, licensing dependence for animation features, and the current closed state of the WordPress.org package.

Best fit: BricksFly makes the most sense for Bricks Builder freelancers and agencies that want extra elements, workflow extensions, reusable layouts, and GSAP-powered interactions in one toolkit. A different option will usually make more sense for non-Bricks sites or mature Bricks stacks where specialist tools already cover the same jobs reliably.

The element library fills practical Bricks gaps

BricksFly currently promotes 30+ advanced elements, with the broader toolkit describing 45+ elements and extensions when both groups are counted. The visible element list includes advanced buttons, social icons, brand sliders, counters, progress bars, galleries, icon boxes, testimonials, team layouts, timelines, animated headings, off-canvas content, social sharing, post meta, several video components, image accordions, toggles, and draggable items.

What I like about that list is that many of the elements solve recognisable client-page problems rather than being minor variations of the same card. Video Story, Video Popup, Timeline, Image Accordion, animated headings, and the marketing/media elements are the sort of components that regularly appear in agency builds.

I would still keep the module list lean. Bricks itself already covers a lot, and the product lets you enable or disable elements and extensions. On a real project I would turn on only what the site uses, both to keep the builder cleaner and to reduce the number of moving parts the team has to remember.

The GSAP layer is one of the better reasons to add BricksFly

The public plugin description and vendor site position GSAP as a core part of BricksFly Pro. The toolkit covers ScrollTrigger-style animation, SplitText, parallax, horizontal scrolling, sticky/pinned interactions, smooth scrolling, image reveals, cursor effects, Lottie/SVG-oriented motion, preloaders, and preset-driven animation.

The 1.0.3 repository release is useful evidence of where the product is going. It added eight advanced presets including Cinematic Mask, Slice Shutter, Mosaic Depth, Liquid Clip, 3D Orbit Tilt, Zoom Tunnel, and Scroll Parallax, along with trigger modes for immediate play, hover, scroll, and scrubbed scroll. It also fixed front-end scale/stretch behavior and ScrollTrigger positioning around lazy-loaded images.

Those fixes matter more to me than the preset names. Scroll-driven animation often breaks when image dimensions change after load, so seeing a release specifically address lazy-loaded-image timing is a practical maintenance signal.

Templates and sections are where agencies may save the most time

BricksFly currently lists 30+ complete website templates and 500+ reusable Bricks sections. The section library covers common page structures such as heroes, services, features, pricing, testimonials, portfolios, FAQs, CTAs, headers, and footers. Sections can be moved into Bricks using live copy/paste, JSON import, or direct import.

The live copy workflow is the most interesting one for day-to-day agency work. Instead of downloading a template file, importing it, and cleaning up the result, you can copy a section into the Bricks canvas and continue editing it as normal Bricks content. The layouts remain editable for typography, spacing, colors, media, responsive behavior, and animation.

I would not treat 500 sections as 500 finished designs I want to ship. I would curate a smaller internal collection that matches the agency’s standards. A good library should make teams faster without making every client site look like it came from the same demo catalogue.

Builder Toolkit and All Access solve different problems

The pricing structure is clearer when you separate the two product levels. Builder Toolkit focuses on the Bricks elements, extensions, animation features, and workflow tools. All Access adds the full website-template and section libraries.

The current purchase guide lists one-site annual pricing at $39 for Builder Toolkit and $49 for All Access. Five-site pricing is $69 and $79 respectively, while the large 500-site plans are listed at $129 and $149. Lifetime All Access offers are also being promoted during the current launch period, so the checkout page should be checked before purchasing because promotions can change.

If I design every client project from a blank canvas, Builder Toolkit is the more logical comparison. If the agency wants a production library and copy-paste sections, All Access is the product that actually differentiates BricksFly from a normal addon bundle.

The annual-license behavior deserves attention before client deployment

BricksFly’s FAQ states that when a yearly license expires, the page content and imported templates remain, but GSAP-powered animation features stop working until the license is renewed. It specifically mentions ScrollTrigger, smooth scrolling, sticky elements, tickers, and other GSAP effects.

That is a significant operational detail. I would never hand off a client site without documenting it. If a hero, navigation experience, or important interaction depends on BricksFly animation, the annual license is not just an update/support subscription; it affects live behavior.

For that reason, I would either keep the renewal under agency management, use a suitable lifetime license where the terms fit, or make sure the client understands the renewal requirement before launch.

The WordPress.org closure should be investigated, not exaggerated

BricksFly has public WordPress.org release history and an official Wealcoder contributor record. Mirrors of the listing show version 1.0.3 with 10+ active installations at the time they were crawled. However, the current WordPress.org API reports the plugin as closed.

PluginSuggest therefore does not display old install, download, or rating figures as current Plugin Health data. A closed listing does not automatically mean the commercial product is abandoned: the vendor site, documentation, pricing, templates, FAQ, and current support materials remain active. But I would ask Wealcoder why the repository package is closed and confirm the supported installation/update path before standardising it across client sites.

That answer matters especially if a team originally planned to use the free repository build as the base plugin and BricksFly Pro as the companion.

Performance depends on keeping the toolkit modular

BricksFly says it loads assets only where used, and the public plugin documentation includes selective module controls and reduced-motion support. That is the architecture I would want from a Bricks addon because Bricks users often choose the builder specifically to keep output and dependencies under control.

Still, a modular plugin can produce a heavy page if the design asks too much of it. Smooth scrolling, video, several sliders, large imagery, multiple pinned sections, and continuous GSAP scrubbing can add up. I would test the busiest production layout on mid-range mobile hardware and measure interaction responsiveness, not only a clean desktop Lighthouse score.

I would also test the site with caching and script-delay settings enabled. Animation runtimes are particularly sensitive to scripts being reordered or deferred in unexpected ways.

The refund wording is not perfectly consistent across vendor pages

BricksFly advertises a 15-day money-back period, but the terms page lists conditions where refunds may not be granted, including some purchase-expectation and change-of-mind cases. Another promotional page describes the 15-day policy more broadly.

I would therefore read the current checkout terms rather than assuming every 15-day request is unconditional. This is a small detail, but it is exactly the sort of thing a good product profile should surface instead of repeating the shortest marketing version.

How BricksFly compares with specialist Bricks tools

The Bricks ecosystem already has specialist products for components, animation, dynamic data, templates, forms, and workflow enhancements. BricksFly’s argument is breadth: elements, extensions, motion, full sites, and sections are in one license.

That is strongest when starting a new stack. If an agency already owns and trusts specialist tools for each of those jobs, I would compare the actual workflows before replacing anything. Consolidation is useful only if the new toolkit covers the details the team depends on, not just the category names.

What I would check before using it on client projects

• Ask the vendor why the WordPress.org listing is currently closed and how the free/base plugin is distributed now.
• Confirm the exact annual or lifetime checkout terms and site activation limits.
• Document that annual-license expiry can disable GSAP-powered front-end behavior.
• Enable only the elements and extensions the project actually uses.
• Test live copy/paste, JSON import, and direct-import workflows on staging.
• Check smooth scrolling, pinning, lazy-loaded media, and scroll effects on physical mobile devices.
• Verify important pages after major Bricks and BricksFly updates before deploying to production.

Who should consider BricksFly?

I would shortlist BricksFly for freelancers and agencies building a new Bricks workflow who want fewer separate subscriptions and expect to use templates, sections, elements, extensions, and animation together. I would skip it for non-Bricks sites and for mature Bricks stacks where existing specialist tools already cover these jobs reliably.

FAQs