Protocols are not a preference. Put fifty Wi-Fi devices on a home router and the network falls over; put a power-hungry camera on Zigbee and it will not work at all. Here is what each protocol is for and how they fit together.
Use Wi-Fi for anything needing bandwidth: cameras, TVs, tablets and speakers. Use Zigbee or Thread for everything numerous and battery-powered: sensors, buttons and most switches. Matter is a language rather than a radio, running over Wi-Fi, Ethernet or Thread. Mains-powered Zigbee and Thread devices form the mesh, so place them deliberately.
The short version
Everyone already has it, and that is both the appeal and the problem. Wi-Fi devices need no extra hardware and get full internet bandwidth, which makes them right for cameras, media devices, wall tablets and anything that streams.
They are wrong for scale. Every Wi-Fi device holds an address and airtime on the same network your laptops use, most consumer routers start behaving badly somewhere between thirty and fifty clients, and cheap Wi-Fi devices are the ones most likely to phone home to a vendor cloud. In a Singapore condo you also have sixty neighbours on the same channels.
Rule of thumb: if it needs bandwidth, Wi-Fi. If it just needs to say "someone moved", not Wi-Fi.
A low-power mesh built for exactly the devices Wi-Fi is bad at. Sensors run for a year or two on a coin cell. Every mains-powered Zigbee device - a switch, a plug, a bulb - repeats the signal, so coverage improves as you add devices rather than degrading.
It is mature, it is cheap, and the device selection in Singapore is enormous. Zigbee shares the 2.4GHz band with Wi-Fi, so channel planning matters, and it needs a coordinator plugged into your hub. In practice this is the backbone of most homes we build.
The modern equivalent: also a low-power mesh, also self-healing, but it speaks IP natively, so each device is addressable like anything else on your network. It has no single coordinator to fail, and it is what Matter uses for battery devices.
Thread is the direction the industry is moving. The device catalogue is still smaller than Zigbee, and border routers from different vendors have not always played well together. It is a good bet for new builds and a poor reason to rip out a working Zigbee mesh.
Runs on sub-GHz frequencies, so it does not compete with Wi-Fi at all and penetrates walls better. Strict certification means devices tend to behave. The trade-offs are price, a smaller Singapore catalogue, and regional frequency variants - a Z-Wave device bought from the wrong region will not work here. Genuinely useful for locks and for a large landed home where wall penetration is the constraint.
The most misunderstood term on this list. Matter is not a radio. It is a common language that runs on top of Wi-Fi, Ethernet or Thread, so a Matter device can be added to any Matter platform without a vendor bridge.
That is real progress, and it is narrower than the marketing implies. Matter standardises the common capabilities - on, off, brightness, colour, open, closed, temperature. Manufacturer-specific features frequently sit outside it, which is why a Matter-only integration of an aircon or a robot vacuum often exposes less than the native integration does. We use Matter where it is the best path and the native integration where it is not.

A typical CtrlSpace build runs three at once, and the visitor never knows:
Cameras, wall tablets, TVs, speakers, robot vacuums, the hub itself.
Wall switches, motion and contact sensors, buttons, curtain motors, temperature and humidity sensors. The bulk of the device count.
Newer battery sensors and locks, on a border router that is often already in the house.
Anything that must never fail. A relay on the gate, a Modbus energy meter, a PoE camera.

Both Zigbee and Thread are only as good as their routers, and their routers are your mains-powered devices.
A complimentary design session covers all of this against your own floor plan, with a live Home Assistant system in front of you.