I get that this is quite nice, yet super trivial. But what I actually ask myself: how fucking often do you create a project that this is even a thing you notice and take the time to write an article about? :D but yeah, crazy feature haha

I do it the same way :) And the average file size is about the same as well here haha...

but as others already mentioned: bitmaps. As soon as you drop some images in (if it's as an applied style or inline doesn't seem to make any difference) sketch probably stores right within the file which heavily bloats the file size...

@sketch: feature request :D Can we have separate assets folder where images, icons and stuff can be linked to and updated? (:

We've been using Zeplin for almost 2 years now and it's definitely a great workflow improvement, for design, dev and product people as well. It still has it's flaws, but they're pushing feature pretty often.

Anyway, Sympli is quite interesting as well, but didn't make me switch for current projects.

Avacode works for web only, afaik, which is a knock-out criteria for me.

Basically pretty nice, but missing svg exportable assets, for example. But the workflow is quite nice, as you can just upload a selected artboard (or all artboards) to invision, wich will show the screen in the prototype (as usual) but also provide the inspect possibilities as well. If svg isn't necessary, you may give it a try :)

I get what you mean, but those are still assumptions and I think you can't surely tell how such a dynamic organism will behave neither can I.

I just wanted to encourage the designer folks here to be less grumbly about this "situation" and more optimistic and actually pro-active. Sure, maybe things are not going to change over at dribbble anyway, but at least we tried? (: I still like dribbble and to stay comfortable I try to mostly ignore and filter / unfollow the stuff I don't want to see.

And regarding the features for descriptions, organization etc. you mentioned; it's exactly this simplicity that keeps me posting stuff rather on Dribbble than on behance for example. Behance's complexity and detailedness is mostly overwhelming and creating meaningful, insightful cases can be tons of work for a single freelancer like me. Teasing WIP with a short yet informative description is the more convenient way to show my stuff to the world. And funnily it seems like similar behavior can be seen at behance as well. People tend to post studid comments there a lot as well. At least someone mentioned this in a comment before. I can't evaluate it as I am not using behance regularly.

I do agree that this exact simplicity narrows the obstacle to post and comment. So I am sure people will always try to benefit by posting "stupid comments"; to raise attention and gain followers. But I also think this is a larger problem that can't be fixed by some conceptional adjustments or a more strict invite system. It's a very much sociology related, talking about group behavior, social networks in general and swarm intelligence / swarm behavior. Maybe worth diving in deeper (:

It's stupid, right. But instead of complaining about it and the "dribbbleization" of design etc. we should rather continue to use dribbble the way we would like to see it used by others as well. Post WIP, not just fully polished stuff, post meaningful and constructive feedback in the comments and don't invite people for the sake of using your invites