Window shopping and Java web applications
previous post I talked about the potential for using a rich client runtime like Java to provide a better experience for web users and a simpler and more productive experience for web developers. But this can raise a concern: what do you do about Google spiders and getting attention from search engines? If your "web site" is embedded in Java, how does Google find you?
Anne refers to an article that discusses this issue in more detail and gives you tips on how your dynamic app can still be available to search engines.
For example, if you have a rich-client calendaring app, then if a spider goes to your URL, you provide an HTML version of your calendar. You can have a rich-client music player, but a spider or someone just "checking you out" can go to your URL and find a nice presentation of your service with updated content.
I think of it as the difference between someone walking down the street window shopping, versus someone going into your store and wanting to try on clothes, push buttons, taste the fruit, and interact with your salespeople. For web applications, the browser and HTML can be used for "window shoppers" while a rich client model can be used for committed users who want to have a richer, more interactive experience of your service.
Some care must be put into how you migrate a window shopper to a committed user with as little effort as possible, so they don't just walk away. It should be as easy as opening a door and walking in.