midhem

Do you remember Twitter breaking hundred of thousands of application because of abrupt API toS change? Facebook breaking APIs without notice? Google changing Google Maps API freemium pricing killing thousands of map integrations? Linkedin killing API access to startup competing with them? If developers had read carefully API Term of Service, they would have known the danger.

Can I use this API safely in the long term is a difficult question to answer in the Digital world we live in. Most of the time, developers discover that their API access has been revoked when users complain their app does not work anymore.

On https://www.apitos.org/ we intend to build a framework making API Terms of service easily shareable and understandable, under the form of a creative commons pattern composed by simple logos and warnings. A quick survey is at your disposal to collect more feedback. Open to debate about what is important for developers and ideas/Feedback welcome!

Can we use this API safely in the long term is a difficult question to answer in the Digital world we live in. Most of the time, companies discover that their API access has been revoked when users complain their app does not work anymore.(Twitter story) Or sometime breaking change occurs without notice (remember Facebook APIs?). Sometimes it is the pricing options or other clauses that actually can break your app (remember Google Maps Pricing change?) because you did not read in depth the API Terms of service, so you did not prepare.

We intend to build a framework making API Terms of service easily shareable and understandable, under the form of a creative commons pattern composed by siple logos and warnings. Feedback welcome!

We are working on making login easier for non tech people, and we want to open the discussion/feedbacks about password issues on websites/mobile app targeted to nontech visitors and users.