Asset store & APIs used

It seems some assets on the store are largely wrappers around open source libraries - geometry, AI etc. Sometimes around closed source, using available APIs too (chatgpt etc)

So is it time Assets stated all used APIs within their description to make clear it is not some entirely brand new creation?

(related - art assets state AI tools used for possible copyright infringement!)

No. I believe not. I don’t care what they use if they deliver what they promise on the way they promise it. Nothing else matters.
And you shouldn’t care either. Using a new technique isn’t inherently valuable. It boils down if the stuff does what you need or not on the way you need it. If they are sacrificing black roosters in the background, but their stuff gets the job done, so be it. I don’t care.

1 Like

Generally… can agree. I always look to use existing techniques where possible!!
But I always look through a package’s content on the store now to see if they are using some github APIs or chatgpt etc. in case I can get more customised usage out of the same API for instance… or to understand possible future issues with closed-source APIs

If an asset’s going to access a web API or do any other network access, the asset description should make that clear.

2 Likes

I don’t see a point. If someone wants to do X, and the asset does X without having to write megabytes of glue code, it does its job.

It should warn if it relies on a paid 3rd party API which requires subscription, though.

Even if it’s not paid. I find it also quite important to know if the asset actually is “stand alone” or depends on a service that could be ended at any time.