DEV Community

Query Filter
Query Filter

Posted on

bridge-36

This document outlines the migration strategy and changes associated with retiring the Atom Launcher and transitioning its applications and features to Citi Desktop.

Here is a summary of the key sections and changes detailed in the report:

1. The Core Change: Retirement of Atom Launcher

  • Transition: The legacy Atom Launcher is being retired. All Atom-based applications will now be launched, managed, and accessed directly through Citi Desktop.
  • Transition to Distinct Application Definitions: In the old model, different variations or regions of an application (known as "streams") were grouped together under a single dropdown menu in the Atom Launcher. Moving forward, this model is superseded. Each stream will now be represented as its own distinct, independently defined application in the Application Directory.
  • Why This Matters: This shift moves the system toward a more modular, explicit, and granular application architecture, improving overall system visibility and backend management.

2. Operational Impact & Example

  • Granular Setup: For every existing stream, a separate application definition must be created in the Application Directory to ensure each variant is recognized as an independent entity.
  • The "DNAViewer" Example:
  • Previously, the application DNAViewer had three regional streams under the same system: NAM, APAC, and EMEA.

  • Under the new architecture, these are split and set up as three completely separate apps in the App Directory (each with its own distinct configuration link).

  • User Experience (UX): For end-users, these individual application definitions will appear as separate, clearly identifiable menu items within the Citi Desktop Navigation Menu, maintaining a familiar layout but offering a cleaner backend structure.

3. Introduction of Multi-Version Application Launching

  • New Capability: Citi Desktop will now natively support launching multiple versions of the same application. This is highly beneficial for development, testing, and operational teams who need to jump between different application iterations or verify specific builds.
  • Opt-In Mechanism (Crucial Action Required):
  • Unlike the old Atom Launcher, which granted automatic access to multiple streams, this multi-version feature in Citi Desktop is strictly opt-in. It will not be enabled by default.
  • Required Action: Users who need to launch multiple versions must manually enable this feature. To do so, navigate to Citi Desktop user preferences and toggle the setting on.

4. Technical Underpinnings: Streams and the NGD System

  • User Groups within Streams: Stream configurations will utilize user groups to facilitate phased rollouts. This allows specific application versions to be deployed to a subset of users (e.g., pilot or beta testers) independently of the broader user base.
  • NGD System Installation: The underlying NGD (Next Generation Desktop) system manages the physical installation of specific stream versions on a user's machine. The deployment agent will only download application versions that match a user's designated stream, environment, and user group profile.
  • Citi Desktop Detection: Citi Desktop dynamically determines which versions are available to run by reading the local NGD configuration files on the user's machine. It will only display and allow the launching of a version once the NGD system has successfully installed it.

Top comments (0)