Run in the background does not equal no load, and it’s not like Homey has 8 cores. Phone apps designed like this are the ones that eat your battery in no time.
I have close to 400 flows, so you’re defending it is possible to cut this in half at the cost of 280.000 useless triggers a day. If you agree it’s not good code then at least add a disclaimer: “don’t try this at home”.
By saying it is doable and at no cost, you’re teaching people bad habits that may very well bite them, and when it does they will have too many flows to fix it.
And mind you, you assume state checks are free, but that depends on the app’s implementation. and more often tan not the then is triggered way more than intended causing heavy load.
This will not be evident immediately, but accumulate over time as more badly designed flows are added. And when you notice Homes is sluggish or unresponsive, Good luck then trying to figure out why your Homey load is 400% all of a sudden.
