1 How Do Mendix Web Apps Work?
Using the WYSIWYG page editor in the Mendix Modelers, users can model pages and interactions that can run locally or be deployed directly from the Modeler. When running locally, the changes are made visible directly. This is done with our instant update feature that instantly reloads the UI while preserving the current state, making testing and previewing apps a breeze.
2 How Does Mendix Support Different Screen Sizes and Devices?
Mendix pages are responsive by default, so they automatically adjust to screen size. This results in web apps that look great out of the box on screen sizes from desktops to phones. For an optimized user experience, it is possible to define separate mobile web channels for phone and tablet. The device type (as in, phone, tablet, or desktop) can also be used in the logic for other scenarios.
Mendix provides several common patterns and best practices per device to help you build great user experiences. You can also extend these patterns with custom variants, as discussed in User Interface Design.
3 How Can I Extend My Web App?
Both the index.html and login page can be fully customized to your needs. It is also possible to add additional resources like styling and images or to provide a Web App Manifest.
Mendix offers several options for extending web apps. These are discussed in the section How Can I Extend the Mendix Front-End? of Front-End and the section How Can I Customize the Look and Feel of My Apps? of User Interface Design.
4 How Can I Test My Web App?
Mendix offers an integrated Application Testing Suite (ATS), in which (non-technical) users can test web applications using recorded test scripts on multiple browsers and multiple devices.
It is also possible to use standard test tooling, like Selenium. Because Mendix widgets have unique identifiers in the document object model (DOM), test tooling can easily leverage these IDs to create readable and robust test scripts.