• SatoshiSea

    (@satoshisea)


    It’s utter garbage. It doesn’t even work with the paid plan. It’s slow, lacks CSS control over hard-coded styles that relentlessly and inevitably execute pseudo-elements, and isn’t compatible with any wordpress thee, or customized css /design /tokens system integrated or builder (Bricks, Divi, Enfold, Elementor, Beaver, etc). The only one that was ore suitable was the Block builder/Gutembertg, but thats not what most designers are aiming for on 2026. Evcen tried disabling every plugin on my system and the same output… and is unbelievable that just on that ters i can have a really slow but decent dark mode peforance with 350mb of emory on tav perforance becasue of all the heavy load hardcoded rules that are useless for a single page and soe few tokens i just set up… totally mindless and not meant to work with the current existent Production and Commercial Leader themes and syastems, and not even able to compatibilize with customizations or ewven the basic wordpress customizer override.

    First, it simply does not work reliably. Across multiple environments (Windows, macOS, Linux) and browsers (Firefox, Chromium-based, Opera), the result is the same: activating the toggle frequently freezes the tab entirely. No console output, no debug information—just a complete lock-up. On the rare occasion it does load, it can take several minutes.

    Second, the implementation is fundamentally flawed. The plugin relies on aggressive, hard-coded CSS rules with excessive use of !important, which override everything—including pseudo-elements, overlays, transparency, and background images. This destroys any non-trivial UI. There is no meaningful way to control or override these styles.

    Third, there is no real developer support:

    • No proper debugging tools or logs
    • No useful technical documentation
    • No guidance for integration with custom themes or design systems

    Fourth, the architecture shows clear limitations. Instead of using modern approaches like tokenization, root variable swapping, or contrast-aware color transformation, it applies brute-force class and style overrides. This makes it incompatible with most real-world themes and completely unsuitable for custom UI systems.

    Finally, the free version is extremely restricted, but even reviewing the codebase suggests that the “pro” features do not address these core issues—they are just gated additions on top of a broken foundation.

    This plugin has a promising idea, but the execution is severely lacking in performance, adaptability, and engineering quality. I cannot understand the high ratings given its current behavior.

    At this point, it’s more practical to build a custom solution than rely on this plugin.
    I hope this feedback, filled with disappointment, helps the team move towards a proper CSS product and a state-of-the-art plugin, like the one I so desperately needed when I was about to buy yours.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Sakhawat Hossain

    (@shshakib2001)

    Hi SatoshiSea,

    Thank you so much for taking the time to write such a detailed review. I’m truly sorry to hear Darkify caused this much frustration on your build — that’s not the experience we want anyone to have.

    A few of the specific issues you mentioned, especially the tab freezing on toggle with no console output, aren’t something we’re seeing reported elsewhere, so I’d really like to understand what’s happening on your setup specifically rather than assume it’s expected behavior.

    Would you be kind enough to open a support ticket here so we can look into it properly: https://themeatelier.net/create-support-ticket/

    If you could include the following, it would help us a lot:
    •⁠ ⁠The site URL (or a staging link) where you’re seeing the freeze
    •⁠ ⁠Which specific theme/builder combo you tested last (Bricks, Divi, Elementor, etc.)
    •⁠ ⁠Your PHP and WordPress version

    On the broader point about the CSS approach — you’re right that the current implementation relies more on override rules than token-based or root-variable swapping, and that’s a fair critique. It’s something we’re actively looking into improving for a future release.

    Thank you again for the honest feedback. We’d really like the chance to make this right for you.

    Best regards,
    Sakhawat.
    ThemeAtelier Support

    Plugin Author Foysal Imran

    (@faysal61)

    Hi SatoshiSea,

    Following up here — we just released version 2.0.3, which includes a rewrite of how Darkify watches the page for changes. Previously it registered a watcher per element, which is exactly the kind of thing that could cause the freezing and heavy memory use you described, especially on larger or more complex pages. That’s now a single watcher for the whole page, so the cost no longer scales with page size.

    If you’re able to update and try again, we’d really appreciate knowing whether this resolves the freeze on toggle. If it’s still happening, the ticket link Sakhawat shared is still open, and the site URL / theme-builder combo / PHP-WP version details would help us reproduce it directly rather than working from a general description.

    We take this kind of feedback seriously, and we’d like the chance to actually fix what you ran into.

    Best,
    Foysal

Viewing 2 replies - 1 through 2 (of 2 total)

You must be logged in to reply to this review.