Latest Updates

Products & Applications

My Blackberry Enterprise Server Push Utility for the Lotus Notes Client, allows you to create Jobs for individual Channel, Message, and Browser Content Pushes, as well as allows you to delete Pushed Channel Icons from defined recipient devices.

Time Tracker
The idea is simple. At the start of your day - upon completion of your first task - create an entry highlighting what you did and whether you feel it was an efficient or inefficient use of your time. Based on several requests, you can also select the priority, apply categories, or even align your time against a project.

For Lotus Notes Client v8.0 and above, you can use the Time Tracker Widget to make this process even easier!

My Configuration-based Rich Text Mail Merge and Emailing Utility, Zephyr allows you to create rich, data-driven emails to support automated workflow - all via Microsoft Word Mail Merge-like architecture. Dear <firstname> allows you to personalize each email message not only to the individual recipient, but also to the individual application workflow event!

xCopy is a simple configurable xCopy client for the Lotus Notes client. By creating and defining xCopy Profiles, you can batch process your file backup or remote upload jobs. With the addition of the xCopy sidebar widget, you can easily kick-off these jobs, and modify both the xCopy Profiles and xCopy itself.

Community & Resources

Lotus Technical Information & Education Community

The Lotus Technical Information & Education community is comprised of IBM, business partner, and customer subject matter experts who use product wikis, published articles, white papers, community blogs and the latest in social media to build and share high quality technical content. - Open Source Community for Lotus Notes Domino

OpenNTF is devoted to enabling groups of individuals all over the world to collaborate on IBM Lotus Notes/Domino applications and release them as open source.

developerWorks Lotus : Wikis

Share your deployment experiences and best practices in our wikis and help IBM to create scenarios for successful deployments. Contribute to the community by collaborating on shared content and leverage the shared knowledge from that community.

Welcome to!

Focused on being the go-to resource for the IBM Lotus Notes Domino developer, delivers introductory-level best practices and advanced development deep dives for the IT professional, book and gadget reviews, and technical weblog, and more!

Application UI Development - Lotus Notes Client Standards or 'Teh nEw H0tn3ss'?

05/01/2009 03:30:12 PM by Chris Toohey

I've been - as several people suggested - following a Twitter keyword search for "Lotus Notes".

Note: I warn any yellowbleeder thinking of doing this - you will hear the most inane, hate-filled, and saddening complaints about Lotus Notes you've ever heard. Twitter - if anything - has given everyone creative license to air their grievances, and creates 140-character Internet Tough Guys.

Some complaints are valid, of course, but one in particular made me stop and think. Here's the exchange:

In training for lotus notes 8.5. Now it sucks *and* uses all your ram!

My response:

curious - and not trolling - what don't you like about Lotus Notes?

And their responses:

it's slow, uses strange non-standard ui for no reason, and I've never used an app with a more cluttered interface

it's all about the ui. its 2009. Don't give me a 1994 interface! I'm used to macs and iPhones!

This got me thinking... How should we be developing our Lotus Notes Client applications? I understand the move to Web 2.0-UIs for Domino Web Applications, but the vast majority of Lotus Notes Client Applications have a similar basic layout:

An example of a typical Lotus Notes Client Application User Interface

Left-hand navigation, top-row action menu, and a NotesView pane where all of the action is. NotesDocuments are often modified via Open in New Tab, ModeChange to Edit Mode, Save and Close. Some Notes Client Applications allow for multi-NotesDocument processing via gutter selection, clicking an action from the View Design Element's Action Bar, and finally refreshing the NotesUIView.

Is this wrong? Wait... that's not fair. Does this meet the user experience expectations set by the majority of today's consumer-facing, popular, and heavily-adopted solutions?

I guess my real question is this: If you were not restricted by limitations of the given client, how would you design your application user interfaces?