Developer Builds Email Client Entirely With AI

A developer created Velo, a full-featured desktop email client, using AI to write 100% of the code based on specifications and architecture. The open-source application was built over three months with Tauri, React, and Rust. The creator noted that community reactions focused more on the AI-driven process than the application's features, indicating potential skepticism toward AI-generated software.

- The choice of Tauri for Velo's architecture results in significant performance advantages over Electron-based apps, with Tauri apps often having installers under 10MB and idling at 30-50MB of memory, compared to Electron's 80-150MB installers and 150-300MB memory usage. This is achieved by leveraging the host operating system's native WebView, whereas Electron bundles the entire Chromium browser. - While 82% of developers report using AI coding tools weekly, a growing distrust is evident. A 2025 survey found that 46% of developers distrust the accuracy of AI-generated code, a sharp increase from 31% the previous year. Many developers find that debugging AI-generated code can take longer than writing it from scratch. - The creator of Velo noted that community feedback often focused on the AI-driven development process rather than the app's features, with some questioning the validity of "building" something with AI. This reflects a broader sentiment in the developer community where there's skepticism and a sense of "identity threat" from AI-assisted development, even as adoption grows. - For engineers considering a move to management, a primary challenge is shifting focus from individual technical achievements to enabling the team's success. This transition involves delegating technical tasks, even enjoyable ones, and accepting that your role is to remove obstacles and provide support rather than writing code yourself. - Maintaining technical credibility as a manager doesn't necessarily mean continuing to code. Instead, it involves staying current with technologies to guide architectural decisions, understand technical trade-offs, and effectively communicate with both the engineering team and other stakeholders. This can be achieved by reviewing code, participating in design discussions, and encouraging the team to experiment with new technologies. - The use of WebAssembly (Wasm) in frontend development allows for running computationally intensive tasks at near-native speeds in the browser. While it doesn't directly access the DOM, Wasm complements JavaScript by handling heavy operations like image and video processing or complex data visualizations, communicating with JavaScript to update the UI. - The React Compiler, now in release candidate, automates performance optimization by automatically memoizing components and hooks, aiming to eliminate the manual work of `useMemo` and `useCallback`. It analyzes code to identify reactive values—those that can change between renders—and caches them to prevent unnecessary re-renders. - Signals, as seen in frameworks like Solid and now Angular, offer a different reactivity model that avoids the overhead of a virtual DOM by updating the DOM directly when state changes. This granular approach can be more efficient than React's component-based re-rendering, and there is ongoing work to standardize a signals model for JavaScript, which could influence future versions of React.

Get your own daily briefing

Scout delivers personalized news, insights, and conversations tailored to your role and industry.

Download on the App Store

Shared from Scout - Be the smartest in the room.