Of the three models, the most frequently used approach for bringing disparate products together is the modular approach. In this model, features from contributing products are modularized into UI containers of various sizes that contain summary data, lists/grids of data, or detailed views. These containers from the different apps can then be composed into the new platform. Interaction across modules from different platforms is often based on context (what data is selected), but little else.
This is often seen as a technically advantageous approach as it enables slightly deeper integration of the UI’s than the hub & spoke approach, but the modules can easily be created by federated design and development teams with a design system and a limited number of architectural standards. To the user, this can appear much more integrated than the disparate products were in the past. However, if individual tasks tend to run across the features from more than one of the contributing products, it can still feel like a cumbersome experience. When choosing this model, it’s critical to understand this relationship of tasks to functionality to understand if this is appropriate for your users. When tasks tend to cut across products, this model may not fully solve user issues.