Feature · Dashboard Apps

Dashboard apps that read on the phone, the laptop, and the big screen in the room.

A dashboard that only works on a desktop monitor fails the executive who checks pipeline on a phone before a board meeting. A dashboard that only works on a phone fails the operator building a tile library on a Thursday afternoon. Strkr's dashboard apps work on every surface a business reader actually uses: native mobile apps for iOS and Android, responsive web for desktop and tablet, and a conference-room mode for the big screen in the meeting room. Same data, same permissions, same refresh cadence on every device.

Start free trial See pricing
The dashboard-app shape

One dashboard, three surfaces, consistent experience.

A business reader interacts with dashboards across three surfaces: a mobile phone for the quick check between meetings, a desktop or laptop for building and deep analysis, and a conference-room screen for the shared discussion in a meeting. Each surface has specific requirements. The mobile app needs to be fast, legible without zooming, and work offline on the data from the last sync. The desktop needs to be dense, interactive, and supportive of building. The conference-room needs to be big, readable from the back of the room, and not require scrolling during a discussion. Strkr builds for all three with one dashboard definition and three rendering strategies.

Mobile first

The dashboard works on a phone.

Every dashboard renders cleanly on a phone screen (375px width). Tiles stack vertically. Numbers are legible without pinch-zoom. Interactions respect finger-size tap targets. The executive checking pipeline from the back of a cab reads the number without a desktop fallback.

Native iOS app

The dashboard in the pocket.

The Strkr iOS app ships every dashboard the user has access to with native iOS performance: offline reads from the last sync, push notifications on anomaly alerts, Face ID authentication, deep links from Slack or email to specific dashboards. The experience matches a native iOS app, not a web wrapper.

Native Android app

The same experience on Android.

The Android app ships the same dashboard capabilities as iOS: offline reads, push notifications, biometric authentication, deep links. The parity between the two platforms is deliberate so a leadership team mixed across iOS and Android reads from the same experience.

Responsive web

From 1440 to 320 pixels wide.

The web dashboard adapts fluidly from a 4K monitor down to a phone browser. Tile widths reflow, filter controls adapt to the available space, interactive elements scale to the input device (mouse hover vs touch). The viewer never needs a device-specific URL.

Tablet layout

A middle ground that works.

Tablet-sized screens (768px to 1024px) get a specific layout tuned for the aspect ratio: two-column tile grid, condensed filter bar, larger tap targets than desktop. The iPad in a meeting works well as a presentation surface, which some executives prefer over a phone.

Conference room mode

The big screen in the meeting.

A dedicated conference-room mode renders dashboards at TV resolution with legible-from-ten-feet typography, high-contrast color schemes, and no interactive elements visible unless the presenter chooses to show them. The team reviewing weekly pipeline sees the dashboard on the shared screen without a laptop display mirroring.

Dark mode

A dark theme that respects contrast.

Every dashboard surface ships with a dark theme that respects WCAG AA contrast ratios for text and chart elements. The dark theme reads better at night and in dimly-lit rooms. The admin can set tenant default theme or let each user pick their preference.

Accessibility

Screen readers, keyboard navigation, high contrast.

The dashboard app meets WCAG 2.1 AA accessibility standards: screen reader support, keyboard navigation for every interactive element, high-contrast mode, caption text for charts. Accessibility is a design requirement, not a retrofit.

Print layout

The dashboard reads on paper.

A print stylesheet renders the dashboard cleanly for a printed copy. Page breaks respect tile boundaries. Colors adapt to grayscale appropriately. The executive printing a dashboard for a board meeting gets a readable artifact without a separate PowerPoint pass.

The native mobile dashboard app

The experience on the phone, specifically.

The mobile dashboard app is where most executives interact with the data between meetings. The app is designed for the specific moments mobile is useful: a quick pipeline check on the way into a meeting, a push alert on a crossed threshold, a drill-in on an anomaly flagged by Strkr AI. The native app ships with iOS and Android parity, offline reads from the last sync, biometric authentication, push notifications, and the specific small-screen UX patterns that make dense data readable.

