Tauri 2 capability files: limits of build-time permission scoping across desktop and mobile targets
Goal I am designing the permission layout for a Tauri 2.x app that shares one codebase across desktop (Windows, macOS, Linux) and mobile (iOS, Android). The goal is a single, maintainable capability configuration that grants each plugin only what it needs, without over-privileging any target. Constraints and uncertainty From the documentation, capabilities a