Our organization rolled out approval workflows using Power Automate with Power Apps interfaces for both mobile and desktop users. After three months of production use, we’re seeing interesting patterns in how users interact with the system differently based on their device.
Mobile users (about 60% of our approvers) complete tasks faster on average but report more UI lag and inconsistent form rendering, especially with complex approval forms that have conditional visibility rules. Desktop users take longer per approval but handle batch operations more efficiently.
We’re considering optimizing our workflow strategy to better accommodate both experiences. Has anyone implemented hybrid approaches where the workflow adapts based on the device type? Curious about your experiences with mobile form optimization versus maintaining feature parity across platforms. What trade-offs have you made for approval speed versus user satisfaction?
For device switching, implement progressive disclosure patterns. Save form state continuously so users can seamlessly transition between devices. We use Power Automate’s “Wait for approval” action with custom response options that include “Review Later” - this saves the current state and sends a new notification. The workflow tracks which fields were already reviewed on mobile and only shows remaining fields on desktop. Works beautifully for your executive use case.
Consider separating your approval workflows by complexity level. Simple approvals (budget under $5K, routine requests) get mobile-first forms with swipe gestures for approve/reject. Complex approvals (contracts, capital expenditure) route to desktop-mandatory forms with rich document preview and comparison tools. We saw 70% of approvals could be mobile-optimized this way, dramatically improving overall throughput while maintaining quality on complex decisions.
The device detection approach sounds promising. How do you handle cases where users switch devices mid-approval? We have executives who start reviewing on mobile during commute then finish on desktop in office.
After implementing hybrid workflow strategies across multiple organizations, here’s what works best for balancing mobile and desktop experiences:
Mobile Form Optimization:
The UI lag you’re experiencing stems from Power Apps mobile client rendering complex forms. Key optimizations:
- Reduce form controls to maximum 15 visible fields on mobile layouts
- Replace dropdown controls with radio buttons for 5 or fewer options (better touch targets)
- Disable auto-save on mobile and implement explicit Save buttons to reduce background processing
- Use tabbed interfaces instead of scrolling forms - each tab loads independently reducing initial render time
- Implement lazy loading for attachments and related records - only fetch when user explicitly requests
- Cache reference data locally in collections rather than calling Dataverse repeatedly
For conditional visibility, replace complex rules with simpler show/hide based on single field values. Move multi-field validation logic to Power Automate pre-processing.
Desktop Browser Compatibility:
Cross-browser consistency requires deliberate design choices:
- Test forms in Chrome, Edge, Firefox, and Safari - each handles canvas apps differently
- Avoid browser-specific CSS in custom components
- Use Power Apps built-in controls rather than custom HTML controls when possible
- Implement feature detection rather than browser detection for progressive enhancement
- For file uploads, provide clear browser compatibility warnings
- Desktop forms can leverage multiple columns, hover states, and keyboard shortcuts that mobile can’t
Hybrid Workflow Strategies:
Device-adaptive workflows deliver the best results:
- Implement device detection at workflow initiation using Power Automate expressions to check user agent
- Create two form variants: Mobile-optimized (simplified) and Desktop-full (comprehensive)
- Route based on approval complexity AND user preference:
- Simple approvals: Default to mobile, allow desktop override
- Complex approvals: Require desktop, provide mobile preview-only mode
- Enable seamless device switching with state persistence:
- Save partial approval data to Dataverse after each section completion
- Send device-appropriate notification links (deep links for mobile app, web URLs for desktop)
- Display progress indicator showing what’s been reviewed
- Batch operations remain desktop-exclusive but provide mobile notifications when batches complete
Our most successful implementation used approval tiers:
- Tier 1 (70% of approvals): Mobile-first, 3-field forms, swipe gestures, <30 second completion target
- Tier 2 (25% of approvals): Hybrid-capable, progressive disclosure, 2-5 minute completion
- Tier 3 (5% of approvals): Desktop-required, full document review, multi-approver collaboration
The trade-off isn’t approval speed versus satisfaction - it’s recognizing that different approval types need different experiences. Mobile optimization shouldn’t mean feature reduction; it means intelligent prioritization of information and interactions. Desktop shouldn’t mean complexity; it means comprehensive context when needed.
Metrics after implementation: 65% faster mobile completions, 35% higher user satisfaction, 90% reduction in “abandoned” approvals, and executives particularly appreciated device-switching capability for travel scenarios.
We faced similar challenges. The key insight was that mobile and desktop users have fundamentally different workflows. Mobile users want quick yes/no decisions with minimal context, while desktop users prefer comprehensive information and bulk actions. We created simplified mobile forms with only critical fields visible by default, with a “View Full Details” option that opens in desktop mode. This reduced mobile completion time by 40% and improved satisfaction scores significantly.