Read more of this story at Slashdot.
Read more of this story at Slashdot.
Elon Musk's SpaceX IPO will probably make him the richest person to ever walk the planet. And while his mountain of horrible personal conduct could fill multiple books, one fact in particular stands out: A year ago, Musk's actions directly led to the deaths of hundreds of thousands of people. He did it knowingly. And, worse - gleefully.
This is not a serious person, but his abuse of the world is deadly serious. In the first months of President Donald Trump's second term, the Musk-led Department of Government Efficiency (DOGE) destroyed the US Agency for International Development, whose mission was a boon to public health around the globe. M …
max-lines-per-function, max-nested-callbacks, and max-statements now highlight only the function header instead of the entire function.max-depth and no-with now highlight only the first keyword.max-depth and max-nested-callbacks rules. These bug fixes can result in reporting more linting errors in existing code.5ca8c52 feat: correct stack tracking in max-nested-callbacks (#20973) (Pixel998)b565783 feat: report no-with violations at the with keyword (#20971) (Pixel998)2ce032f feat: report max-lines-per-function violations at function head (#20966) (Pixel998)732cb3e feat: report max-nested-callbacks violations at function head (#20967) (Pixel998)f9c138a feat: report max-depth violations on keywords (#20943) (Pixel998)bdb496c feat: correct max-depth handling for else-if chains (#20944) (Pixel998)c296873 feat: update error loc in max-statements to function header (#20907) (Taejin Kim)8ae1b5b docs: Update README (GitHub Actions Bot)ca7eb90 docs: update Node.js prerequisites to include ICU support (#20962) (Francesco Trotta)f99b47a docs: Update README (GitHub Actions Bot)acf03d4 docs: clarify precedence of parserOptions over languageOptions (#20926) (sethamus)b18bf58 chore: update ecosystem plugins (#20959) (ESLint Bot)c2d1444 refactor: replace areAllSegmentsUnreachable with !isAnySegmentReachable (#20951) (Taejin Kim)243b8c5 chore: enhance config-rule to support oneOf, anyOf, and nested schemas (#20788) (kuldeep kumar)217b2a9 test: add unit tests for ParserService (#20949) (Taejin Kim)72003e7 test: add location information to error messages in max-statements (#20945) (lumir)7797c26 refactor: deduplicate isAnySegmentReachable across rules (#20890) (Taejin Kim)67c46fa chore: update ecosystem plugins (#20938) (ESLint Bot)95d8c7a chore: update dependency @eslint/json to v2 (#20934) (renovate[bot])cf9e496 chore: update @arethetypeswrong/cli to 0.18.3 (#20933) (Pixel998)fb6d396 test: run type tests with TypeScript 7 (#20868) (sethamus)WordPress already holds your content, media, users, plugins, and more.
But managing all of those moving pieces often means jumping between admin screens, browser tabs, and disconnected workflows.
Desktop Mode, a free and open source plugin built by Automattic, gives WordPress admin a desktop-style workspace.
Windows open, resize, and stack. A dock sits on the left. Virtual desktops let you switch between workflows. It runs on top of WordPress exactly as it is: your site, your plugins, your setup, all untouched.
Posts, pages, and media open as individual windows, so you can have a draft open next to your media library and drag files directly between them—no tab switching. No losing your place.
Send content to a shared folder so your team can review and approve it before it goes live. Restore anything from a unified Recycle Bin covering posts, pages, media, and comments, all from one place. Your window layout saves between sessions, so you pick up exactly where you left off.
A unified command palette (Cmd+K) gives you fast access to everything. The optional AI copilot lets you search across your content, find posts by topic, surface related pages, and get quick answers about what’s on your site. Multiple desktops, called Spaces, let you keep separate projects or workflows organized without cluttering your view.
Desktop Mode comes with hundreds of hooks built in. Every significant behavior is extendable, meaning plugin authors can register native windows, dock items, desktop icons, commands, and AI tools from their own plugin with no patches to Desktop Mode required. You can even register your own AI provider, wiring Desktop Mode’s copilot to any model or service you choose.
Here’s what that looks like in practice: a booking plugin could open its calendar as a native window directly inside Desktop Mode instead of sending you to a separate admin page. A WooCommerce extension could surface your orders dashboard right in the dock. Nick, a long-time WordPress developer, built a native plugin on top of Desktop Mode to test this extensibility from day one, and it works.
Desktop Mode runs entirely in the admin layer, so your site’s frontend, your store, and your checkout are completely unaffected.
The same architecture that lets thousands of WordPress plugins coexist applies here. It’s open source, the code is on GitHub, and contributions are open.
WordPress has always been more than a publishing tool. It’s a platform built to be shaped, not just used. Desktop Mode is a bet on that idea.
What if the place where you manage your site also felt like a real workspace? Where your team can review content before it goes live, your tools open where you need them, and you stop losing time navigating between screens? That’s what we’re building toward.
Already running on hundreds of sites in its first week, it’s actively maintained by Automattic and the community is building on it. This is the foundation and we can’t wait to see where it goes.
Desktop Mode is free for all WordPress users and available today.
It’s a per-user opt-in, so activating it doesn’t affect anyone else on your team until they choose to turn it on themselves.

Most devs over‑optimize the model 🤖
The real leverage is in the system 🔧
Tweaking prompts & swapping models ≠ better outcomes
Giving AI the right data + context = better reasoning + results
Build the pipeline, not just the prompt.
Budget Bytes: https://msft.it/6056viD9Q
SUMMARY
On-device AI runs directly on local devices instead of relying on remote servers. Typically, large AI models are trained in the cloud and then compressed so devices can use them for real-time inference. This approach improves speed, enhances privacy, allows offline functionality, minimizes network bandwidth usage, and reduces cloud costs. However, it also introduces challenges, including limited device resources, the need for model optimization, complex update distribution, and increased power consumption. Ongoing advancements in hardware and increasing consumer privacy demands are expected to rapidly expand the role of on-device AI across industries.
On-device AI refers to artificial intelligence algorithms that run directly on local hardware rather than relying on a remote cloud server. The core concept is to bring the intelligence directly to the device where the data originates.
Instead of sending your voice, image, or text data to a server hundreds of miles away, the computation happens right where you are. These models run entirely locally on everyday devices like smartphones and Internet of Things (IoT) sensors, as well as on dedicated edge hardware.
Modern smartwatches use local AI to detect falls or monitor irregular heartbeats. Smart home cameras use it to distinguish between a passing car and a person at your front door. Even your smartphone keyboard uses local models to predict your next word without sending your keystrokes to the web.
To understand how on-device AI operates, let’s begin with how teams of engineers, data scientists, developers, and other specialists build and deploy these systems.
First, they train a large AI model on powerful cloud computers until it has learned everything it needs. Then they shrink the model’s massive algorithms down to a manageable size so they can push it directly to the local device.
This process highlights the key difference between training and inference. Training an AI model requires massive amounts of data and computing power, which is why training almost always stays in the cloud. Inference is the act of using the trained model to make predictions or decisions. On-device AI focuses almost exclusively on inference.
Standard processors often struggle with the heavy computational demands of neural networks, so modern hardware employs specialized acceleration to speed up local inference. Hardware manufacturers now include neural processing units (NPUs), mobile GPUs, and specialized AI chips directly on device motherboards.
By shifting computing power to the edge, on-device AI provides several distinct advantages for both users and businesses.
When data has to travel from a device to the cloud and back again, applications are slower to respond. On-device AI eliminates round-trip latency and enables instant responses for applications such as autonomous driving and real-time language translation.
Sending personal data over the internet always carries some risk, while keeping it on local hardware inherently protects user privacy. With on-device AI, sensitive information such as fingerprints, voice recordings, and medical data never has to leave the device.
Using an edge vector database for AI can help you increase privacy and enhance performance simultaneously.
Cloud-based AI fails the moment you lose internet access, whereas on-device models work uninterrupted regardless of your connection status. With on-device AI, you can continue to use intelligent features even in remote locations, deep underground, or during network outages.
With Couchbase Mobile, we’ve recently delivered major enhancements for building offline-first AI applications at the edge. You can learn more about our multipurpose capabilities in this blog post.
Processing massive amounts of data on centralized servers is incredibly expensive and eats up tons of network bandwidth. By shifting inference to local hardware, companies can drastically reduce their cloud computing bills and ease the burden on telecommunications networks.
Despite its advantages, moving intelligence to local hardware is not without significant hurdles, including:
A smartphone simply can’t compete with a massive data center. Edge hardware has strict limitations on memory, processing power, and storage space, so developers must carefully balance the capability of their AI with the physical limits of the hardware it runs on.
Large language models often require dozens of gigabytes of RAM to function, so fitting an LLM on a consumer device requires extreme optimization. Engineers must constantly shrink model sizes while trying not to sacrifice accuracy.
Updating software on millions of distributed edge devices is a logistical headache. Unlike updating a single model on a central cloud server, companies must ensure updates reach every individual device safely without breaking existing functionality.
AI calculations require significant energy, and running heavy models locally can drain a mobile device battery in minutes. Managing power consumption is a constant battle for hardware designers and software engineers alike.
To choose wisely between local and cloud-based processing, you need to understand the fundamental differences between the two architectures.
Cloud AI relies on centralized data, and it offers virtually unlimited processing power and storage, making it ideal for massive models like ChatGPT. You should use cloud AI when you need to process huge datasets, run complex training algorithms, or offer high-compute services where latency is not a critical issue.
On-device AI relies on decentralization, and it prioritizes speed, privacy, and independence over raw computing power. You should use on-device AI when you need immediate real-time responses, strict data privacy, or guaranteed offline capabilities.
Many modern applications use hybrid models. For instance, a smart speaker might use an on-device model to listen for a wake word like “Hey Siri.” Once activated, the speaker sends complex requests to the cloud for heavy processing. This edge-plus-cloud approach offers the best of both worlds.
Local intelligence has already been successfully deployed across many major industries.
Smartphones are the biggest playground for on-device AI. They commonly use it for functions like voice assistance, instant photo assist, and live language translation.
Smart home appliances use local processing to become more autonomous. Thermostats learn your daily schedule to adjust temperatures, smart locks recognize approved faces, and robotic vacuums use spatial AI to navigate your home.
Local AI improves your shopping experience, even when you don’t know it’s there. Retailers use edge computing for intelligent point-of-sale systems, smart mirrors can instantly overlay different clothing colors onto a customer, and in-store cameras process foot traffic to optimize store layouts.
In this blog post, you can learn how retailers are using Couchbase Mobile and Google GenAI to power self-serve kiosks, inventory management, and in-store personalization.
In industrial environments, waiting for a cloud response could result in costly downtime or shipment of defective products. To prevent such inefficiencies, businesses use local AI models to monitor machinery for wear and tear, inspect products on assembly lines with cameras, and sort packages in warehouses with robots.
If you’re planning to build applications using local intelligence, follow established best practices to save yourself time and headaches.
First, master model optimization techniques:
Second, handle data efficiently:
Third, prioritize security. Even though data stays local, devices can be stolen:
Finally, choose the right tools and frameworks:
The shift toward local computing will only accelerate as hardware continues to become more advanced.
There’s already incredible momentum behind AI hardware, and chip manufacturers are dedicating more of their silicon to neural processing. At the current pace, it won’t be long before edge devices can run billion-parameter language models entirely on their own.
This evolution will have a huge impact on privacy-first applications as people become more protective of their digital footprints. To meet user demands, companies will have no choice but to process more data locally, and on-device AI will become a core selling point for consumer tech.
At the same time, on-device AI capabilities will rapidly spread into entirely new industries and expand where they’re already being used. Healthcare devices, for example, will be able to monitor complex biometrics without relying on a Bluetooth connection to a phone. And farmers will be able to use drones to navigate and analyze crop health across thousands of acres without needing a cellular connection.
On-device AI is fundamentally shifting how we process data by moving intelligence from distant cloud servers directly onto the hardware we use daily. This transition unlocks massive benefits in speed, privacy, and offline capabilities, though it requires clever engineering to overcome battery and memory constraints. As specialized hardware continues to evolve, local AI will become the standard foundation for modern technology.
Key takeaways:
Related resources:
How do you deploy and update AI models on edge devices at scale? Companies use over-the-air (OTA) updates to push new models to devices. This requires a robust mobile device management system to ensure models download securely in the background without interrupting the user experience.
What types of hardware are best suited for on-device AI workloads? Devices equipped with neural processing units (NPUs) or specialized AI accelerators are best. These chips process the complex math of neural networks much faster and with less power than standard CPUs.
How do developers optimize AI models to run efficiently on constrained devices? Developers use techniques such as quantization (reducing mathematical precision), pruning (removing unused neural connections), and knowledge distillation (training a smaller model to mimic a larger one) to shrink model size.
What security risks are unique to on-device AI, and how can they be mitigated? Local models can be reverse-engineered if a device is physically stolen. Developers mitigate this by using hardware-backed encryption, secure enclaves, and strict access controls to lock down the local file system.
How do you monitor the performance and accuracy of AI models running locally? Developers build lightweight telemetry into the application. The app silently tracks success rates and error codes locally, then sends small, anonymized summary logs back to the cloud when the device has a stable connection.
What tools and frameworks are commonly used to build on-device AI applications? The most popular frameworks are TensorFlow Lite, PyTorch Mobile, ONNX Runtime, and platform-specific tools like Apple’s Core ML and Android’s Neural Networks API (NNAPI).
The post On-Device AI: Benefits, Use Cases, and Challenges appeared first on The Couchbase Blog.