Keep your [phone/PC/whatever] on one VLAN, with a NAT gateway, and they'll work just as they do now.
Keep the IoT Things inside of their own VLAN, without a gateway to the Internet.
And if a device like Home Assistant or whatever needs to exist on both VLANs in order to be useful, then: Make sure it isn't forwarding/routing/NATing packets.
---
The implementation details vary, but they needn't be particularly expensive.
What I do at home is run OpenWRT on a Pi 4 for my home routing purposes. It's fast enough for my needs and it's got simple GUI configuration options for VLAN. (Why OpenWRT? Because it's easy for me to puzzle out when I need to adjust something after a few months or a year -- I don't deal with routing every day, nor do I wish to. (Also SQM is a built-in, which always keeps WAN latency tolerable.))
From there, I've got cheap managed switches that enforce/insert VLAN tags where that is useful to me, so I can decide which physical ports are capable of talking to whichever VLANs.
And from there, I've got relatively inexpensive Mikrotik access points that are configured to provide different SSIDs for different VLANs.
It all works OK, though more enterprisey folks will almost certainly choose a very different path.