Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Making API Terms of Service and Privacy Policy Easy to Read and Understand

DZone's Guide to

Making API Terms of Service and Privacy Policy Easy to Read and Understand

Typically, developers aren't malicious; they are just usually ignorant of the best practices that often exist in the platforms legalese we agree to, but seldom ever read.

· Integration Zone
Free Resource

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

The NextWeb had a great story saying that Google has redesigned its developer policies with clearer language and visual examples. Normally, I don't just parrot what the tech blogosphere publishes, but it's an important enough API message that I think it warrants repeating. In my experience, API providers just emulate what they hear in the space and stories like this need amplification.

What Google did isn't rocket surgery. They just simplified the legalese around what they expect of developers. What better way to actually help ensure these best practices around the platform actual happen than by actually providing simple titles, summary description, images, and other relevant links on a developer policy page? In most scenarios, developers aren't malicious; they are just usually ignorant of the best practices that often exist in the platforms legalese we agree to, but seldom ever read.

My friend Tyler Singletary stated:

The organization here for policy is fun, mostly clear, and interactive. A company the size of Google distilling the deep TOS policy into such a user and developer friendly front end is pretty astounding.

I agree. Simple like this, when you operate at Google scale can be pretty hard, and is something I'd love to see standardized across Google offerings. 

I will be adding any of the elements from the simplified Google Play developer policy that are missing in my API terms of service, privacy, licensing, and branding research. I will also add the concept of having visuals for each area, or building block, and add the common theme of "keep it simple." This will help API providers remember that they actually want developers reading and understanding this stuff, not having it buried in the legalese that nobody will give a sh*t about.

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

Topics:
api ,integration ,privacy policy ,terms of service

Published at DZone with permission of Kin Lane, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}