1. Someone owns one of these systems which is functioning perfectly well.
2. They stumble across a link allowing them to download the controller app, and so they install it on their normal tablet, expecting to be able to control the system from their tablet
3a. It doesn't work, so they contact technical support. Technical support wastes a bunch of time before figuring out why the app isn't working, only eventually to realize what's going on.
3b. They can't get the app to work, and so slag the system on social media.
Both have costs both to the people who end up downloading it, and to the company -- costs which could be avoided by having a simple error message.
There can be multiple reasons to do something. It's a simple, effective way to avoid some legit issues that doesn't require much if any testing; by itself it's a perfectly legitimate business decision and doesn't need to be illegal.
Paired with their attitude towards repairing the broken tablets, it's clearly also a part of their "planned obsolescence" scam.
This is pretty simple to solve for. Eg. Have the app provide an ID the customer can quote to the CS rep; Have the app also log this ID, along with the system it's being run on, to the cloud/an interface that pops up an "unsupported system" message to the CS agent on entering the ID.
1. Someone owns one of these systems which is functioning perfectly well.
2. They stumble across a link allowing them to download the controller app, and so they install it on their normal tablet, expecting to be able to control the system from their tablet
3a. It doesn't work, so they contact technical support. Technical support wastes a bunch of time before figuring out why the app isn't working, only eventually to realize what's going on.
3b. They can't get the app to work, and so slag the system on social media.
Both have costs both to the people who end up downloading it, and to the company -- costs which could be avoided by having a simple error message.