Exporting 'shiny' applications with 'shinylive' allows you to
    run them entirely in a web browser, without the need for a separate R
    server. The traditional way of deploying 'shiny' applications involves
    in a separate server and client: the server runs R and 'shiny', and
    clients connect via the web browser. When an application is deployed
    with 'shinylive', R and 'shiny' run in the web browser (via 'webR'):
    the browser is effectively both the client and server for the
    application. This allows for your 'shiny' application exported by
    'shinylive' to be hosted by a static web server.

Assesses the number of concurrent users 'shiny' applications
    are capable of supporting, and for directing application changes in
    order to support a higher number of users. Provides facilities for
    recording 'shiny' application sessions, playing recorded sessions
    against a target server at load, and analyzing the resulting metrics.

Track and record the use of applications and the user's interactions with 'Shiny' inputs.
  Allows to trace the inputs with which the user interacts, the outputs generated, 
  as well as the errors displayed in the interface.

Easily integrate and control 'Lottie' animations within 'shiny' applications', without the need for idiosyncratic expression or use of 'JavaScript'. This includes utilities for generating animation instances, controlling playback, manipulating animation properties, and more. For more information on 'Lottie', see: <https://airbnb.io/lottie/#/>. Additionally, see the official 'Lottie' GitHub repository at <https://github.com/airbnb/lottie>.

Provides functions that wrap HTML Bootstrap
    components code to enable the design and layout of informative landing home
    pages for Shiny applications. This can lead to a better user experience for
    the users and writing less HTML for the developer.

Simple and secure authentification mechanism for single 'Shiny' applications.
    Credentials are stored in an encrypted 'SQLite' database. Source code of main application
    is protected until authentication is successful.