PWA Feasibility Study: Replacing Native Mobile & Desktop Apps¶

Project: Forma3D.Connect
Version: 1.0
Date: January 19, 2026
Status: Research / Proposal

Executive Summary¶

This document evaluates Progressive Web Apps (PWA) as an alternative to the currently planned Tauri (desktop) and Capacitor (mobile) native shell applications. Based on research conducted in January 2026, PWA technology is highly relevant and well-suited for Forma3D.Connect's use case, potentially eliminating the need for separate mobile and desktop applications.

Recommendation¶

Adopt PWA as the primary cross-platform strategy, deprecating the planned Tauri desktop and Capacitor mobile apps from the roadmap. The Forma3D.Connect admin dashboard is an ideal PWA candidate: a SaaS-style application focused on data visualization, real-time updates, and notifications rather than heavy device integration.

Current Architecture Plan¶

As documented in C4_Container.puml:

Container(desktop, "Desktop App", "Tauri, Rust", "Native desktop shell wrapping the web application (future)")
Container(mobile, "Mobile App", "Capacitor", "Mobile shell for on-the-go monitoring (future)")

Both planned apps are essentially WebView wrappers around the existing React web application. This makes them prime candidates for PWA replacement.

PWA Relevance in 2026¶

Market Position¶

PWA technology remains highly relevant and growing in 2026:

• Market CAGR of 30-32% projected through 2034
• Strong enterprise adoption for admin dashboards, internal tools, and SaaS applications
• Particularly strong in emerging markets where network/device constraints exist

Key Capabilities (2026)¶

iOS/Safari PWA Support (Critical Analysis)¶

Apple's PWA support has significantly improved but retains some limitations:

What Works (iOS 16.4+)¶

• ✅ Web Push notifications for Home Screen installed PWAs
• ✅ Badging API for notification counts
• ✅ Declarative Web Push (iOS 18.4+) - improved reliability
• ✅ Screen Wake Lock
• ✅ Standalone display mode

Limitations¶

Assessment¶

For an admin dashboard like Forma3D.Connect, iOS limitations are acceptable. The primary users (Forma3D operators) will: - Install the PWA once to their Home Screen - Use the app regularly (not affected by inactivity suspensions) - Receive push notifications for order/print job updates

PWA vs Tauri Comparison (Desktop)¶

Tauri Advantages Not Needed¶

• Rich file system access: Forma3D.Connect doesn't require local file manipulation
• System tray: Dashboard is used actively, not as background utility
• Native performance: Admin dashboard doesn't have performance-critical requirements
• Rust backend processing: All heavy processing is server-side (NestJS API)

PWA Advantages Critical for Forma3D¶

• Zero maintenance overhead: No separate build pipelines, code signing, or distribution
• Instant updates: Deploy once, all clients updated immediately
• Lower complexity: Single codebase, single deployment target
• Browser familiarity: Operators can use existing browser or install as PWA

PWA vs Capacitor Comparison (Mobile)¶

Capacitor Advantages Not Needed¶

• Deep device integration: Dashboard doesn't need NFC, Bluetooth, health sensors
• App Store discovery: B2B tool for known operators, not consumer app
• Native UI components: React + Tailwind provides excellent mobile UX

PWA Advantages Critical for Mobile¶

• No app store friction: Operators can start using immediately
• Cross-platform consistency: Same experience on iOS and Android
• Easier onboarding: Share URL, install from browser

Forma3D.Connect Feature Compatibility¶

Evaluating current and planned features against PWA capabilities:

Only Limitation¶

Printing shipping labels on mobile: This is inherently challenging on any mobile platform. The standard workflow (print to network printer) works via browser print dialog. For Bluetooth thermal printers, native apps would have advantages, but this is not a primary use case for mobile operators.

Implementation Plan¶

Phase 1: PWA Foundation (Minimal Effort)¶

The current React/Vite web app requires only minor additions:

1. Web App Manifest (manifest.json)

   {
     "name": "Forma3D.Connect",
     "short_name": "Forma3D",
     "start_url": "/",
     "display": "standalone",
     "background_color": "#ffffff",
     "theme_color": "#0066cc",
     "icons": [...]
   }
   

2. Service Worker (via Vite PWA plugin)

3. vite-plugin-pwa handles generation
4. Cache static assets, enable offline access

5. Precache critical routes

6. HTTPS (Already implemented)

7. Required for PWA features

Phase 2: Push Notifications¶

1. Implement Web Push API in frontend
2. Add VAPID key configuration
3. Backend push notification service (integrate with existing email notifications)
4. User permission flow in settings

Phase 3: Enhanced Offline Support¶

1. IndexedDB for offline data storage
2. Background sync for queued actions
3. Optimistic UI updates

Cost-Benefit Analysis¶

Development Cost Savings¶

Estimated savings: 80-150 hours initial + ongoing maintenance reduction

Complexity Reduction¶

• Remove Tauri app from monorepo (apps/desktop)
• Remove Capacitor app from monorepo (apps/mobile)
• Single deployment target (web only)
• No native build environments required (Xcode, Android Studio, Rust toolchain)

Risk Reduction¶

• No platform-specific bugs to debug
• No webview inconsistencies between platforms
• No app store rejection risks
• No signing certificate management

Risks and Mitigations¶

Decision Framework¶

Adopt PWA If:¶

• ✅ Application is primarily data-driven (dashboard, forms, lists)
• ✅ Real-time updates needed but not gaming-level performance
• ✅ Push notifications required
• ✅ Cross-platform reach is important
• ✅ Rapid iteration and updates desired
• ✅ Development resources are limited

All criteria apply to Forma3D.Connect

Keep Native If:¶

• ❌ Heavy graphics/3D rendering required
• ❌ Deep device integration (Bluetooth LE, NFC, sensors)
• ❌ App store presence essential for marketing
• ❌ Offline-first with complex sync requirements
• ❌ Background processing requirements

None of these apply to Forma3D.Connect

Conclusion¶

PWA technology in 2026 is mature, well-supported, and ideal for Forma3D.Connect. The planned Tauri and Capacitor apps would add significant development and maintenance overhead while providing no meaningful advantages for an admin dashboard application.

Recommended Actions¶

1. Add PWA support to the existing web application (Phase 1)
2. Implement push notifications for print job and order status updates (Phase 2)
3. Remove apps/desktop and apps/mobile from the project roadmap
4. Update C4 Container diagram to reflect PWA-only architecture
5. Create ADR documenting this architectural decision

References¶

• WebKit Blog: Web Push for Web Apps on iOS
• WebKit Blog: Declarative Web Push
• web.dev: PWA OS Integration
• HTTP Archive: PWA Almanac 2025
• Vite PWA Plugin Documentation

Appendix: Updated C4 Container Diagram (Proposed)¶