The concept of useLib offers digital sovereignty, software ergonomics, accessibility as well as data protection, IT security and legal conformity on the most varied of viewing levels. The integrated implementation of workplace and BITV regulations as well as integrative software and usability engineering are guiding principles of the concept. It is based on the platform-independent use of HTML5-enabled browsers, whose capabilities are fully utilized and specifically expanded using clever JavaScript programming. Central is the software-ergonomic optimized interaction:

• • Various new form input fields (widgets) from 3-month calendar to bank details with integrated IBAN check and BIC mapping are integrated parts.
  • Complex selection tasks are massively improved, especially multiselect becomes a simple interaction task here by means of a innovative, automatically generated dialog window.
  • The useLib can be easily integrated into existing cloud applications and websites.
  • Existing input fields and selection lists are simply dynamically overlaid, the original contents continue its function!
  • By means of a configuration file: useLibConf.js the useLib can be adapted exactly to the need via Tailoring.

The decentralized concept of useLib, its extensions and accompanying HTML applications makes the designation as framework not quite appropriate. Nevertheless, this is probably the most common suitable paraphrase, since the useLib can be embedded in existing websites. However, the useLib really starts where others stop and this without installation. In particular, the software-ergonomic optimizations can also be seamlessly integrated into a wide variety of frameworks.

The content is based on more than 35 years of experience in operational processes, IT, software ergonomics and usability from various projects or research work and on many years of continuous development work. Also the development and maintenance of the data structures provided for input support or control and much more. E.g. IBAN check needs support.

You can rely on the overall concept with the accompanying tools that can also be used separately. Then HTML-Apps are created, single-file-multi-side-applications whose surprisingly small files can also be sent via email, much like a single-side page. These HTML files work like Excel- or Word files up to an entire Internet portal. However, no office package is required, just a standard Internet browser. This is also how the grey IT can be channeled! Extensive documentation with various form examples can be found in the HTML file of the useExamples-App.

Using simple wiki syntax, employees can describe highly complex forms. Form content can be saved temporarily or permanently in the individual HTML files. If necessary or after processing has been completed, the data can be transferred to one or more framework(s) or servers. The processing server (backend) delivers and receives only standardized data. Update or other information can also be displayed. At the highest security level, SHA3-512-encrypted local storage and viewing can also take place using 2-factor authentication. Optionally, an external check of access authorization and the integrity of the JavaScript++ is integrated.

The HTML apps are created using the useEditorApp, which copies itself, so to speak, and saves it locally with new project-specific content. The result can be tried out directly in a preview window. It is an HTML-based wiki editor that can be operated locally or in the network. External texts can also be processed. Freely scalable - also purely graphical surface designs - for different work environments, situations and devices, but also ametropia can be corrected using the useSkinnerApp create and view via direct interaction. Further supplementary HTML-APPs for card sorting, prototyping etc. generate a complete security and usability engineering process as a service, also in online group sessions.

Of course, the results of group work can be saved with useCardsort and usePrototype as Export wiki texts. These texts can then be further processed directly in the useEditor. It is deliberately not a highly integrated development environment, since separate processing should be possible, for example for special work tasks. But also the necessary connection to tools and their file formats etc. is omitted. This is also an element of digital sovereignty.

The development environment is the local user interface with its file system. The organization can therefore use organizational rules, e.g. for file names or with an already used management system. The transition from explorative to evolutionary prototyping using large sample data sets can not only always be freely adapted to the respective requirements, but also highly effectively and efficiently implemented.