If it's compatible with HomeKit, it's probably compatible with everything else you listed. Alexa works with a ton of stuff. I have a few of the new LifeX bulbs, and I bought an echo dot because they're not HomeKit compatible, at the moment at least.
This new LEDVANCE bulb is works with Bluetooth, which Amazon Echo does not (yet? natively) support for controlling home automation devices. It must have some sort of IP interface, e.g., through a Hue bridge, a SmartThings or other compatible hub, or similar. So, I doubt it will work to control with Alexa. I think the best bet for future compatibility is to home SmartThings finally works in making the Bluetooth radio they included in the v2 hub useful, which would work well for things like this and SwitchMate.
Also, to those fighting over HomeKit vs. SmartThings: I think it's clear they both have their advantages and disadvantages. SmartThings probably has the widest compatibility (excluding Bluetooth devices like this that were made to work only with HomeKit) and is extremely customizable (you can import or personally write new device handlers for devices SmartThings doesn't officially support that are in some way compatible with the system--Z-Wave, ZigBee, or HTTP; and you can write custom "apps" to automate or make the devices behave or interface with other devices or actions in exactly the way that you want, though the stock apps do quite a bit as well). The downside is that it is heavily reliant on the "cloud," even for devices/actions that are entirely capable of being controlled locally. I use SmartThings but often contemplating switching to Vera or something in hopes they can do more locally, which SmartThings improved with v2 but not as much as they could have. This wouldn't be a problem if they didn't have such frequent server problems (which have also gotten better, but as recently as a few days ago my hub was convinced for about 15 minutes that all my actions happened 5 minutes in the future, so my lights wouldn't turn on when I walked in the room...yet).
I don't think there are quite as many devices as compatible with HomeKit, but the number is constantly increasing. The main advantage to HomeKit for me is the ability to use Siri to control devices. I can't do automation because I don't have an AppleTV (or an iOS 10 iPad that's always home), but I seriously doubt it's as flexible as what SmartThings allows (can you write custom code?). Contrary to what one poster said, it's also much less likely to be compatible with older devices. The only time I have seen this happen is with Philips Hue, which required a new bridge and just happened to allow the older
bulbs (which don't directly interface with HomeKit--the Bridge communicates over the IP-based network and controls the bulbs over its ZigBee mesh network). Insteon did something similar as well, I believe. It is difficult for many other devices to do this due largely to the bleeding-edge security requirements HomeKit mandates (including the use of very strong encryption and apparently the need for a special security co-processor). I think SmartThings theoretically stands a technical chance at HomeKit integration if they make a compatible hub, but I'm not sure if Apple's requirements would prevent them from using it to control potentially security-sensitive devices like locks and garage doors (which are disabled through the default Alexa integration for similar non-technical reasons).
tl;dr Liking SmartThings doesn't make you a Samsung fan, and SmartThings is not designed to work well with exclusively Samsung products--SmartThings has been around before it was acquired by Samsung and the main difference now seems to be that you can use certain Samsung TVs as a hub rather than buying the dedicated SmartThings Hub if you want. Lots of devices work well with either ST or HomeKit, and some work only with one. Use whatever you like and works well for you--or a little of both.
