>>25737
Okay, I've been on both sides.
The benefits of team projects:
- gets 'viral' quicker, since instead of just you, you have multiple people shilling simultaneously.
- you learn to not be perfectionist, since you just accept each team member's contribution, and assuming it doesn't look evidently half-assed, assume that's already a good enough quality for the project
- you finish quicker
The downsides of team projects:
- if the project falls apart, it's done. The only person who legitimately has the 'copyright' to continue would be the project leader IF he put his own money up front. Best forget about it and all the wasted time.
- the project quickly evolves into something which may not feel like your project anymore.
I myself prefer solo now:
- no deadlines, I work at my own pace
- I just troll around for creative commons 0 or royalty free stuff and stockpile them, and easily add them to my projects later on. It's the same as custom commissioning but far cheaper. Even better since the end result is already nice, compared to the directions you still have to instruct to the freelancer who may or may not screw up.
- No need to worry about lost projects unless I failed to back up. Since they're all my projects, I can restart them anytime.
The downsides of course
- time
- no one but you shilling
I wouldn't even mention lack of quality in solo projects, because as mentioned, plenty of CC0 stuff are quality assets now, and if you put them together competently you will feel like a pro.