I’ve been experimenting with Capsule and really like the concept.
I confirmed that external REST APIs work from Capsule via fetch(). I’d like to use Capsule as a lightweight/offline client for Claris FileMaker Server, but FileMaker Data API does not support CORS or OPTIONS preflight requests, so a direct request currently fails with TypeError: Load failed.
Would you consider providing a native HTTP API through the Capsule/Tauri host, e.g. capsule.http.request()?
That would allow:
Capsule → Native HTTP → FileMaker Data API
without requiring a separate proxy server, while still allowing Capsule to control network access through its permission system.
I think this would be useful beyond FileMaker too — for internal/legacy REST APIs, NAS devices, IoT devices, and other local-network APIs without browser-compatible CORS support.
The idea of a self-contained Capsule app that works offline, stores data locally, and syncs directly with an existing business system when online is especially interesting to me.
I confirmed that external REST APIs work from Capsule via fetch(). I’d like to use Capsule as a lightweight/offline client for Claris FileMaker Server, but FileMaker Data API does not support CORS or OPTIONS preflight requests, so a direct request currently fails with TypeError: Load failed.
Would you consider providing a native HTTP API through the Capsule/Tauri host, e.g. capsule.http.request()?
That would allow:
Capsule → Native HTTP → FileMaker Data API
without requiring a separate proxy server, while still allowing Capsule to control network access through its permission system.
I think this would be useful beyond FileMaker too — for internal/legacy REST APIs, NAS devices, IoT devices, and other local-network APIs without browser-compatible CORS support.
The idea of a self-contained Capsule app that works offline, stores data locally, and syncs directly with an existing business system when online is especially interesting to me.