Currently, it is possible for recommendations to be surfaced based on guid co-installations that are incompatible with the client's OS. This is handled elegantly by AMO whent he recommmendations are surfaced, however, the client should not be exposed to unavailable extensions.
No obvious solution presents itself without splitting the ETL job by OS, which would mean that no recommendations are available for OS'es with few clients (to meet minimum installs thresholds in place for privacy).
@birdsarah @crankycoder Let's discuss a strategy for providing a good experience to all platforms.
Currently, it is possible for recommendations to be surfaced based on guid co-installations that are incompatible with the client's OS. This is handled elegantly by AMO whent he recommmendations are surfaced, however, the client should not be exposed to unavailable extensions.
No obvious solution presents itself without splitting the ETL job by OS, which would mean that no recommendations are available for OS'es with few clients (to meet minimum installs thresholds in place for privacy).
@birdsarah @crankycoder Let's discuss a strategy for providing a good experience to all platforms.