User experience (UX)

Develop your app and UI once & use it on any device

OS.bee applications feature great user experience (UX) due to its genuine user interfaces (UI) no matter if on desktop browsers, mobile or any other device, utilizing the power of the included technology stack such as the Vaadin framework, BIRT and mxGraph. OS.bee increases the productivity of developers at the same time as the ergonomics of its applications with a mature application layout model (E4), easy modeling of views as well as unique automation features such as auto-binding and auto-layout.

Stunning user experience with OS.bee

Sophisticated Application Layout

Perform your daily work using 360° insight into all data needed for your business. Users are never forced to navigate around to get necessary information for their decisions. All information is at sight, at any time. 

The structure of an OS.bee application (OS.app) relies on the Eclipse E4 application model, which provides a very flexible way to determine how the application frontend can be subdivided. E4 elements can easily be nested in any structure to express every use case in a comprehensive frontend. In other words, end user applications build with OS.bee benefit from the well-known Eclipse IDE ergonomics.

Learn more about perspectives

UI and layout components

In OS.bee, UI and layout components can easily be defined and laid out either using a graphical WYSIWYG editor or by editing UI DSL instances. 

The UI DSL provides binding mechanism, referencing data transfer objects (DTO) and application logic triggering such as validation or conversion. A sophisticated auto-binding algorithm disburdens the modeler from manually binding visual components to data sources.

Find out more about the UI definition

Versatile views

OS.bee delivers typical visualization and interaction components that build a graphical user interface (GUI), including dialogs, tables (and grids), reports, charts, topology maps, business processes, and organograms.  All these features can be designed via distinct view model DSL. A view, once defined, can be reused on different parts.