[{"data":1,"prerenderedAt":738},["ShallowReactive",2],{"blog-posts-en-US":3},[4,259,480],{"id":5,"title":6,"body":7,"description":247,"extension":248,"meta":249,"navigation":254,"path":255,"seo":256,"stem":257,"__hash__":258},"blog\u002Fblog\u002Fen-US\u002Fproduct-roadmap.md","AuraShell Product Roadmap: From Desktop Engine to Creative Ecosystem",{"type":8,"value":9,"toc":238},"minimark",[10,14,19,27,30,52,58,61,65,72,75,100,107,110,114,117,120,144,151,154,158,165,168,188,195,199,209,213,216,235],[11,12,13],"p",{},"In our previous posts, we discussed \"why we're building this\" and \"why we chose Tauri.\" Today, let's talk about where we're headed next. AuraShell is not a one-time software delivery; it's a gradually evolving desktop engine. Below is our clear three-step roadmap and a broader ecosystem vision for the future.",[15,16,18],"h2",{"id":17},"phase-1-solidify-the-core-icon-organization-dynamicstatic-wallpaper-built-in-widgets","Phase 1: Solidify the Core — Icon Organization + Dynamic\u002FStatic Wallpaper + Built-in Widgets",[11,20,21,22,26],{},"At the current stage, our focus is to deliver a ",[23,24,25],"strong",{},"stable, blazing-fast, and beautiful foundational experience",".",[11,28,29],{},"Specifically, this phase includes:",[31,32,33,40,46],"ul",{},[34,35,36,39],"li",{},[23,37,38],{},"Smart desktop icon organization",": Custom grid areas, automatic categorization, drag-and-snap, and one-click switching between multiple layout schemes. This is the skeleton of the desktop—we get it standing first, smoother than any existing tool.",[34,41,42,45],{},[23,43,44],{},"Wallpaper engine",": Supports static wallpapers, video wallpapers, and HTML5 interactive wallpapers. Use an image, a video, or an entire webpage as your desktop background. The wallpaper layer embeds cleanly beneath desktop icons, never interfering with interaction.",[34,47,48,51],{},[23,49,50],{},"Built-in basic widgets",": Weather, clock, system monitoring, to-do list, quick-launch panels, and other common modules. We provide a set of thoughtfully designed default widgets that work out of the box, covering 80% of daily needs.",[11,53,54,55],{},"The core goal of this phase: ",[23,56,57],{},"Let users uninstall all other fragmented desktop utilities—AuraShell alone is enough.",[11,59,60],{},"We expect to complete alpha testing and optimization for this phase in Q2 2026, delivering the full core experience to our first 300 testers.",[15,62,64],{"id":63},"phase-2-open-the-ecosystem-sdk-custom-widgets-local-export","Phase 2: Open the Ecosystem — SDK + Custom Widgets + Local Export",[11,66,67,68,71],{},"Once the foundational experience is polished, we immediately move to ",[23,69,70],{},"developer-friendly transformation",". The desktop shouldn't only host components we build; anyone should be able to write their own desktop cards.",[11,73,74],{},"This phase includes:",[31,76,77,83,94],{},[34,78,79,82],{},[23,80,81],{},"AuraShell SDK release",": A CLI toolkit and debugging environment allowing developers to write desktop widgets using Vue 3 (React support planned). The SDK encapsulates system capabilities provided by Tauri—file I\u002FO, network requests, system info, and desktop-specific window management APIs.",[34,84,85,88,89,93],{},[23,86,87],{},"Custom widget loading",": Users can locally load ",[90,91,92],"code",{},".aura"," widget packages developed by themselves or third parties, drag them onto the desktop, and interact as if they were native windows. Widgets support free resizing, click-through, and pinning above the wallpaper layer.",[34,95,96,99],{},[23,97,98],{},"Local import\u002Fexport",": Widgets and desktop layout configurations can be exported as a single file, making backup, migration, and community sharing effortless. Share your carefully crafted desktop setup with a friend; they import and replicate instantly.",[11,101,102,103,106],{},"The significance of this phase: ",[23,104,105],{},"AuraShell begins to transform from a tool into a platform."," We don't dictate what your desktop should look like; we provide the canvas and the brushes.",[11,108,109],{},"Expected timeline: Q3–Q4 2026.",[15,111,113],{"id":112},"phase-3-establish-the-component-marketplace-from-sharing-to-commerce","Phase 3: Establish the Component Marketplace — From Sharing to Commerce",[11,115,116],{},"When the community starts producing a wealth of high-quality components, a centralized distribution channel becomes essential.",[11,118,119],{},"We will launch:",[31,121,122,128,138],{},[34,123,124,127],{},[23,125,126],{},"AuraShell Component Store",": An online marketplace built directly into the app. Users can browse, search, and one-click-install widgets and wallpaper themes. The store supports ratings, reviews, and update pushes.",[34,129,130,133,134,137],{},[23,131,132],{},"Creator onboarding and revenue sharing",": Developers can apply to become creators, upload works, and set them as free or paid (one-time purchase). We insist that ",[23,135,136],{},"the majority of revenue goes to the creator",", with the platform taking only a small operational cut.",[34,139,140,143],{},[23,141,142],{},"Quality review and security",": All published components undergo basic security checks (Tauri's sandboxing inherently limits widget permissions), ensuring user data safety.",[11,145,146,147,150],{},"This phase upgrades AuraShell from a \"personal productivity tool\" to a ",[23,148,149],{},"two-sided marketplace with commercial potential",". Desktop beautification gains a legitimate, monetizable content ecosystem for the first time.",[11,152,153],{},"Expected to begin rolling out in H1 2027.",[15,155,157],{"id":156},"future-vision-steam-launch-and-workshop-integration","Future Vision: Steam Launch and Workshop Integration",[11,159,160,161,164],{},"Our long-term goal is to bring AuraShell to ",[23,162,163],{},"the desktops of gamers worldwide",". Steam is the ideal channel.",[11,166,167],{},"Future plans include:",[31,169,170,176,182],{},[34,171,172,175],{},[23,173,174],{},"Steam store launch",": Release AuraShell as a desktop enhancement app on Steam. The base version remains free; a premium version (with AI organization, advanced wallpaper features, etc.) uses a one-time purchase model, aligned with Steam user payment habits.",[34,177,178,181],{},[23,179,180],{},"Deep Workshop integration",": This is the most critical step. Steam Workshop offers mature subscription and distribution mechanics. We'll enable widgets and wallpapers to be published directly through the Workshop. Users subscribe, and AuraShell auto-downloads and loads them—just like subscribing to mods in a game.",[34,183,184,187],{},[23,185,186],{},"Marketplace-Workshop bridging",": Our standalone component store will sync with Steam Workshop. A creator publishes on one side, and it optionally appears on the other. Paid components on Steam follow standard microtransaction flows, with transparent revenue splits. This means developers build once and reach users on both channels.",[11,189,190,191,194],{},"We aim to advance this phase during H2 2027 through 2028. By then, AuraShell will no longer be just a \"desktop tool,\" but a ",[23,192,193],{},"desktop content distribution and creation platform"," — similar to what Wallpaper Engine did for wallpapers, but covering a broader scope: wallpapers, widgets, full desktop themes, and workflow templates.",[15,196,198],{"id":197},"roadmap-at-a-glance","Roadmap at a Glance",[200,201,206],"pre",{"className":202,"code":204,"language":205},[203],"language-text","Phase 1 (2026 Q2)\nCore Foundation\nIcon Organization + Wallpaper Engine + Built-in Widgets\n──────────────────────────\nPhase 2 (2026 Q3–Q4)\nOpen Ecosystem\nSDK + Custom Widgets + Local Export\n──────────────────────────\nPhase 3 (2027 H1)\nComponent Marketplace\nOnline Store + Creator Revenue + Review System\n──────────────────────────\nPhase 4 (2027 H2+)\nSteam & Workshop\nGlobal Distribution + Workshop Integration + Dual-Channel Sync\n","text",[90,207,204],{"__ignoreMap":208},"",[15,210,212],{"id":211},"where-can-you-participate-right-now","Where Can You Participate Right Now?",[11,214,215],{},"We are in the alpha sprint of Phase 1. The first 300 testers will directly shape the core experience, and your feedback will influence the design of the SDK and marketplace rules down the line.",[11,217,218,219,226,229,230],{},"📧 Apply for alpha: ",[23,220,221],{},[222,223,225],"a",{"href":224},"mailto:liuxinye660@gmail.com","liuxinye660@gmail.com",[227,228],"br",{},"\n🌐 Website: ",[222,231,232],{"href":232,"rel":233},"https:\u002F\u002Faurashell.dev",[234],"nofollow",[11,236,237],{},"The desktop was never meant to be a static wasteland. Join us to turn it into the most creative space you own.",{"title":208,"searchDepth":239,"depth":239,"links":240},2,[241,242,243,244,245,246],{"id":17,"depth":239,"text":18},{"id":63,"depth":239,"text":64},{"id":112,"depth":239,"text":113},{"id":156,"depth":239,"text":157},{"id":197,"depth":239,"text":198},{"id":211,"depth":239,"text":212},"AuraShell is not a one-time software delivery; it's a gradually evolving desktop engine. Read our clear three-step roadmap and ecosystem vision.","md",{"date":250,"readTime":251,"icon":252,"image":253},"2026-04-24","7 min read","🗺️","\u002Fimages\u002Fblog\u002Froadmap.png",true,"\u002Fblog\u002Fen-us\u002Fproduct-roadmap",{"title":6,"description":247},"blog\u002Fen-US\u002Fproduct-roadmap","NUlqla9WC7H9SkcwT0isLBR4Uh-Ah5soWxluWOcFTUA",{"id":260,"title":261,"body":262,"description":471,"extension":248,"meta":472,"navigation":254,"path":476,"seo":477,"stem":478,"__hash__":479},"blog\u002Fblog\u002Fen-US\u002Fwhy-build-aurashell.md","Why I Built AuraShell: A 15MB Lightweight Windows Desktop Customizer",{"type":8,"value":263,"toc":464},[264,267,274,285,289,296,299,309,313,316,323,329,333,336,347,371,375,386,393,396,400,406,411,437,444,451,457,459],[11,265,266],{},"Chances are, your Windows desktop looks the same as it did years ago: a static wallpaper and a clutter of icons. The space that occupies our vision for hours every day remains strangely neglected, like an unfinished room.",[11,268,269,270,273],{},"I was once that user who couldn’t stand it anymore. I tried every ",[23,271,272],{},"Windows desktop customization software"," available: Wallpaper Engine, Fences, Rainmeter. Every attempt felt like opening a matryoshka doll — there was always a missing piece, some visual inconsistency, or a heavy resource load that made \"customization\" feel more like a compromise.",[11,275,276,277,280,281,284],{},"Eventually, I decided to stop waiting. Together with a few friends, I started building ",[23,278,279],{},"AuraShell"," — a high-performance ",[23,282,283],{},"Windows Desktop Customizer"," built with Rust and Tauri. Here is why we chose to reinvent the wheel.",[15,286,288],{"id":287},"_1-the-fragmentation-problem-one-all-in-one-desktop-engine","1. The Fragmentation Problem: One All-in-One Desktop Engine",[11,290,291,292,295],{},"The world of desktop tools is fragmented. You want a live wallpaper? Buy Wallpaper Engine. You want to tidy up your icons? Install a ",[23,293,294],{},"Desktop Organizer"," like Fences. You want widgets? Hunt down a Rainmeter skin and endure its ancient syntax.",[11,297,298],{},"These three things happen on the same screen yet require three separate apps that never communicate. The result: your system tray overflows, and your RAM vanishes.",[11,300,301,304,305,308],{},[23,302,303],{},"AuraShell’s mission is \"Unification.\""," We believe the desktop itself should be an integrated command center. By merging the wallpaper layer, icon organization, and widgets into a single ",[23,306,307],{},"All-in-One Desktop Engine",", we ensure your tools work in harmony rather than competing for resources.",[15,310,312],{"id":311},"_2-modern-aesthetics-escaping-the-windows-xp-ui","2. Modern Aesthetics: Escaping the \"Windows XP\" UI",[11,314,315],{},"I’m not singling anyone out, but many desktop enhancement tools still look like they were designed in the early 2000s.",[11,317,318,319,322],{},"The beauty I want isn’t a neon circus. It’s ",[23,320,321],{},"restrained, modern, and breathable native aesthetics",". Windows 11 brought us Acrylic and Mica materials — why isn’t there a toolchain that makes the desktop feel this premium?",[11,324,325,326,26],{},"We treat UI as a first-class citizen. AuraShell’s frontend is built with Vue 3 and Tailwind CSS, offering the visual quality of a top-tier SaaS product. Your desktop deserves to escape the patchwork look and embrace ",[23,327,328],{},"modern desktop customization",[15,330,332],{"id":331},"_3-the-performance-gap-why-lightweight-is-non-negotiable","3. The Performance Gap: Why \"Lightweight\" is Non-Negotiable",[11,334,335],{},"This is what infuriated me the most. Many popular tools run on the Chromium engine, with a single wallpaper process consuming 400MB+ of RAM. For developers running IDEs, VMs, or design tools, that 400MB is the straw that breaks the camel’s back.",[11,337,338,339,342,343,346],{},"We firmly chose ",[23,340,341],{},"Rust + Tauri + WebView2",". This architecture allows AuraShell to be the most ",[23,344,345],{},"Lightweight Windows Desktop Manager"," on the market:",[31,348,349,359,365],{},[34,350,351,354,355,358],{},[23,352,353],{},"Ultra-low Footprint:"," Only ",[23,356,357],{},"15–50MB RAM"," at idle — 10x lighter than Electron-based tools.",[34,360,361,364],{},[23,362,363],{},"Native Efficiency:"," We call Win32 APIs directly via Rust, bypassing bloated middleware.",[34,366,367,370],{},[23,368,369],{},"Instant Response:"," Performance shouldn't be the price of beauty. Your computer shouldn't feel like it’s rendering a heavy browser game just to show a wallpaper.",[15,372,374],{"id":373},"_4-minimalist-architecture-a-5mb-native-installer","4. Minimalist Architecture: A 5MB Native Installer",[11,376,377,378,381,382,385],{},"In an era where \"tiny\" utilities have 200MB installers, we chose a different path. By using ",[23,379,380],{},"Tauri’s minimal packaging",", the core AuraShell installer is under ",[23,383,384],{},"5MB",". It won’t stash a hidden Chromium instance on your drive or install dozens of background dependencies.",[11,387,388,389,392],{},"You’re downloading a genuinely native Windows application, not a browser in a coat. With our ",[23,390,391],{},"Developer SDK",", you can extend this lightweight core with your own programmable widgets using standard web tech.",[394,395],"hr",{},[15,397,399],{"id":398},"the-future-of-your-desktop","The Future of Your Desktop",[11,401,402,403,26],{},"Why did I build this? Because ",[23,404,405],{},"Windows desktop tools should be smarter, prettier, and lighter",[11,407,408],{},[23,409,410],{},"What we’ve built into AuraShell:",[31,412,413,419,425,431],{},[34,414,415,418],{},[23,416,417],{},"Smart Desktop Organizer"," — custom grid areas and auto-sorting.",[34,420,421,424],{},[23,422,423],{},"Next-Gen Wallpaper Engine"," — Interactive HTML5 and video support with hardware acceleration.",[34,426,427,430],{},[23,428,429],{},"Programmable Widgets"," — Write your own cards in Vue 3.",[34,432,433,436],{},[23,434,435],{},"Coming Soon:"," Widget Marketplace and Steam Workshop integration.",[11,438,439,440,443],{},"We’re currently recruiting the first ",[23,441,442],{},"300 Alpha Testers",". If you’re a power user who demands a better desktop experience without sacrificing performance, join us.",[11,445,446,447],{},"📧 Apply for Alpha: ",[23,448,449],{},[222,450,225],{"href":224},[11,452,453,454],{},"🌐 Official Site: ",[222,455,232],{"href":232,"rel":456},[234],[394,458],{},[11,460,461],{},[23,462,463],{},"Your desktop is the command center of your digital life. We’re rewriting that experience, one line of Rust and one Vue component at a time.",{"title":208,"searchDepth":239,"depth":239,"links":465},[466,467,468,469,470],{"id":287,"depth":239,"text":288},{"id":311,"depth":239,"text":312},{"id":331,"depth":239,"text":332},{"id":373,"depth":239,"text":374},{"id":398,"depth":239,"text":399},"Frustrated by Electron’s bloat, we rewrote the desktop experience in Rust. Discover how AuraShell merges a **Windows Desktop Organizer**, a live wallpaper engine, and widgets into one high-performance suite.",{"date":250,"readTime":473,"icon":474,"image":475},"8 min read","🛠️","\u002Fimages\u002Fblog\u002Fwhy-build.png","\u002Fblog\u002Fen-us\u002Fwhy-build-aurashell",{"title":261,"description":471},"blog\u002Fen-US\u002Fwhy-build-aurashell","x7MCDIVWOS_kk9BzW0xL-oo2ezpnIrYyHRCglGXJyEo",{"id":481,"title":482,"body":483,"description":729,"extension":248,"meta":730,"navigation":254,"path":734,"seo":735,"stem":736,"__hash__":737},"blog\u002Fblog\u002Fen-US\u002Fwhy-choose-tauri.md","Why I Chose Tauri Over Electron for This Desktop Tool",{"type":8,"value":484,"toc":723},[485,492,506,512,516,519,522,527,547,554,557,561,564,578,589,608,613,628,639,646,650,653,656,661,675,678,681,685,688,694,701,704,715,717],[11,486,487,488,491],{},"During the technology selection phase for AuraShell, the first and most critical question wasn't \"Which frontend framework?\" but rather ",[23,489,490],{},"\"What will host our entire desktop engine?\""," For a tool that embeds directly into the Windows desktop environment, interacts deeply with the system, and must not compromise on performance, the choice of underlying framework practically defines the project's DNA.",[11,493,494,495,498,499,502,503,26],{},"We had two main options: ",[23,496,497],{},"Electron"," and ",[23,500,501],{},"Tauri",". Many assume Electron is the only way to write desktop apps with web technologies—after all, VS Code, Figma, and Discord use it. But when we examined the actual requirements of a desktop enhancement tool, the answer became overwhelmingly clear: we chose ",[23,504,505],{},"Tauri (driven by Rust)",[11,507,508,509,26],{},"Here are the three decisive angles: ",[23,510,511],{},"extreme performance, system-level access, and minimal bundle size",[15,513,515],{"id":514},"_1-extreme-performance-a-desktop-tool-cannot-be-a-memory-vampire","1. Extreme Performance: A desktop tool cannot be a memory vampire",[11,517,518],{},"An Electron application essentially runs your webpage inside a bundled Chromium browser. No matter how simple your app’s functionality, launching it loads an entire browser kernel: V8 engine, renderer process, GPU process, network service… Even if all you want is a weather widget on the desktop, Electron will quietly consume hundreds of megabytes of RAM.",[11,520,521],{},"This is unacceptable in a desktop enhancement context. Our users already have VS Code, Chrome, Figma open, maybe Docker and WSL running too. AuraShell, as a persistent background application, must be featherlight. Ideally, it should sit as unobtrusively as a system tray icon, only invoking the WebView2 renderer when needed.",[11,523,524],{},[23,525,526],{},"Tauri fundamentally changes the resource model:",[31,528,529,535,541],{},[34,530,531,534],{},[23,532,533],{},"No bundled browser engine",": Tauri uses the operating system's native WebView (WebView2 on Windows, i.e., Edge kernel). This engine already exists on the user's machine; we merely reuse it. Zero additional runtime.",[34,536,537,540],{},[23,538,539],{},"Backend logic compiled as native Rust binary",": Rust code compiles directly to machine code, requiring no interpreter or virtual machine. Tasks like file monitoring, wallpaper layer injection, and window management are all handled by Rust at native performance levels.",[34,542,543,546],{},[23,544,545],{},"Minimal process model",": A Tauri app typically runs only two processes—the main process and the WebView renderer. Electron may spin up numerous auxiliary processes.",[11,548,549,550,553],{},"The result? AuraShell idles at roughly ",[23,551,552],{},"15MB"," of RAM and stays under 50MB even with a dynamic wallpaper playing. An Electron shell displaying only a static wallpaper can easily consume 200MB+. This order-of-magnitude difference isn't fixable with optimization; it's an architectural advantage.",[11,555,556],{},"We ran a simple test: create an empty Electron app and an empty Tauri app, launch them and do nothing. The empty Electron shell consumed ~120MB; Tauri's was ~5MB. Place a simple HTML page in each—the former shoots to 200MB, the latter stays around 15MB. In desktop tools, this gap defines the difference between \"user will uninstall\" and \"user forgot it's running.\"",[15,558,560],{"id":559},"_2-system-level-access-native-interaction-cannot-be-simulated","2. System-Level Access: Native interaction cannot be \"simulated\"",[11,562,563],{},"AuraShell is not an ordinary windowed application. We need to:",[31,565,566,569,572,575],{},[34,567,568],{},"Embed a wallpaper layer underneath desktop icons (WorkerW window)",[34,570,571],{},"Monitor file system changes to auto-organize icons",[34,573,574],{},"Create transparent, click-through, bottom-most widget windows",[34,576,577],{},"Seamlessly coexist with system tray, taskbar, and the desktop icon layer",[11,579,580,581,584,585,588],{},"These operations require direct Win32 API calls, some even involving undocumented system window handles. In Electron, you can use ",[90,582,583],{},"ffi-napi"," or ",[90,586,587],{},"node-win32-api"," to invoke system APIs, but it's essentially \"diplomacy\": you're tunneling out of a browser process to reach the outside world, crossing the JS engine, Node bindings, and C++ extension layers every time—performance and reliability are compromised.",[11,590,591,592,595,596,599,600,603,604,607],{},"Some fine-grained operations are practically impossible from Electron's Node layer. For example, precisely controlling extended window styles (",[90,593,594],{},"WS_EX_LAYERED",", ",[90,597,598],{},"WS_EX_TRANSPARENT",") on the wallpaper window, monitoring specific folders via ",[90,601,602],{},"ReadDirectoryChangesW",", or communicating with the desktop icon window (",[90,605,606],{},"SysListView32","). With Electron, you'd either write a native C++ module as a workaround or abandon the feature.",[11,609,610],{},[23,611,612],{},"Tauri provides a \"native-first\" capability:",[31,614,615,622,625],{},[34,616,617,618,621],{},"The backend is directly Rust, enabling zero-overhead calls to any Win32 API. No extra binding layers, no ",[90,619,620],{},"node-gyp"," rebuild nightmares.",[34,623,624],{},"Tauri's API surface naturally supports window control, file system access, system tray, global shortcuts—things that often require extra packages or native modules in Electron.",[34,626,627],{},"More critically, Tauri allows you to handle complex system logic on the Rust side and pass only the final results as JSON to the frontend WebView. This means the frontend code is always a lightweight UI description, while the real \"heavy lifting\" happens in Rust.",[11,629,630,631,634,635,638],{},"For instance, AuraShell's icon organization requires real-time monitoring of multiple folders, triggering automatic rearrangement when files change. In Rust, we directly use the ",[90,632,633],{},"notify"," crate to listen for file system events—efficient and zero-latency. In Electron, you'd rely on Node's ",[90,636,637],{},"fs.watch",", which depends on libuv's event loop underneath; efficiency and reliability are on a different tier.",[11,640,641,642,645],{},"System-level access isn't just about \"can it run?\"—it demands ",[23,643,644],{},"native-grade responsiveness and stability",". Tauri's Rust backend makes us feel like we're writing a true Windows program, with the frontend merely a UI shell bolted on. This architecture is purpose-built for a desktop engine like ours.",[15,647,649],{"id":648},"_3-minimal-bundle-size-an-installer-should-not-download-a-browser","3. Minimal Bundle Size: An installer should not download a browser",[11,651,652],{},"We've all seen it: a user wants to try a small desktop utility, sees a 200MB download, 500MB after installation, and walks away. Electron packages bundle the entire Chromium runtime, meaning the simplest \"Hello World\" application easily exceeds 100MB.",[11,654,655],{},"For a tool like AuraShell, bundle size directly impacts distribution and conversion. Our planned promotion includes posts on V2EX, GitHub, and social media—users' first impressions often come from download speed and unpacked size. If the installer is too large, many won't even wait for it to finish.",[11,657,658],{},[23,659,660],{},"Tauri's advantage in bundle size is crushing:",[31,662,663,669,672],{},[34,664,665,666,26],{},"Tauri distributes a compiled binary, typically a few MB. Our core program is expected to be ",[23,667,668],{},"under 5MB",[34,670,671],{},"It leverages the OS-native WebView2, carrying no browser runtime. Windows 10 1803+ already includes or auto-installs WebView2 transparently.",[34,673,674],{},"Assets and frontend UI files (HTML\u002FJS\u002FCSS) are bundled into the binary but are very small after compression.",[11,676,677],{},"Compare: a typical Electron app (like Wallpaper Engine’s configuration UI) can easily be several hundred MB. Our entire desktop engine, built with Tauri, might be smaller than a high-resolution wallpaper. This contrast itself is a technical narrative: \"You're downloading not a browser in costume, but a genuinely native program.\"",[11,679,680],{},"Additionally, a small bundle means low update costs. We can release frequent patches without forcing users to download tens of MB each time—critical during the rapid iteration of the alpha phase.",[15,682,684],{"id":683},"choosing-tauri-is-choosing-a-philosophy","Choosing Tauri is choosing a philosophy",[11,686,687],{},"Electron is not without value. It has enabled countless web developers to quickly build cross-platform desktop apps, and its ecosystem and maturity are unmatched. But its original design purpose is \"bring web apps to the desktop\"—its DNA carries the heavy troops of a browser.",[11,689,690,693],{},[23,691,692],{},"AuraShell's positioning is completely different."," We're not a ported web app; we're a tool born from inside the Windows desktop. It needs to seep into every corner of the system like water, demanding extreme lightness and native feel. Tauri gives us that possibility: use the best systems language (Rust) for low-level logic, use the most flexible UI technology (web frontend) for presentation, bridged by a minimal IPC layer.",[11,695,696,697,700],{},"To sum it up: ",[23,698,699],{},"Electron hands you a Swiss army knife; Tauri hands you the operating system's own scalpel."," For a desktop engine, we need the scalpel.",[11,702,703],{},"AuraShell is currently recruiting its first 300 alpha testers. If you’d like to experience a tool powered by Rust, just a few MB in size, yet capable of fundamentally transforming your desktop, we welcome your email.",[11,705,218,706,710,229,712],{},[23,707,708],{},[222,709,225],{"href":224},[227,711],{},[222,713,232],{"href":232,"rel":714},[234],[394,716],{},[11,718,719],{},[720,721,722],"em",{},"Next post we’ll dive into technical details: how to embed a custom wallpaper layer under desktop icons using Rust and Win32 API. Stay tuned.",{"title":208,"searchDepth":239,"depth":239,"links":724},[725,726,727,728],{"id":514,"depth":239,"text":515},{"id":559,"depth":239,"text":560},{"id":648,"depth":239,"text":649},{"id":683,"depth":239,"text":684},"Why did the AuraShell team abandon Electron and choose Rust-driven Tauri for their desktop engine? Here are the technical reasons.",{"date":250,"readTime":731,"icon":732,"image":733},"6 min read","🦀","\u002Fimages\u002Fblog\u002Fchoose-tauri.png","\u002Fblog\u002Fen-us\u002Fwhy-choose-tauri",{"title":482,"description":729},"blog\u002Fen-US\u002Fwhy-choose-tauri","NxpyjJGp0YW-1y_CqytXxcQmwlBQbsm8cqcVQZKONlU",1778166894573]