Get the weekly radar
One short email with the freshest products, every week.
Grounded in available product and source data
Toolkit for building native desktop apps Discussion | Link
These 7 comments were collected from the discovery source. ProductVisit does not host replies in Release A.
How difficult is migration from existing desktop projects and could step by step examples make adoption much smoother?
1 source upvotesi appreciate the message based state model because predictable updates can reduce debugging time. have you tested performance with very large applications and would publishing benchmark results help developers understand where this toolkit performs best?
The "no browser, no WebView, no compromise" positioning is very clear. Desktop apps are in a weird place where a lot of tools feel like websites wrapped in a window, which is fine until performance, memory, offline behavior, or native feel actually matter. A toolkit that gives declarative UI and a predictable state model while still rendering natively sounds like a strong direction. Curious how close Native SDK gets to platform-native behavior out of the box. Does it handle things like keyboard shortcuts, menus, window controls, accessibility, and OS-specific patterns automatically, or do developers need to wire a lot of that themselves?
I like the focus on native applications instead of browser based solutions. Could adding more sample projects for different industries help developers discover practical ways to use the toolkit?
A built-in cost dashboard showing real-time bandwidth and function invocation spend per project would be huge. Right now I have to dig through usage logs and try to estimate monthly bills myself, which makes budgeting for client work way harder than it needs to be.
I've been driving native desktop apps with automation and half my breakage comes from each OS handling windows and menus differently. Does Native SDK give you one API across Mac and Windows, or are you still writing platform-specific code under the hood for the fiddly stuff like tray icons and file dialogs? That gap is usually where cross-platform toolkits quietly leak.
Usually going native like that means giving up easy stuff like embedding web content or styling with CSS. Is the tradeoff worth it in practice, and what's it actually like to build with something closer to React, or something new to learn? Excited to try it out!