http:\/\/goo.gl\/forms\/G3vddOdRL3<\/a><\/strong>\n<\/p><\/blockquote>\nThings we want to improve<\/h2>\n
This is a shortlist; if you’ve got areas you want to improve, please add a comment.
\n<\/p>\n
Challenge 1: Value<\/h3>\n
Quality is immensely variable – there are no standards on pricing. So sometimes you get an asset worth $30 and it’s free (amazingly). Other times you pay $30 and the asset is so poorly supported, and badly written, that you feel it’s not worth anything at all.<\/p>\n
Unity has an excellent refund policy: basically, if you feel you were mis-sold, you get a quick, easy refund. (allegedly – I’ve never tried to get it, but I know others who have, and said it went fine).<\/p>\n
Challenge 2: Quality<\/h3>\n
The Asset Store lets you see a few screenshots and a very hard-to-read description, along with optional customer short-reviews. But we’re an audience of experts! We can write – and we need – detailed, expert reviews.<\/p>\n
Challenge 3: Comparison<\/h3>\n
Most things have 20 or more competing solutions on the Asset Store, but when you’re looking at one, you can’t see any of the others (unless they randomly appear on the listing). Most of the time, an asset is “almost but not quite right”, and you need direct competitors you can compare to.<\/p>\n
Bonus: if this happened more, we’d see more competition-driven improvements to assets.<\/p>\n
Challenge 4: Compatibility<\/h3>\n
Many assets are incompatible with common \/ standard assets. They shouldn’t be. But with no-one holding the authors to account, there’s no reason for them to change this.<\/p>\n
On the other hand, many assets claim compatibility with each other, which boosts their sales. So compatibility guides should help everyone.<\/p>\n
Challenge 5: Discovery<\/h3>\n
How do you know what to look for when you don’t know what exists?<\/p>\n
For instance, some of the major bugs in Unity that are too niche for Unity to fix … have easily-purchasable assets that fully fix the problem. If you only knew this, you would have a better, more stable Unity.<\/p>\n
Challenge 6: UX \/ GUI \/ Usability<\/h3>\n
Unity puts (almost) no limits on the usability of assets. This is great for freedom. But it’s bad for long-term development. Often you install an asset are immediately lost: how am I supposed to use this thing? Does it have a GUI? Or not? Where do I click?<\/p>\n
It’s often a problem for 3D models (many are packaged incorrectly), and for editor-extensions (MANY of them have major bugs eg. no support for Undo, or they corrupt when moving stuff between scenes, or … etc).<\/p>\n
What would help enormously is some standardization that asset authors can apply, and users know and know how to use.<\/p>\n
What can we do about it?<\/h2>\n
My plan has a couple of stages:<\/p>\n
\n- Compile a list of “best of the asset store”\n
- Solicit reviews of everything on the list, and peer-review them for accuracy\/impartiality\n
- Create “best practices” standards for authors to follow\n
- Hilight assets that adopt the best-practices\n
- Start small, scale it by pushing out to Unity community to grow\n<\/ol>\n
Step 1: Share your favourite Asset-store assets!<\/h3>\n
Here’s a google form for sharing your favourites. NB: this will combine all the repeat recommendations for the same asset. If you add something someone else has added you’re effectively voting it to the top:<\/p>\n
http:\/\/goo.gl\/forms\/G3vddOdRL3<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"Unity is still the only major game-engine with an effective, established Asset Store. This is an enormous benefit to game developers – but do you feel you’re making full use of it? I’ve bought and used hundreds of Unity plugins, models, scripts, etc from 3rd parties. I’ve found some amazing things that transformed my development. […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[67,69],"tags":[],"_links":{"self":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/3833"}],"collection":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/comments?post=3833"}],"version-history":[{"count":2,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/3833\/revisions"}],"predecessor-version":[{"id":3835,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/posts\/3833\/revisions\/3835"}],"wp:attachment":[{"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/media?parent=3833"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/categories?post=3833"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/new.t-machine.org\/index.php\/wp-json\/wp\/v2\/tags?post=3833"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}