Fax has been doing a great job of answering questions!
I’ve updated the top of the FAQ with some of the questions he has answered. I’ve omitted ones that were already answered.
I’m going to tackle a big one, though. Let’s dig deep a little…
Let’s tackle the source file questions and concerns!
And my apologies – this is going to be a long one. 
When we (or anyone, for that matter) is designing a product or feature, you generally operate with a certain target audience in mind. Even if you intend for something to be used by far more people than that initial audience in the future, picking an initial audience can help narrow development scope.
When you’re working with a limited number of resources, this can help you make difficult decisions: you’re working with a certain number of people and you have a certain timeframe and budget.
This means you’ve gotta make some hard choices!
In creating the Avatar Marketplace, we’ve opted to target users who weren’t currently being adequately served by our current content pipeline. Basically, out of the gate, we’re looking at folks that have never used the SDK – and likely have no interest in doing so. Yet, these folks also really want an avatar.
The current solutions that exist aren’t great: avatar worlds, search worlds, and the like are what current experienced users are used to… but they’re not a great experience for your average VRChat user.
If you’re an avid reader of the bi-weekly Developer Update, you’ll remember us saying that we’ve been bringing a lot of UX research into our planning. These choices are a reflection of that data and research!
Consequently, this also means that we’re thinking about the features that make the most sense for this particular cohort. If you lay out everything an Avatar Marketplace needs on the table and are allocating resources, does including a method of downloading source files really make sense for this particular initial target? Is it so important that it’s worth sacrificing development time for another feature? How will this move the needle and make this more successful for these particular users? You get the idea.
Much in the same vein, when we first announced the Creator Economy, we heard loud and clear from avatar creators that they wanted to be part of CE! They’re another big factor here – we wanted to build something that worked for them.
So when we were building out the Avatar Marketplace, we included them in the process. We took account of their needs, and what their biggest requests were. We also took into account some of their biggest gripes – piracy, having to provide a high-level of user support to folks just using Unity for the first time, and so on.
All of this data – from tons of UX research directed at both users and creators – helped us prioritize what would be included in this first, initial release of the Avatar Marketplace.
Just because this is what the Avatar Marketplace looks like now does not mean this is what it will look like in the future. Our philosophy is to constantly iterate and improve, and of course, this is part of that, too.
Trust me: we have a lot of plans for the Avatar Marketplace.
The Avatar Marketplace is a vital part of our ability to continue existing as a company – of course we want to make it useful to as many people as possible! But, as mentioned previously, you’ve gotta make hard choices out of the gate – else you’re going to end up in development hell.
We are extremely grateful that our community is vocal about the stuff they want – that’s a good thing! We encourage you to keep telling us your pain points and we welcome the sort of passionate discussion these sorts of things bring out.
Finally: serving one community doesn’t mean we are going to be ignoring another. We’re continuously adding tools to our SDK, for both avatar and world creators. We have no intention of stopping! We want to help people make really cool things – that’s core to our purpose.
At the same time though, some people just want to look cool, and we want to help those people, too.