* Read other chapters: http://blog.csdn.net/cuibo1123/article/details/39894477
The final thought
I learned through difficult studies and many years of mistakes. Wrote this article about creating components and API rules. I'm trying to practice my writing skills, although inevitably there are a lot of examples that I haven't mentioned.
Not all rules apply in all cases, and no rule is applied under any circumstances. Here is just as much inspiration as you can to make your design more flexible for yourself and others. Reusable components.
You may need a high-speed summary of all the rules, as you can see. I have a full-size version on my Flickr.
Suppose you are interested in opening up your components for others to use. You may need to read my opinion about publishing open source code, and it also talks about how to write a Readme file, license selection and other related matters.
I hope you like this article. Suppose you like, maybe you'll consider buying my non-open source component, or support this blog post by donating it.
I really appreciate that.
To learn about many other designs that originate from the software and user experience, as well as other topics, you can follow me on Twitter (@mattgemmell). can also hire me to work together.
Today, you are able to make great software.
-------------------------
English formerly known as " API Design "
author :Matt Gemmell
formerly linked :http://mattgemmell.com/api-design/
The Chinese version is xoneday translate
http://blog.xoneday.com @xoneday one day
Let's say that this translation brings you help, and 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: do not cut the author/Content translation information and Support section if you do not accept these terms and do not reprint.
Component Interface (API) Design Guide [5]-final thought