Native app, not a wrapper

Built for the platform, not around a web view.

The Strkr mobile apps are native iOS and Android apps built with platform-native UI frameworks. The scrolling is native, the gestures are native, the typography follows platform conventions. The experience is a native app, not a web view wrapped in an app shell.

Offline reads

The last sync lives on the device.

The app caches the dashboards the user accesses so a flight-mode view still shows the last-synced data. The staleness of the cache is visibly displayed (e.g. "Data as of 3 hours ago"). When connectivity returns, the sync happens in the background and the data refreshes.

Push notifications

The anomaly alert on the lock screen.

When Strkr AI detects an anomaly or a threshold crossing on a dashboard the user cares about, a push notification arrives on the phone with the specific signal. "Pipeline pacing dropped below 80 percent target." Tapping the notification opens the specific dashboard tile.

Biometric authentication

Face ID, Touch ID, Android fingerprint.

The mobile app supports biometric authentication: Face ID and Touch ID on iOS, fingerprint and face unlock on Android. Opens in two seconds without typing a password. The security posture respects the device's own biometric layer rather than inventing a parallel one.

Deep links

From Slack to the specific tile.

A link from a Slack message, an email, or a scheduled digest can deep-link into a specific dashboard or tile in the mobile app. The executive reading a weekly digest on the phone taps a link and lands on the dashboard with the right filter applied.

Pinned dashboards

The user picks their home.

The user pins the dashboards they read most to the mobile app home screen. The app opens on the pinned view. The executive who always starts with the pipeline-pacing dashboard sees it on the first screen without a navigation step.

Drill-in gestures

Tap, long-press, swipe.

Dashboard interactions use native gesture patterns. Tap a tile to expand. Long-press for context menu. Swipe for history. Pull-to-refresh. The patterns match mobile user expectations rather than forcing a desktop interaction into a phone context.

Battery and data

The app is cheap to run.

The app minimizes battery and cellular data usage: deltas on sync rather than full refreshes, batched background updates, respect for low-power mode. The executive running the app for a day of meetings does not see a noticeable battery drain.

App store presence

In the official stores, reviewed and signed.

The Strkr app ships through the Apple App Store and Google Play Store with the review process completed. IT teams can distribute through MDM (Jamf, Intune, Workspace ONE). The security posture is auditable through the store review and the signing certificates.

The desktop and tablet experience

Where the operator builds and the manager analyzes.

The desktop and tablet surfaces are where the operator spends the working day: building dashboards, running custom reports, drilling into specific records, running the weekly operating rhythm. The experience is denser than mobile, more interactive, and supportive of the composition work. The responsive web app is the primary surface, with a dedicated desktop app available for teams that prefer a specific window outside the browser.

Dense layout

More tiles, more detail, more drill-in.

The desktop layout shows more tiles per screen, denser charts, and richer interactivity. The operator sees the full dashboard in one view and drills in on the specific tile that needs attention. The density matches the input device: mouse and keyboard support richer interaction than touch.

Interactive filters

Click a bar, filter the dashboard.

Interactive dashboards let the user click a bar in a chart or a row in a table to filter the rest of the dashboard. Clicking "Enterprise segment, $1.2M" on a pipeline bar scopes the whole dashboard to the Enterprise segment. The interaction pattern turns a dashboard into a navigable analysis surface.

Multi-window

Open two dashboards side by side.

The web app supports multiple tabs with separate filter states. An operator can open the sales ops dashboard in one tab and the marketing ops dashboard in another for comparison. The dedicated desktop app supports multi-window layouts for teams who prefer side-by-side arrangements.

Keyboard shortcuts

Power users move faster with keys.

