I didn’t just test Vue on a side project, I actually had to use it on a client’s website. On paper, it sounded like a good idea: modern JavaScript framework, reactive UI, and plenty of developer hype. But once I paired it with Advanced Custom Fields (ACF) inside WordPress, things started to feel more like a headache than an upgrade.

The integration just wasn’t smooth. Vue brought in its own way of handling data and reactivity, while ACF had its own established structure inside WordPress. Instead of working in harmony, the two felt like they were constantly pulling in different directions. The result? Extra layers of complexity, more time spent troubleshooting, and less time actually delivering the experience the client wanted.

Vue itself isn’t a bad tool, but in this setup it felt bloated. Too many moving parts for what should have been straightforward functionality. Sometimes, simple is better. In fact, I found myself wishing there was a single JavaScript library to rule them all. One tool that plays nicely with the WordPress ecosystem out of the box, without needing all these extra patches and workarounds.

Takeaway

Until we get there, I’ll keep leaning toward lighter, more flexible solutions that feel natural in WordPress projects. Vue might be a good fit for certain standalone apps, but when combined with ACF in client work, the experience was far from great.