Vercel
The frontend cloud. Creators of Next.js.
5.0•951 reviews•15K followers
The frontend cloud. Creators of Next.js.
5.0•951 reviews•15K followers
Vercel provides the developer tools and cloud infrastructure to build, scale, and secure a faster, more personalized web.
This is the 30th launch from Vercel. View more
Native SDK
Launching today
Native SDK is the complete toolkit for building beautiful native desktop applications: declarative markup, a predictable message-based state model, a modern component library, and its own native renderer — no browser, no WebView, no compromise.
Free
Launch Team
Google Cloud Platform
Cloudflare Pages
Netlify
Railway
Render
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?
How difficult is migration from existing desktop projects and could step by step examples make adoption much smoother?
i 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?
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!
I am excited about this - having an alternative to the standard Electron/Tauri and having explored Flutter and React Native, this sounds very compelling and the sample apps - especially the note-taker - look quite smooth. I am wondering if the fact that our platform is a monorepo with React/Next/Tailwind/TypeScript will be a multiplier in being able to use this? We've built heavily on Vercel SDKs (we use the AI Gateway, the AI SDK, Nextjs) and we're big V0 users as well! Love this, @Vercel!
QWERTYS by Smart Keys
I thought this kind of approach was already outdated. Does it still make sense to have this type of hybrid platform in the world of AI assistants, where building natively is no longer a big challenge? And you no longer need to rely on third parties to use recent native APIs or to avoid surprises when your packages and app break.