The web app supports keyboard shortcuts for the common actions: open dashboard, apply filter, drill-in, export, share. Power users (ops leads, sales managers) learn the shortcuts and move through dashboards faster than mouse-only users.

Builder mode

Edit dashboards in the same place.

The admin edits dashboards in the same web app the operator views them in. No separate authoring tool. The transition between view mode and edit mode is a toggle. Admins see what the viewer sees without a context switch.

Live collaboration

Two editors on one dashboard.

The dashboard editor supports multiple simultaneous editors with real-time cursor visibility and conflict-free editing. Two admins working on the same dashboard do not step on each other's changes. The pattern matches the collaboration experience of a modern document tool.

Shared cursors

See where the other admin is.

When two users are viewing the same dashboard, their cursors appear briefly on each other's screens with the user's name. The pattern is useful for the Zoom pair-session where two people are reviewing the same dashboard together.

URL state

The dashboard URL carries the filter.

Filter state encodes into the URL so sharing a specific view is a copy-paste. "Share the dashboard scoped to Enterprise segment, last 30 days" is a URL, not a screenshot. The pattern reduces the common "my dashboard looks different from yours" confusion.

Export shortcuts

One click to PDF, CSV, or slide image.

An export button on every dashboard produces a PDF snapshot, a CSV of the underlying data, or a PNG suitable for pasting into a slide deck. The exports carry the current filter state. The pattern supports the "I need this in a slide tomorrow morning" moment without a separate design pass.

The conference-room and large-screen experience

The dashboard that reads from the back of the room.

A weekly operating meeting often happens around a shared screen with the team looking at a dashboard. The specific requirements for that screen are different from desktop: larger typography, higher contrast, no personal filter changes that disturb the shared view, and auto-refresh so a long meeting does not drift on stale data. The conference-room mode is a specific rendering optimized for the shared-screen use case. Strkr's dashboard app detects the resolution and offers the mode as a one-click toggle.

Large-screen rendering

Typography sized for the back row.

The conference-room mode scales typography and chart elements for readability from ten feet or more. Numbers that are small on a laptop are the dominant visual element on the shared screen. The design is deliberate about what matters at that distance.

Auto-refresh

A long meeting does not go stale.

Dashboards in conference-room mode auto-refresh on a configurable cadence (every 30 seconds, every minute, every five minutes). An hour-long leadership meeting ends with the same freshness it started with.

Presenter mode

The presenter runs, the room watches.

A presenter mode designates one user as the active presenter. The presenter navigates and filters; the shared screen reflects the presenter's view. Other viewers can watch without their own personal clicks affecting the shared surface.

Focus mode

One tile fills the screen for discussion.

A focus toggle on any tile expands it to fill the screen. The team drills in on a specific pipeline view, discusses, and returns to the full dashboard. The focus mode supports the natural rhythm of a meeting that zooms in and out of specific numbers.

Chromecast and AirPlay

Cast from a laptop to the room.

The dashboard supports Chromecast on Chrome and AirPlay on Safari for projecting to a conference-room screen. No HDMI dongle, no laptop display mirroring, no separate screen-share app. The dashboard runs natively on the room screen.

Shared annotations

Mark up the dashboard during the meeting.

In meeting mode, viewers can annotate the dashboard with highlights, arrows, and short notes that appear temporarily on the shared screen. The annotations do not persist to the dashboard definition but are useful for the real-time discussion.

Recording

The dashboard state at meeting time, saved.

The presenter can save a snapshot of the dashboard's state at the start of the meeting for later reference. "Here is where we were when the forecast call happened." The snapshot is a point-in-time record that supports post-meeting review.

Narrative overlay

The Strkr AI summary alongside the chart.

The narrative tile from Strkr AI shows prominently on the shared screen so the meeting opens on the plain-English summary before the detailed charts. The opening narrative frames the conversation efficiently.

Automated weekly setup

The dashboard is already up when the meeting starts.

