yes i hear you, but here’s an example.
let’s say you have an app that has multiple features that users can turn on and off. or that some users employ but others do not. assume one is to show some data from google analytics in a card, the other is to show data from mailchimp. but all users don’t need this data, and some users don’t need either. but b/c i have to setup a structured data “holder” as a hubspot crm extension object, i have to create two “card carriers” to hold these cards.
now, true i could just add a button but the whole point here is to not have the user need to add an extra interaction. i mean if we wanted to go that route, we would use the entire crm extension to do nothing other than just add a button to open a modal and do everything in there.
so then what happens when you have not just two “types” but lots of them? it eats up a ton of real estate, or requires the user to move the unused card carriers to the bottom to get out of the way.
so, in that case, a plausible workaround is to create one app called “APPNAME - ANALYTICS” and another called “APPNAME - MAILCHIMP” and so forth. so for every feature, it’s a new app and subscription. but that gets really annoying and complicated to manage on your end too.
so i don’t think its about showing 10+ objects, it’s about having 10+ different object types, where at any time only a handful of users may use 1-2 different object types.