Component Interface (API) Design Guide [5]-final thought

* Return to Table of contents read other chapters: http://blog.csdn.net/cuibo1123/article/details/39894477

The final thought

I wrote this article about creating components and API rules through difficult learning and years of mistakes. I am trying to practice my writing skills, although inevitably there are many examples that I have not mentioned.

Not all rules apply in all cases, nor does a rule apply in any case. Here is just as much inspiration as possible to make you design more flexible, reusable components for yourself and others.

You may need a quick summary of all the rules. I have a full-size version on my Flickr.

If you are interested in opening up your components for others to use, you may want to read my view on publishing open source code, which also talks about how to write a Readme file, license selection and other related matters.

I hope you like this article. If you like, maybe you'll consider buying my non-open source components, or support this blog post through donations.

I really appreciate that.

To learn more about the software and user experience design, and other topics, you can follow me on Twitter (@mattgemmell). can also hire me to work together.

Now, you can make great software.

－－－－－－－－－－－－－－－－－－－－－－－－－

" api Design "
Span style= "COLOR:WINDOWTEXT;" >        author : matt Gemmell
        original link : http:/ /mattgemmell.com/api-design/

The Chinese version is xoneday translate
        Welcome to Translator blog: Http://blog.xoneday.com        @xoneday one day

If this translation brings you help, I hope you can download my APP to support me:
watercress reading: https://itunes.apple.com/cn/app/id695492935
Memo Clip: https://itunes.apple.com/cn/app/id580552733

Memo Clip watercress Reading

* Reprint statement: Please do not Delete the content of the author/translator information and Support section, if you do not accept this clause please do not reprint.

Component Interface (API) Design Guide [5]-final thought