The Benefits and Challenges of Using Container Controls in WEB2

Container controls offer tremendous value to developers. Their ability to pre-package groups of controls, especially labels and fields, promotes consistency throughout an application’s UI. We’ve integrated them extensively across our web application because they significantly expedite the development process. The feature where controls can be nested within other controls is especially commendable.

However, there’s a significant challenge we’ve observed: performance degradation when multiple container controls are employed on a single page. Using more than three or four on a page results in noticeable lag. In several instances, we’ve had to revert our design, breaking down the container back to its basic elements to achieve an acceptable load time.

I acknowledge and appreciate Xojo’s mission to ensure uniform functionality across different platforms. While development consistency is important, from our experience, the efficient performance of complex container controls in Web2 is currently lacking and thus is not consistent real world cross platform development. (Essentially, you can develop the same way, but it won’t work when you deploy it)

To address this, I’ve initiated feature request #73570. I kindly urge Xojo Inc. and Geoff to consider dedicating resources towards optimizing the performance of container controls. Such an improvement would not only benefit our team but also countless other developers who leverage these controls for their web applications. Please vote it up.