WEB 2.0 Programming Ideas: 16 rules
Original: Thinking in Web 2.0:sixteen Ways
Author: Dion Hinchcliffe
1. Before you begin, set a simple goal. Whether you're a creator or a user of a Web 2.0 app, make a clear idea of your goals. It's like "I need to save a bookmark" or "I'm going to help people create editable, shared pages" so you can keep your most basic needs. The first attraction of many Web 2.0 applications is its simplicity, which avoids and hides extraneous complexities. Standing in the creator's shoes, you can imagine Google's home page with almost no content, as well as the simple lines of del.icio.us. From the end user's point of view, the same is the initialization page provided by diggdot.us. You can and want to add more features, but do it first. Just do one feature at a time and accomplish a goal. It sounds too simplistic, but it will make you more focused and you will understand what I mean.
2, link is the most basic idea. That's one reason we call the Web. Links are the most basic elements that connect the various entities in the Web. Your information, your relationship, your navigation, and even any content that can be written as a URL. Here is a link should follow the rules (in fact you do not have to strictly abide by):
1. Everything on the Web can be connected by a URI or URL.
2. Save all the links as a source of his origin so that you can share it with anyone, anywhere, anytime.
3. The premise at any time in the second article is that the link must be persistent, and it will not be changed or disappeared without any reason.
4. Links should be human readable, stable, and self-explanatory.
3. The data should belong to the person who created it. Yes, you listen to me. Any user created, contributed, or shared is their own, unless they obviously give up the power to give you the freedom to dispose of it. Any information they contribute to the web should be editable, deleted, and able to be unshared, at any time, whenever the user wishes. This also includes indirect data like records, logs, browsing history, website access information, or any information that can be tracked. All sites must clearly and simply complain that the information is created by the user, and that they provide a way to stop creating it, or even to clear it.
4, data first, experience and function second. Whether it's text, pictures, audio, or video, the web ultimately parses these into data. In other words, you can't render content out of the data. All of this data is located through the easily discoverable URLs (see article 2nd). Looking at this in another way, the web is finally a noun first, and the verb second, although recently shifted to a verb. Take a look at examples of nouns: calendar entries, family photos, stock prices. There are some examples of verbs: set an appointment, share a picture, buy a stock.
5. Be prepared to actively share everything. Share as much as you can, all the data you have, all the services you provide. Encourage use that does not follow the original intent, promote contributions, and do not persist in the content that needs to be shared. After sharing and discovering, providing easy-to-use browsing is an obvious requirement. Why: In other words, you will benefit from the sharing of others. Note: There is no license to violate copyright laws, and you cannot share your burned DVDs or have commercial copyright music, because you have agreed not to share these things. But you can find and share those completely open media content. A small suggestion, you can learn creative Commons license (co-creation Agreement).
6, the web is a platform, to let it grow. Of course, we also have many other platforms (Windows, Linux, Mac), but those are not the point. In other words, the web is a platform that can't be disconnected, and you can extend the platform in a variety of ways without disrupting the platform. The data and services you provide on the web will become part of the web, and eventually you will play your role somewhere in the Web platform. Play your part and take good care of the later.
7. Understanding and believing in "Ladder nature". Today's web is growing, spreading almost all over the world, and already has 1 billion of users. My point is that there are subtle differences and differences between the various components of the Web, just like users in different places. For example, the design part of the Web: Ease of use always takes precedence over speed, reliability, reusability, and integration. You should also provide the same experience to your users. It has been emphasized again and again by people in the documentation that loyal users will soon become professional users who expect faster speeds and more. Step back and support them. Also, there are a lot of users who will go to the bottom of this ladder, as you would expect. They may not speak your language, are unfamiliar with your culture, and don't even know how to get here. So you need to make it clear to them.
8, anything is editable. Or it should be woven better. To be sure, only a few things can not be edited, the rest is OK, this is a writable web. This does not mean the loss of the original content, but is often understood as the user can easily comment on the content, or the commentary is found there. If you're good with this app, they can do more than you think (string up the content and give the original content to create your own, etc.).
9, the identity on the web is sacred. Unfortunately, this does not mean that you can get more privacy (which is entirely the idea of the last century). But verification of identity is necessary, and you should be thankful for services that can determine your identity with just one email address. This means that as long as you commit to your users, you must keep their privacy safe. When necessary, somewhere in the world you have to stand up for your users and challenge the authority of the local authorities. If you're not going to do that, you have to tell your users about the situation. On the other hand, if the identity is necessary, do not attempt to disguise it, or on one day we will abandon our last little privacy right on the web.
10, understand the popular standards and use them. From the standpoint of a consumer or creator, the data will be exchanged in different formats with any one person. At the same time such data will in turn promote the improvement and adoption of standards. This usually means the popularity of simple standards like RSS, OPML, XHTML, Easy XML, JSON, and avoiding soap, XSD, and RDF, Atom, and using them will bring pain to my heart. Please also vote for your favorite criteria to support them.
11, follow the law of unintentional use. If you open and share very interesting data and services in a widely used format, you will get what you deserve and others will build on your web platform. Maybe you'll get more from someone else, so it's better to prepare for it. I can't remember how many times I've seen a podcast (podcasting) service break down because of the popular transition, because they are included in Slashdot and del.icio.us. It's important to know that a lot of network means that if a content is very interesting, even a small corner will get a staggering amount of traffic. Encourage the use of this approach, it is also very valuable, if you want to be prepared.
12, granulation of your data and services. We should have known that in a long-run, massively integrated data is only available for download and batch operations that are not managed. Decompose your data so that they can be individually described as URL addresses, as well as for your service. Conversely, you should not create large, complex, tree-like data structures and services. Keep it simple, it's very simple. Let these pieces of separation be easily reorganized and discovered.
13. Provide data and services that users can benefit from individually. It is risky to rely on this kind of socialization, and you need to give your users a little incentive to contribute time, enthusiasm and information, unless they can directly benefit. Social sharing is much more beneficial than individual behavior, and unless you can inspire your users ' personal motives, you will not be able to enjoy this gift.
14, let users organize and filter information. It is not necessarily necessary, but it is very important. Let users annotate and organize their data in their own way, because you will never be able to deal with them in a timely manner. Users are treated and built in the best way they understand. Make sure that your Web services work the way you want them to be. This is also the main factor in the way that labels (tagging) and popular classifications (folksonomies) are so successful.
15, to provide a rich user experience. The web has been fiercely competitive with local applications. Why? Because the local program still feels better and faster. But it will not last long (be sure that the competition will not exist in 5 or 15 years). Yes, I'm talking about rich Internet applications, Ajax, and incredibly interactive apps. They make the Web a truly "platform-free" platform, if you know what I think.
16, believe in and support rapid improvement and feedback. This usually means speeding up, but it also means using lightweight tools, techniques, and not making the counterproductive pain decisions (for example, using a layered AJAX framework instead of being able to do it by blending, or building everything in C + +, actually using Ruby better). This also means a very fast way to handle error reports, fix bugs, and release new versions. From a user's point of view, report any problems you find, as well as the places you often complain about, even those that are not a bug.
Of course, Web 2.0 is an extremely broad and esoteric topic, and no one can enumerate all its priorities and characteristics. If you are interested in this, take a moment to add the places I did not mention. I think this is the participation of Web 2.0!
The title of the original author draws on the names of the two best sellers of Bruce Eckel: "Thinking in C + +" and "Thinking in Java", "C + + programming Ideas" and "Java programming ideas", which explains why you should translate this topic:)
Indigo Translation Finishing
http://www.bkjia.com/PHPjc/735104.html www.bkjia.com true http://www.bkjia.com/PHPjc/735104.html techarticle Web 2.0 Programming Ideas: 16 Rules Original: Thinking in Web 2.0:sixteen Ways Author: Dion Hinchcliffe 1, before you start, set a simple goal. Whether you are a web ...
