Submit Your Suggestions For Field View

While I can see that for quite a few years (even back in 2016) there have been upvoted requests for introducing various formatting and presentation improvements, these have not been implemented, despite the technical simplicity of such upgrade. Frankly, the whole thing needs to be brought up to 21st century.

Luckily, it's 2023, and software development is a breeze, especially when it comes to UI controls.

Problem:

• Reports, which are a deliverable of high importance, are simply of generally low quality, neither presentable nor easily read/reviewed.

• Working forms are equally suffering from lack of features that make certain things stand out, sections grouped together, or intentionally sufficiently separated to be easily distinguished from each other, etc.

• The little bit of formatting there is (in text fields), is displayed differently on different platforms. For example, on Windows app formatting is lost altogether. Even "View report" on device apps gets buggy and includes text fields that are specifically marked not to be displayed in report

Solutions/suggestions:

• Implement various basic tools to text boxes and various other controls. Some very welcome basics would include text/fill colour and font size&style.

• Implement a way to visually group, or purposefully separate, sets of questions. This is especially important in the final report, but just as needed while filling live forms on devices where screen real estate is limited, and users don't have proper overview of where in form they are. This could be done by varying background colours between 'groups', custom indentation (more than what seems like barely 1 pixel in current implementation), or even simple geometrical shapes - questions in the same group could be bounded by a rectangle, as an example of a simple yet effective visual communication tool.

• For questions with logic that enables/disables groups - make them work at any level (currently only top level groups can be accessed), and allow option to not display disabled groups in report (or indeed live form), if creator so choses.

Coding side of things is trivial, even in the stable branch of product, so I cannot see why a willing and dedicated developer couldn't implement above suggestion in a very short cycle. But I also appreciate that some of these things will have additional, albeit seemingly small, impact on database, and you may not be able or willing to take that load. Even then, at least for now, workarounds could be made that would make use of predefined styles, colours, shapes, etc. That would reduce both the storage implications (it adds up when you have millions of forms), as well as number of database queries.

I hate to had written that last paragraph, because it basically spells concessions and encourages workarounds (not unlike many other things in FV, unfortunately). But I also live in real world, and have real clients, so if developers were unable to deliver on similar other suggestions in the past 9 years, I would be fool to expect miracles today.

I guess, what I am saying is - give us any kind of improvement now - even if suboptimal.