The requirements for the two teams are fundamentally different. The internal analyst team needs a comprehensive, detailed application for deep analysis, which is best suited for a desktop experience. The sales team needs a streamlined, simplified, and touch-friendly application optimized for mobile devices, focusing on key performance indicators.

Creating two separate apps allows for a purpose-built user experience for each group without compromise. The mobile app can be designed with a single-column layout and fewer objects for clarity and performance, while the desktop app can provide the complex, multi-chart "global view" the analysts require. Both apps can leverage the same underlying data model to ensure consistency.

A. One app with a specific extension for mobile users: An extension cannot fundamentally alter a complex app's layout to make it suitable for a small screen; it only adds specific functionality.

C. A mashup with various objects: A mashup still faces the same design challenge of serving two different experiences and would likely require separate, tailored web pages, making it a more complex solution.

D. One app with various objects: A single, complex app designed for a "global view" will be cluttered and difficult to use on a mobile device, even with Qlik's native responsive capabilities.

1. Qlik Sense® on Windows Help: In the section on creating visualizations, the documentation provides guidance on responsive design. It explicitly states, "For small screens, it is a good practice to design the sheets with a single column layout" and to "Limit the number of visualizations on a sheet." This advice for mobile design directly conflicts with the requirements for a "global view" for analysts, supporting the need for a separate, optimized mobile app.

Source: Qlik Sense® on Windows Help, "Creating visualizations" -> "Building responsive apps" -> "Tips for creating responsive layouts".

2. Qlik Sense® on Windows Help: The best practices for app design emphasize tailoring the application to the intended audience and their needs. When audiences have conflicting needs, such as deep exploration versus quick mobile access, creating separate, targeted apps is the standard approach to ensure usability and adoption for both groups.

Source: Qlik Sense® on Windows Help, "Creating apps and visualizations" -> "Best practices for designing apps".