My suggestion is a new view feature that allows you to create hidden view from the user, similar to the internal views, but these view will have the ability to autocomplete for the name when programming an @DbLookup, @DbColumn, Lotus Script getView, etc. ..
These views can display the designer elements that have calls to them and are using them in the form of a diagram, to prevent any developer from altering or deleting a view that is used by certain functionality and therefore causing errors in the application.
Example: The application is divided into 8 nsf databases, containing more than 200 views, it presents performance problems after an analysis, the solution found was to exclude redundant views, but the problem is that a large application, when deleting a view, can there is a risk of causing errors in certain features of the application used by one of the 8 databases, such as a field doing @DbLookup in one of the views. How these features or something like that can show you visually and quickly where the vision is being used will prevent problems like this from occurring.
It would also be useful for this new view to allow the column information with the document data, to be displayed in the Notes standard or in clean JSON format, to facilitate the development of new APIs.