I would like to report a UX issue in the Ninox App that has persisted for years and significantly affects workflow when working with larger Pages containing multiple Views. It is an extremely annoying issue that I believe Ninox should have addressed a long time ago if the company wishes to appear serious and credible.

The problem occurs when scrolling down a Page that contains one or more Views. As soon as the mouse cursor moves over a View, scrolling appears to stop. This is particularly noticeable when all records in the View are already visible and there is no additional content available for internal scrolling within the View itself.

As a result, the user cannot continue scrolling naturally down the main Page. To proceed, the mouse cursor must be moved outside the View before scrolling works again.

This feels highly unnatural, disrupts workflow, and is incredibly frustrating.

Expected Behaviour

When a View contains additional content, it should of course be possible to scroll within that View.

However, when the View has reached the top or bottom, or when there is no additional content available for scrolling inside the View, scrolling should automatically continue in the main window/Page.

This is standard behaviour in many modern user interfaces and feels intuitive to the user.

Current Behaviour

• The user scrolls on a Page.

• The mouse cursor moves over a View.

• Scrolling stops or becomes trapped within the View area.

• The main Page no longer continues scrolling.

• The user must move the mouse cursor outside the View in order to continue scrolling.

Consequences

For users building larger workspaces with many Views and sections, this becomes highly frustrating in daily use.

The issue causes:

• Navigation to feel cumbersome.

• Workflow to be interrupted unnecessarily.

• The user experience to appear less professional.

• Large dashboards and workspaces to become more difficult to use than necessary.

Suggested Solution

The View components should handle scrolling more intelligently by passing scroll events to the main Page whenever the View itself has no more content available for scrolling.

This would make scrolling feel seamless and natural while still allowing internal View scrolling whenever it is actually needed.

I hope Ninox is still willing to prioritise the desktop app to some extent and that this can be considered for improvement in future versions of Ninox App. This issue has a significant impact on the practical user experience in larger solutions, as well as on the credibility of the platform when evaluating whether Ninox is worth using at all, particularly with regard to server-based deployments.

No serious software vendor allows its products to continue carrying long-standing usability issues indefinitely. Such issues should be addressed in order to maintain a professional and trustworthy product.