feat: add documentation for 2.11 features#3786
Conversation
mobile multi-window: tauri-apps/tauri#14484 file association: tauri-apps/tauri#14486
✅ Deploy Preview for tauri-v2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
only commenting this so i don't forget it over night. do we also want a few sentences on multi-window support on phones (so without side-by-side)? Not sure if that's even a realistic use-case but it's probably a question that will come up. |
good catch, pushed |
|
|
||
| On **iOS**, multi-window uses the [UIScene](https://developer.apple.com/documentation/uikit/uiscene) API, which allows iPad users to open multiple instances of your app in separate windows. | ||
|
|
||
| On **phones**, the system usually does not lay out two windows side by side. On **Android**, creating another window still launches a separate activity, but on handset-sized displays it is typically **pushed onto the activity back stack**—so **Back** returns to the previous activity instead of closing a split. On **iOS** (especially iPhone), opening or creating another window often **replaces the current UI** with the new scene’s content rather than keeping both visible at once; true concurrent windows remain an **iPad** (and Stage Manager) experience. |
There was a problem hiding this comment.
I'm struggling to reconcile this comment with the app.supportsMultipleWindows flag. Since this flag is the source of truth as to whether multi-window is supported, should we simply return false for phones?
Applications will likely use this flag to detect whether to enable the feature for their users. If it returns true on phones but isn't really supported this somewhat defeats its purpose.
There was a problem hiding this comment.
app.supportsMultipleWindows returns false on iPhones (though for Android phones it returns true if API >= 32; in that case, the system will just push the new activity to the stack, that's just the fallback behavior defined by Android)
the docs just state what happens if you try to create another window even though supportsMultipleWindows return false
There was a problem hiding this comment.
Thanks @lucasfernog — that helps. I think there's still a gap worth addressing in the doc itself, though.
The concern is that app.supportsMultipleWindows returns true on Android phones (API ≥ 32) even though the platform's behaviour is push-to-back-stack rather than split. Apps that gate "Open in new window" UI on this flag — which is how the doc presents it as a runtime check — will end up offering a feature that doesn't work the way users expect on phones.
There was a problem hiding this comment.
unfortunately there's no check AFAIK to properly determine whether the platform supports it or not - maybe we should just check if it is a tablet or not?
github-project-automation
Bot
moved this from 🪵 Backlog
to 🏗️ In progress
in Documentation
3 participants
mobile multi-window: tauri-apps/tauri#14484
file association: tauri-apps/tauri#14486