A scheduled flow can pull up the weekly operating dashboard on the conference room screen at the meeting start time via a smart display integration. The team walks in and the dashboard is already live, scoped to the week, and refreshing. No one spends five minutes getting the screen configured.

The security and governance posture across all surfaces

Mobile, desktop, and shared screens respect the same rules.

A multi-surface dashboard experience creates specific security requirements. The mobile app must authenticate reliably without creating a workaround to the password policy. The desktop web app must respect the same session controls as the mobile. The conference-room mode must not accidentally display confidential data to a visitor in the room. Strkr's dashboard apps implement the security posture consistently across every surface, with specific controls for the shared-screen case.

SSO everywhere

One identity, every surface.

SAML and OIDC SSO work on mobile, desktop, and conference-room modes. The user authenticates once through the corporate IdP and the session carries across every Strkr surface. No separate password for the mobile app.

Session management

The admin controls session length.

Session timeout is a tenant-level policy applied to every surface. A conservative session policy (30-minute idle timeout) applies to mobile and desktop equally. The admin manages the policy once; the apps enforce it uniformly.

Biometric gates

Device-level biometric unlock.

Mobile apps gate behind the device's biometric unlock in addition to the SSO session. A phone that is unlocked but has not been biometrically verified to open the app does not show dashboard data. The pattern protects against a phone picked up by the wrong person.

MDM compatibility

Jamf, Intune, Workspace ONE support.

The mobile app is compatible with the common Mobile Device Management (MDM) platforms. IT can push the app to managed devices, enforce enrollment, revoke on departure, and apply policy constraints (no screenshot, no copy-paste outside the app).

Visitor mode

A conference room screen with a visitor-safe layout.

The conference-room mode supports a visitor-safe layout that hides fields marked confidential at the tenant level. A product review meeting with an external attendee can show the deal pipeline shape without showing the specific competitor-sensitive deal names.

Screen record detection

A warning when the shared screen is recorded.

When the dashboard detects that a screen recording is active (via platform APIs where available), it displays a prominent indicator. The pattern reminds everyone in the room that the view is being captured and may need to be scoped to a safer dataset.

Audit log of access

Every dashboard access logged.

The audit log records every dashboard access with the user, the timestamp, the IP range, the device type, and the dashboard identifier. A compliance review traces who read which data from which device. The audit covers mobile, desktop, and conference-room access uniformly.

Share controls

Who can view, who can share further.

A dashboard shared with a user can be configured to disallow further sharing. The pattern prevents a dashboard from leaking across role boundaries when a well-intentioned user forwards a link. The share chain is auditable and controllable.

Revocation

A departing user loses access instantly.

When a user leaves the tenant (role revoked, SSO group removed), all dashboard access revokes immediately across every surface. The mobile app on their phone shows a re-authentication prompt and refuses to render dashboards until a current session reauthenticates.

Dashboard apps that work on every surface a business reader uses.

Native iOS and Android apps, responsive web, dedicated desktop app, and conference-room mode. Same data, same permissions, same refresh cadence. Strkr AI drafts narratives and surfaces anomalies across every surface. One platform, every device.

Start free See pricing
Common questions

What buyers ask about this feature.

Does Strkr have native mobile apps, or just a mobile web view?

Native apps for both iOS and Android, available through the Apple App Store and Google Play Store. The apps are built with platform-native UI frameworks and provide the experience executives expect from a native mobile app: offline reads from the last sync, push notifications on anomaly alerts, biometric authentication (Face ID, Touch ID, fingerprint), deep links from Slack or email to specific dashboards, and native gesture patterns (tap, long-press, swipe, pull-to-refresh). The apps are not web view wrappers. Everything the dashboard renders on the web renders on the native apps with layouts tuned for the smaller screen, and the data respects the same permission model across every surface. IT teams can distribute through MDM platforms (Jamf, Intune, Workspace ONE) with enforcement of enrollment, revocation on departure, and policy constraints like screenshot prevention.

