MX-Client was developed for several reasons. First, to help developers build applications faster. By taking care of the execution, MX-Client allows the developer to focus only on application content. The main purpose of MX-Developer is to design the application content, whereas the client's job is to execute it. MX-Client recognises the content developed with MX-Developer and presents it to the end-user. MX-Client is contentless and as such it is suitable for hosting any type of content, from home applications to enterprise applications.

Second, MX-Client ensures that all applications have a uniform "look and feel" and consistent behaviour, which improves overall user experience and enhances application recognizability.

Creating new user account in MX-Client

Next, when developing competitive business applications, the so-called system features such as login, user account management, security, localization, application settings, etc. cannot be avoided. Their implementation is time consuming, which means less time for content development. MX-Client shares this burden with the developer. A rich set of built-in system features saves time and leaves the developer to focus on content. All system features of MX-Client are easy to manage and highly efficient.

Sample MX-Client application

Many developers know that developing multi-user applications can be a real nightmare. Each user has his own ideas about how the interfaces should look: one user wants to change the position of the controls; the other wants to hide a field in a grid; the third wants to group or filter data, etc. In this case, personizable user interfaces would be the best solution, but also the most difficult to implement. Just imagine yourself worrying about how to make the user interface personizable, how and where to save changed layouts, how to create new versions of layouts, how to bind layouts to application profiles (user or workgroup), how to manage layouts, etc. By default MX-Client supports all these functionalities.

In the world of globalization, applications are often developed for different language regions and the localization becomes an important aspect in terms of competitiveness of the application. MX-Client supports localization. Knowing that MX-Client is a .NET application, which supports localization inherently, one might think that then is no real advantage in MX-Client. But .NET Framework only offers the option to have a text associated to control in different languages, which is usually not enough. User often expect from an application to support language switching and binding specific language to some application profile. And developer knows that this functionality demands time and increases the costs. With MX-Client, the user can manage all visible descriptions in any language, change the applications language on the fly and bind localization to a specific profile.

Runtime localization editor which also enables creating new languages.

With the increase the use and complexity of computer systems, security becomes a very important issue. Usually the use of an application functionality is permitted on basis of security credential. Users have several applications installed on their computer and each of them has their own security accounts. One account for all applications would be much better.  Usually is this ensured by the domain account. But implementing a security model that would satisfy customer needs is all but easy. Developers usually do not have enough time to develop a security model which can be reused in another application without adapting the source code. The developers of MX-Client took that time for you, and developed a sophisticated security model and integrated it into MX-Client. The model allows the protection of every aspect of the application which can be based on combination of security entity such as user, workgroup, application role, workstation and work place. In MX-Client, all the security is managed in runtime without need to recompile the application. In addition, all application developed with MX-Developer will have a uniform security model which means simple its management and use, and reduces development time.

Software development is a laborious and error-prone job. Applications often have a complex user interface with several mutually linked combo-boxes and grids with master-detail relation. Finding an error in such case is difficult, takes time and requires good debugging skills. Early detection of the cause and quick removal of the error is crucial for ensuring an efficient application and a satisfied customer. This was the concerns of MX-Client developers who succeed developed diagnostics tools that helps the developer establish, recognize and fix any design-time or content error appearing in runtime. With tools such as data profiler and workflow profiler, the developer can easily pinpoint the error and remove it with MX-Developer.

MX-Client built-in profiler for various diagnostics

When analyzing a business process the history of data changes is very helpful, because it contains information about who and when changed the data, the values, etc. MX-Client can track any data change in the application, and the integrated Audit Trail Viewer enables the user to easily analyse history of data modifications. This enhances transparency of data modifications.

Beside analyzing data modifications, the user sometimes requires that important actions within the application are authorised. MX-Client contains the feature of Electronic Signature which can be used to authorise any action and thus prevent malevolent use of applications. When functionality such as audit trail or authorisation with electronic signature is required, MX-Client can significantly reduce the cost for its development.

Special care was given on the Client's performance. MX-Client runs smoothly even when processing a huge amount of data. Then user practically cannot distinguish whether the application manipulates with small or large amounts of data. This is an important advantage: your application will give highly professional look and satisfy even the most demanding customer.

Reports are an integral part of almost every application and as such also a frustration for any developer. Each user has his own requirements for the reports, so normally for each report change the application hast to be recompiled. This endless changing of report design takes an enormous amount of valuable time. The question is how to reduce or even better, avoid this enormous waste of time. The answer to this problem is a run-time report designer which enables the user to redesign the existing report and customize it to his needs in run-time. Such redesigned reports can be then saved, make it available for other users or set as default reports. All versions of a report are available through report repository. The user can change between different report versions from the repository on the fly without restarting the MX-Client.

MX-Client runtime report designer which also supports report versioning.

The look, functionality and behaviour of the MX-Client are also completely personizable. The user can redesign Client's look to meet his demands at any time. Functionalities can be removed, application skins can be modified, the client can behave as MDI application, etc.