Don't get me wrong, as a ubiquitous client, the
web browser is hard to argue against. Despite many pitfalls, it's got
tremendous momentum. At the same time, I have been thinking. When
do client applications matter? Simply put, when does a rich
client have an "unfair advantage" over a web browser in
terms of bringing real value-add to the application composite?
In thinking this one through, seven application patterns
stand out (I am sure there's plenty more), and it seems clear that there is
lots of potential synergy between these attributes.� Needless to say, this is something to think
about as you build your next generation Internet applications:
- The application leverages a
local data store.
- There are lots of
associations between items in the store.
- The application relies
on near-real time filtering to provide customizable user views.
- Maintenance of
a transparent information flow between a user�s other
client applications is integral.
- Reliability of data access is
mission critical to the application.
- Multimedia content
is regularly presented by the application.
- Peer-to-peer communications
or shared work spaces are a fundamental part of the application.
Do you buy my logic? Do other scenarios stand out for you?
Categories
Web
Comments (10)
Read More Entries by Mark Sigal.
The last cluetrain left 5 minutes ago
First off, I don't think I went the kindergarden route at all. An anonymous poster disses with nothing constructive to say. I consider that weak and said so. In contrast, you cite a clear, constructive perspective that's not insulting, and I will take that to heart in subsequent postings. Thanks for taking the time. :-)
The last cluetrain left 5 minutes ago
Kool-Aid.
It's weak to write in meaningless jargon, and then make a defensive reply to a valid point that was made about the poor quality of the writing. I agree with the poster; the language distracted from the topic, regardless whether they posted anonymously or not. I'd hope that you'd be able to offer a more mature perspective as to your poor choice of words, but you went the kindergarten route instead. Sad. But, as I am anonymous as well, my opinions have no merit either without a name as well, I suppose?
How about the following...
No doubt, although there were certainly a few companies (Applix is the one that most comes to mind) that tried to build a word processor that was wholly thin client based (leveraging Java in the web browser). Here's an old article:
http://www.wired.com/news/technology/0,1282,8870,00.html
Applix has completely re-launched themselves from this path in the market.
How about the following...
Applications where the level of interaction with the user cannot be supported by thin client (web browser?) applications.
I've often wondered if a word processor or CAD application could be effectively implemented as a thin client app.
The last cluetrain left 5 minutes ago
Everyone is entitled to their opinion, although it is particularly weak to diss while hiding under the shroud of anonymity. When you say meaningless, I am assuming it's because you are such a sage programmer that your world class applications (provide us an URL) find the perfect balance between the issues I raise and the ubiquity of the web browser. Or maybe you’ve just drunk the koolade, and everything else that doesn’t conform is just stupid? Either way, shine a light on yourself so others can make their own determination about you. :-)
The last cluetrain left 5 minutes ago
Value-add? Synergy? Leverage? Mission critical? Was this just a joke, trying to see how many ridiculous buzzwords could get thrown into a meaningless entry?
Hmmmm....
My personal take is that a hybrid approach, such as Zoe, makes a lot of sense, as it maintains a balance between what a rich client is really good at and what a browser excels at. On some level, to the extent you bake intelligence into your local store, the boundaries between client and server are murky anyway.
"tests the limits"
Favorably impressed so far (in terms of richness, speed of development, performance, reliability), with the exception that in areas where a specific library in the framework does not do what you need you are generally left re-creating all of the functionality, as opposed to using the subset that fits your needs and customizing the elements that don't.
"tests the limits"
Did you stumble? ;)
Hmmmm....
Perhaps... but where does this leaves an application like this? Which is a sort of "local" server running on your desktop...
It does 1 through 7... with perhaps the exception of 6.
Thoughts?