How does the dashboard experience adapt across phone, tablet, desktop, and conference-room screens?

The dashboard definition is one artifact; the rendering adapts to the surface. On a phone (320 to 420 pixels wide), tiles stack vertically with each tile sized for finger-tap interaction and typography sized for arm-length reading. On a tablet (768 to 1024 pixels), a two-column grid with condensed controls. On a desktop (1024 to 2560 pixels), a dense multi-column grid with full interactivity, keyboard shortcuts, and multi-window support. On a conference-room screen (TV resolution), a large-typography mode with high-contrast colors and auto-refresh for long meetings, plus a presenter mode that designates one user as the active controller. The admin designs once; the dashboard works everywhere. The same filter state, the same permission scoping, and the same Strkr AI narrative integrations apply uniformly.

Can we view dashboards offline when traveling or without connectivity?

Yes, on the native mobile apps. The app caches the dashboards the user accesses locally, so a flight-mode view still shows the last-synced data. The staleness of the cache is visibly displayed on the dashboard ("Data as of 3 hours ago") so the user is never confused about whether they are seeing current information. When connectivity returns, the sync happens in the background and the data refreshes. For heavy dashboards with lots of tiles, the sync is incremental: only the tiles the user is currently viewing refresh first, with the rest syncing in the background. The offline mode is one of the specific requirements that pushed us toward native apps rather than a web view, because the browser-based offline experience is less reliable across platforms than the native app can offer.

How does conference-room mode work for team meetings?

Conference-room mode is a dedicated rendering optimized for the shared-screen use case in a meeting room. Typography and chart elements scale for readability from ten feet or more. Auto-refresh runs on a configurable cadence so a long meeting does not go stale. A presenter mode designates one user as the active controller; the presenter navigates and filters, and the shared screen reflects the presenter's view without other viewers' clicks disturbing the shared surface. A focus toggle expands any tile to fill the screen for discussion of a specific number. Chromecast on Chrome and AirPlay on Safari project to the room screen without an HDMI dongle. For meetings with external attendees, a visitor-safe layout hides fields marked confidential at the tenant level. A scheduled flow can even bring up the weekly operating dashboard on the conference-room screen at the meeting start time via smart display integration, so the team walks in and the dashboard is already live.

How do security and governance work across all these surfaces?

The security posture is consistent across every surface because the model enforces at the query layer rather than the client layer. Authentication uses SSO (SAML and OIDC) with the user's corporate IdP, and the session carries across mobile, desktop, and conference-room modes. Session timeout, password policy, and IP allowlist are tenant-level settings applied uniformly. Mobile apps gate behind device biometric unlock in addition to the SSO session. MDM compatibility supports Jamf, Intune, and Workspace ONE for enforcement, revocation, and policy constraints. The audit log records every dashboard access with user, timestamp, IP range, device type, and dashboard identifier, covering mobile, desktop, and conference-room access uniformly. When a user leaves the tenant, access revokes immediately across every surface. The combination keeps the multi-surface experience from becoming a multi-vulnerability experience.

Can we build custom dashboards or are we limited to the shipped templates?

The templates are starting points, not limits. The dashboard builder supports any custom dashboard the function needs, with the full tile library (metric cards, charts, tables, text blocks, embeds), dashboard-level and tile-level filters, interactive drill-ins, comparison periods, and tenant-level branding. The builder is self-serve: an admin picks tiles from the saved report library, arranges them on a responsive grid, configures shared filters, and publishes. The composition language is the same whether the dashboard has four tiles or forty. For large-screen or mobile layouts, the responsive grid handles the adaptation automatically, so the admin designs once and the dashboard works across every surface. Permissions apply at the dashboard level and the tile level, supporting mixed-audience dashboards where some tiles are visible only to managers without separate per-role versions.

Related features

Pair this with...

Dashboard Software Business Dashboard Software KPI Dashboard CRM Dashboard Mobile CRM Sales Dashboard

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing