- Someone wants a custom application created immediately to capture data. They're not concerned with working out the features now, but will tackle that later.
- A client wants a throwaway application now, instead of waiting for a more robust solution. However, that client later gets sticker shock and decides to make the best of what was built off the shelf.
- A Lotus Notes Domino project is sought out specifically for its well-developed application features.
In all cases, working best practices into your base template and design habits can help your application and Notes/Domino replication if your "throwaway" application is widely used in production for several years. After having to refit a number of applications that weren't expected to outlive the quarter they were built in, I've noticed some common attributes of applications brought into the shop for repairs, including poor performance, interface adjustments and application expansion needs. I will touch on these topics in this tutorial.
Tutorial: Lotus Notes Domino application development best practices
Part 1: Improving Lotus Notes Domino application performance
Part 2: Tweaking the Lotus Notes Domino application interface
Part 3: Expanding or modifying a Lotus Notes Domino application
|ABOUT THE AUTHOR:|
Paul Stockinger is currently certified as an IBM Advanced Developer for Lotus Notes/Domino 6 and 7 and has designed Notes and Domino applications since 1997. He can be reached at firstname.lastname@example.org.
This was first published in June 2008