Except for some brief forays into some Sametime+Web Intranet integration, and some blog work I've been doing, I'm for the most part immersed in Notes Client work. But that's just for the time being with my current workload. It does fluctuate...but we have a plethora of client stuff!

My last contract was entirely web; in my current environment it's about half and half, although everything I've been assigned so far has been web, primarily with the intent of making all existing Notes apps dual-interface.

I've actually done much more Notes client than web work throughout the last 10 years, including in my current gig. I've done plenty of Domino web stuff too, but nothing to match the depth of my client development efforts.

My philosophy is to build client apps when the Notes client is fully deployed in an organization, unless some other factor justifies otherwise. I've found that sometimes an application was built for the web as opposed to the client more to satisfy the developer's desire to experiment than anything.

I do think that as opportunities to use web services, etc. and create compound applications (or whatever term applies) increase, and as Ajax and other UI enhancements close the functionality gap, my calculus will likely shift.

(Hi Chris, long time reader, first time poster... :)

When I was in consulting, I worked almost exclusively on web-based apps. Now that I'm a regular IT joe at a company where everyone has the client, 98% of my work is client-based. I miss the web development like crazy, to be honest, but I'm gradually (grudgingly?) learning to appreciate the client work as well...

Most of the development I have done over the last 5 or 6 years has been a combination of both web and Notes. Most of the time, the application needs to work the same for both clients. But there are times where the application will only be used via the web or certain things, like Rich Text, that can only be done in Notes. It's amazing how some things on one interface is incredibly easy while it's either frustratingly hard or impossible to do with the other client. Working in a Notes client only environment after doing a lot of web work will make you appreciate some of the things that Notes gives you.

Sean---

Although I was hired in my current job to convert most Notes apps to browser apps, the project was subsequently scrapped and now all my work is for the Notes client.

Client client client, day in, day out... :) Got a web project on the horizon next month, but overall, I'd say it is about 10% web, 90% client.

Hey partner,

( long time listener, seldom a reader, first time poster... :P ) (( I speak with Chris every night before bed time ))

For many global companies development has been limiting. If development occurs it is all in the Notes Client.

For the various small clients: they try to do web development ( thanks in part to Microsoft and its push for web development ) but then they realize the Notes client has all they need.

Being an IBM employee, the small apps I build for internal/dept needs are all client-based.

But your blog has got me thinking and I'm now asking my Domino admin if I could create web-based ones instead, and use all the "coolz coding skillz" I have ;)

Most of our custom work is still for the Notes Client. Our internal user base all have the client installed. However, we have done some work to integrate domino based forms into our internal portal and use the Notes client for the processing that happens after submission. It fits the Notes client model but facilitates locating the form/request.

Entirely client. I've tried to get into the web side of things, but the .NET people in my company have established pretty tight control over that side of things. In my company Notes/Domino is exclusively relegated to internal apps, and we are losing ground there, too.

Client client and more clients. I've been working as a developer/administrator for eight years and all the work available is 75% Lotus Client with the rest Domino development.

The .Net and Sharepoint people still have a minor issue with security and hackers to acknowledge, address and resolve :). The government is starting to realize this with government sites being hacked daily. <Thanks Bill for the job security>

Working the little yellow ship that still can.

90% client, 10% web, kind of like everyone else. And i'm the only web designer there is. (Coincidentally enough, my employers are governmental-based, and we use Lotus/Domino for the main reason that Kelley said above me.)

After spending heaven only knows how much time getting Domino to do what Cold Fusion developers can do with one hand behind the back, I finally realized this;
Notes is optimized for one thing, building applications for the Notes client. Yeah it can do web and all sorts of integration, but those things are comparitively painful. I have refocused my efforts on building awesome applications for the Notes client and will use other tools when appropriate.

In our company we develop standard applications for Lotus Notes/Domino. In this year many customers ask for applications which can be used in the web browser and run on the Domino server. Thus, in this year we develop more do extend the Domino databases for web browser usage. Besides me, my colleagues in our consulting team develop more for the Notes client as the for web browser. But unfortunately our development based on R6 and not on R7, since most of the customer use the R6 client.

We still do more development for the Notes client than the browser. When the customers have the Notes client installed, it makes sense.