I believe the devs are just unaware of early UI / UX tenets, mainly because they've left the native Delete button and the Sort button for the end user as I can notice in the video. The Delete button is dangerous and the Sort button exposes a very foreign window mechanism to users.
Many consider the native FM status bar as being strictly a dev tool and only a certain admin or two on the client side might be granted access to it for particular solutions. They're free to work with the status bar on their own files if they care to.
Many times record navigation can have deep dependencies when simply entering or exiting a record. Hence, requirement to use scripted navigation buttons and not the natives. Also revealed by the native sort button is, besides what are often foreign field names, the list of tables and their relationships. Users should not be exposed to such eyesores.
I'm afraid it gets worse.
When typical end users are provided the FileMaker tools, they closely associate the entire solution as being "FileMaker." If the user experience is less than delightful, "FileMaker" typically becomes the failure identified, and often the sole failure, especially if the user has no previous exposure to stellar FM solutions which savvy devs designate a thoughtful name.
For the lack of such awareness lost over the course of time, it's only one important reason Claris is battling the "less than stellar" past reputation of the FileMaker name. They let the brand get out of their control.
Fortunately it's all fixable. I recommend they start by controlling the Claris logo being used on certain Market Place offerings which are not really Claris products.