With all of this said, designing for mobile isn’t just how much content you are including/excluding. Designing for mobile is realizing that because of a smartphone’s size, technical limitations, and interaction method, people don’t need or want to be able to do everything on their phones like they can on their desktop computers. We don’t want to have all the same features available on all devices.
The smartphone isn’t just a smaller laptop. It is a different approach to consuming & manipulating content. Don’t just take all of the same content from the desktop experience and find a place to cram it into a phone. You should design for smartphones with the knowledge of what your users want to know and accomplish on a phone, and design an experience to meet those needs. Similarly, knowing what your users will want to know or accomplish on a laptop, you design for that. There will certainly be overlap, and that overlap should maintain design consistency, but there will be things that don’t need to be included on the phone experience.
No smartphone experience is perfect but the best experiences give users all of the content they need on-the-go, with the features they will use, and excludes extraneous / hardly-ever-used features. When designing Qlik apps for phones: ask your client why users will be opening the app on their phones. What will they want to accomplish on a smartphone? Perhaps it really is to fully explore an application, or more likely it is to get some basic information and then close the app. Design for what they need and omit the rest.
For more information on designing for mobile, and user experience design for business intelligence in general, we have a guide of best practices available to help you create the best designed application.