Forum Discussion
Impactful Individualwhat can i expect from mobile
hi its been years since i stood up a mobile version of a report created in my own personal tenant. i may need to do the same now for my company's tenant.
im looking at the report (not dashboard) in question and wonder a few things. is the fact that its a report going to limit me in picking which visuals to make most prominent? honestly maybe 10% of what i see seeems like it would be useful in a mobile display where real estate is at a premium.
also we have a handful or 2 of slicers. and 3 radio buttons down left that determine what perspective (facility, customer, product) should show in one top 10 table visual. are any of those (slicers or radio) fair game in a mobile rendering?
Hi. I don't know how much is years. But I know users that appreciate the mobile view. Now you can build specific mobile view of each page of a report. It let's you pick visuals from the original page to make it easier to read. The idea is that mobile should keep easy to read and fast to manipulate things. If you expect users to click like 10 times and check three visuals at the same time, that's not a good UX for mobile.
The mobile view let's you adapt the filters pretty good to let the user use them and check visuals.
Tables are something that it's always unconfortable for mobile unless it's a small one. If it has too many columns you scroll a lot, and if it has many rows the scrolling UX mixes with scrolling the report canva.
I hope that helps,
3 Replies
- ShivekMaharaj
Memorable Member
Hi db042190,
You are not limited just because this is a report rather than a dashboard.
Power BI lets you build a separate mobile-optimized layout for each report page, and you do not have to place every desktop visual onto the phone layout. You can choose only the visuals that are useful on mobile, or use the auto-create option as a starting point and then simplify it. Microsoft documents that under mobile layout view.
For your slicers, I would definitely keep them if they are important to the workflow. Microsoft specifically supports slicers in mobile layouts and recommends making them compact/responsive for smaller screens.
The three radio-style options for Facility / Customer / Product should also be fine if they are implemented as slicers or buttons. The current mobile layout canvas is interactive, so you can actually test the slicers, buttons, and visual interactions while designing the mobile version.
What I would avoid is trying to reproduce the full desktop page exactly. If only 10% of the desktop content is useful on a phone, that is completely reasonable. I would treat mobile as a focused companion view rather than a scaled-down desktop report.
A practical layout could be:
- Facility / Customer / Product selector at the top
- One or two compact slicers underneath
- The most important KPI/summary visuals next
- Detail visuals further down only where users genuinely need them
Microsoft's mobile design guidance also recommends horizontal slicers/navigation where possible and removing unnecessary titles, legends, and other detail to preserve screen space.
So yes, slicers and your perspective selector are fair game. The main design decision is really which visuals deserve to survive on mobile, not whether the report type prevents you from using them.
AI-assisted drafting: AI was used to help structure and phrase this response. I reviewed and validated the technical content before posting.
- DataTako
Resolver IV
Hi,
Being a report actually helps you here. In Power BI Desktop there's a dedicated Mobile layout view (View > Mobile layout): a phone canvas with a tray of all the page's visuals, and you drag on only the ones you want. So your "only 10% is useful on mobile" instinct is exactly the point, you curate a small prominent subset rather than cramming everything in.
Slicers are fair game and stay interactive in the mobile app. Your three radio buttons work too: if they're a single-select slicer they behave like any slicer, and if they're Button visuals wired to bookmarks those render and fire in mobile as well, so your facility/customer/product switch carries over either way. Just note mobile layout is per page, so set it up for each page you want optimised.
If this helps, please mark it as the solution.
Paco
Helping data analytics leaders distribute their reports - ibarrau
Super User
Hi. I don't know how much is years. But I know users that appreciate the mobile view. Now you can build specific mobile view of each page of a report. It let's you pick visuals from the original page to make it easier to read. The idea is that mobile should keep easy to read and fast to manipulate things. If you expect users to click like 10 times and check three visuals at the same time, that's not a good UX for mobile.
The mobile view let's you adapt the filters pretty good to let the user use them and check visuals.
Tables are something that it's always unconfortable for mobile unless it's a small one. If it has too many columns you scroll a lot, and if it has many rows the scrolling UX mixes with scrolling the report canva.
I hope that helps,
