The exporters are not built in though, they are on a server
That is actually the very opposite of what this petition thread is requesting.
I guess when people say "built in", they dont care about where the feature is (the cloud), what they really mean to desire is an exporter that was made specifically for construct - even if it was made with the same technology that they have been already using on their construct2's built-in exporters - only NOT built-in c3
The irony of what is requested, how the request is met and the community's reaction just amazes me
I guess in the end the whole point is to make the export process a one click effort