16 Web 2.0 programming ideas

1. Set a simple goal before you start. Whether you are the creator or user of a Web 2.0 application, please have a clear idea of your goal. The goal is like "I need to save a bookmarks" or "I want to help people create editable and shared pages", so that you can maintain the most basic requirements. The initial attraction of many Web 2.0 applications is its simplicity, which avoids and hides unnecessary complexity. From the standpoint of the Creator, we can imagine that Google has almost no content on its homepage, and there are simple lines of Del. icio. us. From the end user's point of view, it is the initialization page provided by diggdot. Us. You can and want to add more functions, but do the first thing. Only one feature at a time to achieve one goal. It sounds too simple, but it will make you more focused and you will understand what I mean.

2. Linking is the most basic idea. This is what we call web. Links are the most basic elements connecting various entities in the web. Your information, your relationship, your navigation, or even anything that can be written as a URL. Here is a link rule (in fact, you do not have to strictly abide by it ):

(1) anything on the Web can be connected by Uris or URLs.
(2) Save all links as their original source so that you can share them with anyone, anywhere, and anytime.
(3) the premise in article 2 at any time is that the link must be persistent and will not be changed or disappear without any reason.
(4) links should be readable, stable, and self-explanatory.

3. 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 explicitly give up this power to allow you to freely deal with it. Any information they contribute to the web should be editable, deleted, and shared at any time, as long as the user is willing. This also contains indirect data, such as records, logs, browsing history, website access information, or any information that can be tracked. All websites must clearly and simply complain that the information is created by the user, and provide methods for stopping the creation, or even clearing the information.

4. Data first, experience and function second. Whether it is text, images, audio, or video, the Web finally parses the data. In other words, you cannot render content without data. All of the data is located by URLs that are easy to discover (see article 2nd ). Looking at this in another form, web is ultimately a top noun, followed by a verb, although it is being shifted to a verb recently. Let's take a look at the examples of nouns: calendar entries, family photos, and stock prices. There are also examples of verbs: setting a appointment, sharing a picture, and buying a stock.
5. Make preparations for actively sharing everything. Share everything, all your data, and all your services as much as possible. We encourage you not to follow the original intent, advocate contribution, and do not insist on setting the content to be shared as private. After sharing and discovery, it is obvious to provide easy-to-use browsing methods. Why: in other words, you will benefit from others' sharing. Note: There is no law that permits you to infringe on copyright protection. You cannot share your DVD or commercial copyrighted music because you have agreed not to share these things. However, you can discover and share fully open media content. For a small suggestion, you can learn about Creative Commons license ).

6. Web is a platform. You need to make it grow. Of course, we also have many other platforms (Windows, Linux, and Mac), but those are no longer important. In other words, the Web is a platform that cannot be separated and will not be interrupted. You can expand the platform in various ways. The data and services you provide on the Web will become part of the web, and eventually you will assume your role somewhere on the web platform. Assume your role and take care of the future.

7. Understanding and believing in "tiered ". Today, the Web is getting bigger and bigger, spreading to almost all countries around the world, and already has 1 billion million users. My point is that there are subtle differences and differences between different components of the Web, just like users in different places. For example, in web design, usability always prevails over speed, reliability, reusability, and integration. You should also provide the same experience to your users. It has been repeatedly emphasized in the document that Loyal users will soon become professional users and they expect more faster speeds. Back to support them. Similarly, many users will enter the bottom of this step, as you expect. They may not speak your language, are not familiar with your culture, or even have no idea how they are here. So you need to make it clear to them.

8. Everything can be edited. Or it should be woven better. It must be determined that only a few items cannot be edited, and the rest can be edited. This is a writable web. This does not mean the loss of the original content. It is generally understood that the user can easily comment on the content, or the content of the comment is found there. If you do well in this application, they can do more than you think (concatenate the content and give the original content to create your own, and so on ).

9. The web identity is sacred. Unfortunately, this does not mean you get more privacy (this is entirely the idea of the last century ). However, identity authentication is necessary. You should thank the services that can identify you with only one email address. This means that as long as you promise your users, you must ensure their privacy and security. If necessary, you have to stand up for your users somewhere in the world and challenge local authorities. If you do not intend to do that, you have to tell your users the actual situation. On the other hand, if the identity is required, do not try to disguise it. Otherwise, one day we will give up our last privacy right on the web.

10. Understand popular standards and use them. From the standpoint of a consumer or creator, data will be exchanged with anyone in different formats. At the same time, such data will in turn promote the improvement and adoption of standards. This usually means the popularity of simple standards such as RSS, opml, XHTML, simple XML, JSON, and so on, avoiding soap, XSD, and RDF and atom, using them brings pain to my heart. Please vote for your favorite standards to support them.

11. Follow the rules of unintentional use. If you open and share very interesting data and services in a widely used format, you will get what you deserve, others will also build on your web platform. You may also get more from others, so it is better to prepare for this. I can't remember how many times I saw a podcasting service collapsed due to the popular transition, because it was included by Slashdot and Del. icio. us. You need to know this: the proliferation of the network means that if a content is very interesting, even a small corner will get amazing access. It is very valuable to encourage you to use this method, provided that you have to prepare for it.

12. Virtualize your data and services. We should have known it a long time ago that large-scale integration of data is only applicable to downloads and batch operations that do not need to be managed. Break down your data and separate them into descriptive URLs, which are the same for your services. On the other hand, you should not create huge, complex data structures and services like Christmas trees. Keep it simple. These separated parts can be easily reorganized and discovered.

13. provide data and services that can be separately benefited by users. Depending on this type of social participation, there are risks. You need to give your users a little motivation to contribute time, enthusiasm, and information, unless they can directly benefit. Social sharing is much more beneficial than individual behaviors. Unless you inspire your personal motives, you will not be able to enjoy this gift.

14. Let the user organize and filter information. It is not necessarily necessary, but it is very important. Let users label and organize data in their own way, because you can never process them in time. Users will process and build as best as they understand. Make sure that your web service can work in the way users want it. This is also the main factor for the success of tagging and folksonomies methods.

15. Rich user experience. Web has been fiercely competing with local applications. Why? Because the local program still feels better and faster. But this will not last long (I'm sure this competition will not exist in five or 15 years ). Yes, I'm talking about rich Internet applications, Ajax, and incredible interactive applications. They make web a real "platform-free" platform, if you know what I think.

16. believe in and support quick improvement and feedback. This usually means speeding up the pace, but it also means using lightweight tools, technologies, and not making the painful decisions that are counterproductive (for example, using an Ajax framework that is surrounded by layers can be achieved through mixing, or we can use C ++ to build everything. In fact, it would be better to use Ruby ). This also means that you need a very quick way to handle error reports, fix bugs, and release new versions. From a user's point of view, report any problems you have found, and the places you often complain about, or even those are not a bug.

Of course, Web 2.0 is an extremely broad and profound topic, and no one can list all its highlights and features. If you are interested in this, please take some time to add what I didn't mention. I think this is the participation of Web 2.0!

The title of the original author draws on Bruce Eckel's two best-selling books: Thinking in C ++ and thinking in Java. the C ++ programming ideology and Java programming ideology explain why this problem should be translated in this way :)