You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tracking Issue: Adapt systems to support native platform APIs #2540
This deals with future work plans on the desktop app. See this issue's parent tracking issue.
I'm not sure what's the concern with it here, I'm asking about more details on what are those plans referring to. Stuff like window title bar seems like something that could be part of ongoing contributions to desktop app implementation right now, so I was asking about what is it referring to since I was looking forward to contributing.
Gotcha, it sounded like your question was asking about its role within the web ecosystem, when in fact this deals with native APIs not web APIs. This issue is blocked since it comes after the current blocker on the desktop app, which is the platform-specific compositor challenges for combining the webview and native render. If you're interested in getting involved with native development for the desktop app initiative, please see #2541 and #2648 and take a look over in the #desktop-app channel of our Discord where the recent discussion has taken place which can fill in those details. Thanks!
changed the title [-]Adapt systems to support native platform APIs[/-][+]Tracking Issue: Adapt systems to support native platform APIs[/+]on Sep 3, 2025
Activity
banocean commentedon May 25, 2025
I think this could be quite big ui/ux concern when we would lean too much on os implementation and use for example native menu bar
Can't this be done via browser apis? Are there any limitations of the Clipboard API making this not possible?
Keavon commentedon May 25, 2025
This deals with future work plans on the desktop app. See this issue's parent tracking issue.
banocean commentedon May 25, 2025
I'm not sure what's the concern with it here, I'm asking about more details on what are those plans referring to. Stuff like window title bar seems like something that could be part of ongoing contributions to desktop app implementation right now, so I was asking about what is it referring to since I was looking forward to contributing.
Keavon commentedon May 25, 2025
Gotcha, it sounded like your question was asking about its role within the web ecosystem, when in fact this deals with native APIs not web APIs. This issue is blocked since it comes after the current blocker on the desktop app, which is the platform-specific compositor challenges for combining the webview and native render. If you're interested in getting involved with native development for the desktop app initiative, please see #2541 and #2648 and take a look over in the #desktop-app channel of our Discord where the recent discussion has taken place which can fill in those details. Thanks!
[-]Customize native window and utilization of native APIs[/-][+]Customize native window and utilize native APIs[/+]24 remaining items
[-]Adapt systems to support native platform APIs[/-][+]Tracking Issue: Adapt systems to support native platform APIs[/+]Keavon commentedon Dec 22, 2025
All remaining issues are now tracked in #3507 and #3508.