Project Overview

Technical Objectives

Scalable Platform for Multi-Tenant Ecosystems:
The platform is engineered to be scalable, meaning it can handle an increasing workload or expand in response to growing demand without compromising performance. This scalability is crucial for multi-tenant architectures, where the platform hosts multiple clients or tenants, each with their own set of data and user base. The design allows for a flexible number of functions, which means that as new tenants come on board or as existing tenants' needs evolve, the platform can accommodate these changes seamlessly. This adaptability ensures that the platform remains efficient and cost-effective, as resources can be allocated and adjusted based on the specific requirements of each tenant.

Native Mobile Application Development for iOS and Android:
The platform supports native mobile application development for both iOS and Android operating systems. Native apps are built specifically for the platform they are intended to run on, utilizing the software and hardware capabilities of the devices to the fullest. This results in applications that perform better, are more reliable, and offer a higher degree of user experience with smooth animations and responsive interfaces. Native development also allows for the use of platform-specific features, such as push notifications, camera integration, and GPS, to enhance the functionality of the app.

Highly Customizable CMS System:
The platform includes a Content Management System (CMS) that provides a high level of customization. The CMS enables administrators to toggle features on and off, manage system records, update static content, and configure various aspects of the application. This flexibility allows for rapid adaptation to changing market trends or user feedback without the need for extensive redevelopment. The toggle feature is particularly useful for A/B testing and rolling out new features in a controlled manner, as it allows for selective enabling or disabling of functionalities for specific user groups or tenants.

Open for Third-Party Cooperation and Collaboration:
The platform is designed to be open and collaborative, allowing for third-party features to be integrated through a plugin system. This openness encourages cooperation and collaboration with external developers, vendors, and partners, who can contribute their own plugins and features to the platform. The plugin system facilitates the addition of new functionalities without the need to modify the core application, making it easier to expand the platform's capabilities and offer a broader range of services to end-users. This approach also enables the platform to tap into a wider innovation ecosystem, as third-party developers can bring in fresh ideas and cutting-edge technologies.

Technical Components

AOK Mobile Platform (AMP) will be the foundation of the Navida App with AMP Frontend, Backend and CMS

AOK Navida Pro App's architecture is built to be modular and extensible, with a strong emphasis on ease of integration and management of plugins. The Open Contract provides a clear framework for plugin development and lifecycle management, while the unified API gateway and BFF concept ensure efficient data handling and a streamlined user experience. The ability for each AOK to independently manage content and configurations enhances the flexibility and responsiveness of the app to meet the evolving needs of users

Plugins Developed Internally and Externally
The architecture of the AOK Navida App is designed to support plugins, which are essentially add-on functions that can enhance the app's capabilities. These plugins can be developed both internally by the AOK's own development team and externally by third-party developers. This dual approach to plugin development allows for a rich variety of features to be added to the app, catering to the diverse needs of users. Internal development ensures that core functionalities align closely with AOK's strategic objectives, while external development opens the door to innovative features and integration with other services.

Automatic Linking of Open Contract, Base App, and Plugins
The system utilizes an "Open Contract" model, which is a set of predefined rules and specifications that describe how plugins interact with the base application. This model ensures that when a new plugin is developed, it can be automatically linked to the AOK Navida App without the need for extensive manual integration work. The Open Contract defines the life cycle of a plugin, from development and testing to deployment and maintenance, ensuring that all plugins are compatible with the base app and can be integrated smoothly.

Lifecycle and Integration of Plugins via Open Contract
The Open Contract not only facilitates the automatic linking of plugins but also details the lifecycle and integration possibilities of each plugin. It acts as a blueprint that developers follow to ensure that their plugins can be easily incorporated into the app's ecosystem. This includes guidelines on how plugins should be structured, how they communicate with the base app, and how they can be updated or retired. By standardizing the integration process, the Open Contract simplifies the management of plugins and maintains the stability of the app.

Unified API Gateway for Backend and CMS Access
The architecture includes a unified API gateway that serves as the single point of entry for frontend applications to access backend systems and the CMS. This gateway streamlines the communication between the frontend and backend, providing a consistent and secure way to retrieve and manage data. It simplifies the frontend development by abstracting the complexity of the backend services and ensures that all data exchanges are routed through a central, controlled environment.

Preparation of Third-Party Data via Backend Services - BFF Concept
Third-party data is processed and prepared by dedicated backend services following the Backend for Frontend (BFF) concept. This approach tailors the backend services specifically for the frontend's needs, optimizing the data and interactions for the user interface. The BFF layer acts as an intermediary that formats and aggregates data from various sources, ensuring that the frontend receives data in the most efficient and usable form.

Independent Content and Configuration Editing by Each AOK
Each AOK has the autonomy to edit and create its own content and configurations directly within the system, without the need for additional developer intervention. This empowers content managers and administrators at each AOK to tailor the app to their specific requirements and preferences. They can update information, adjust settings, and customize the user experience to reflect their branding and operational needs. This level of control reduces the dependency on developers for content updates and allows for more agile and responsive content management.