I have a Type that would require a huge amount of fields, the reason being that it tracks multiple type’s of products, each with its own data, technically i could create a type for each product.
The question is: is there any negative implications for “going wide”, rather than creating a Type for each Product?
(Saving or editing a product will never change more than 10 fields at a time)
With the caveat that I don’t know the specifics of your app, my hunch here would be that it’s better to go for one Type with a lot of fields, than a lot of different types with fewer fields. One of the big reasons is that it will make it a lot easier for you to display or make changes to a lot of products at once: it will only take one search instead of one per type. Reason number two is the worry that as your business grows, more products will be added and you end up with a huge number of Types.
In one app I made though, I kept track of different items that were so fundamentally different that it made sense to separate them into different Types, as they would never interact in any way. So there’s no given answer, it all comes down to what exactly your app is doing and the specifics of the products it keeps track of.
