Posts tagged announcements

Pay with Stripe

We’re excited to announce that we’re now offering Stripe as a way to make credit card payments for Pro accounts or Jobs on Dribbble. Until now, PayPal had been the only available payment method, and it continues to be an option along with Stripe. If you live outside the United States and have had difficulties making purchases in the past, or if your business has had trouble using a company card, give Stripe a try!

image

Thanks to Stripe Checkout, we were able to integrate their functionality in to our site with incredible speed and ease. Plus, instead of sending customers to a third-party site to make a payment, Stripe Checkout offers a simple popover box to pay instantly without ever leaving Dribbble. All payment information is securely processed by Stripe, and the results are immediately returned to our servers for processing.

Our new developer Tristan spearheaded the integration, and he was pleasantly surprised with how easily Stripe could be worked in to our existing code and UI. When we told him we’d be mentioning him in this post, he replied, “Aw shucks, Stripe is going to know I have a crush on it.” I couldn’t have said it better myself.

Evolving Our Community Guidelines

We’ve just updated our Terms of Service and Player’s Handbook with new rules and guidelines as to what constitutes appropriate content at Dribbble.

Historically, Dribbble has been a relatively open publishing platform. It’s self-organizing in the sense that members can create their own community by following (and blocking) other members as they see fit. For the most part, we’ve tried to stay out of the business of deciding what content is and is not appropriate by crowdsourcing this responsibility. This model appears to works well for services like Twitter and Facebook; combined with our small population and invitation system, we believed it was working well for us.

That self-organizing nature is likely here to stay, but recent events shifted our thinking about community and our role in managing it. We better understand that:

  1. There is much stronger sentiment of Dribbble as a single community versus separate, sub-communities (a la Twitter, Facebook), and thus we have more responsibility to provide guidelines for Dribbble as a whole.
  2. Some people have expressed that they do not feel welcome or comfortable at Dribbble due to the nature of some of our content and comments. And we hate this.

Today, we’ve made changes to our Handbook to clarify what types of content are inappropriate to post on Dribbble, in order to make it a more welcoming and inclusive community for designers and fans of all ages. Specifically, we’re going to be more aggressive in removing content that doesn’t meet these new guidelines. We can’t guarantee we’ll catch every inappropriate shot or comment that’s posted, but we think expectations are now much clearer and more conducive to fostering community.

It’s important to point out that inappropriate content has been a small fraction of what’s posted. The vast majority of work shared is inspiring and the reason for Dribbble’s success.

Adding manual and automated mechanisms to better enforce our guidelines will be an ongoing process. It won’t happen overnight, so we ask for your patience as we continue our efforts to grow gracefully.

Thank you yet again, Dribbblers, for creating such a special place. We’re trying hard to keep it that way.

There’s no I in team. But there’s an API in Dribbble.

Just over a week ago, we published the first draft of the Dribbble API. But it seems like much longer, given the avalanche of API-related inquiries, shots, apps, sites and other creations in this short period.

Players and other interested parties have been requesting an API from Dribbble’s [yes, I’m going there] Inception. (They asked during the beta; the beta beta; the beta beta beta; ok, the top has long stopped spinning on this joke.) We’ve always been excited about the prospect of having an API, but dragged our feet on it for a while, as it comes with risks.

Releasing an API marks the progression of an application from web site to PLATFORM. Even without the caps, it’s a scary transition. Ease of access to your data is accompanied by potential for abuse, new and more difficult-to-predict scaling issues, loss of control over the presentation of your content, the need to define guidelines for usage, etc. It’s a big leap.

It also presents business challenges: If folks start viewing Dribbble through other lenses (iPhone, iPad, etc), are we cannibalizing our own advertising revenue? How do our nascent efforts toward a sustainable Dribbble (revenue) fit in this new paradigm?

We thought long and hard about all these issues, read all the research and came up with a comprehensive 5-year plan for our business. Wait, that was in the dream. What we actually did was add another server, set some rate limits and take the red pill. (Whoops, wrong movie.)

We’re not sure how many levels deep the API is going to take us. And we don’t know what it means for our current reality. Nonetheless, the seed has been planted. APInception. We can’t wait to see what you dream up.

Posted by Rich

About Dribbble

Dribbble is a community of designers sharing screenshots of their work, process, and projects. This is our official blog.

Dribbble Newsletter

Sign up for our newsletter to receive periodic news, updates, featured content, and more.

Dribbble Equipment

Threads and goods for designers like you. Official Dribbble shirts in our equipment shop.

Follow Dribbble

Dribbble Dribbble on Twitter Dribbble Meetups Dribbble on Instagram Dribbble on Facebook