Meta open-sourced Muse Glimmer this week, a small-parameter model (an LLM with fewer tunable internal parameters, making it lighter and faster) that runs directly on phones and laptops, with the sibling Muse Spark 1.2 also due out soon. Community discussion has converged on two points: parameter count reportedly sits between 2B and 4B (2 to 4 billion), and the headline use case is full local inference — data stays on-device, no cloud dependency.
What this is
So-called "local AI models" are AI that run on your own device with no server connection. Over the past year, large models have mostly lived in cloud data centers, and local models have routinely been dismissed as "small, dumb, and slow." Meta's two products take a different bet: trim capability down to just-enough, in exchange for privacy, offline operation, and lower latency.
In short, Meta is wagering on a judgment: not every AI task needs to call on a GPT-4-class brain. Plenty of scenarios — phone keyboard suggestions, local document summarization — are fine with a small, focused model.
Industry view
Supporters say this is the right direction for on-device AI (AI that runs directly on the endpoint device rather than being uploaded to the cloud). Bloomberg and The Information have both previously reported that Apple and Google are betting on the same path with their custom chips, on the grounds that inference cost (the compute fee incurred every time an AI is called) becomes an ever-heavier burden for cloud models, especially once a product crosses the hundred-million-user line.
But the pushback is just as clear. Hugging Face engineers have said on multiple podcasts that for most users, local models "save on API fees but drive up the electricity bill," because inference (the process of the model generating a response from an input) continuously taxes CPU and battery. On Reddit's r/LocalLLaMA, plenty of hands-on testers report that models like Muse Glimmer are passable on English tasks but noticeably weaker than same-size Qwen (Tongyi Qianwen, Alibaba's open-source model family) on Chinese.
Our own judgment: local models are not a replacement for the cloud — they are a complement. Their real value lies in privacy-sensitive scenarios (medical, legal) and offline scenarios (business travel, cross-border work), not in daily office work.
Impact on regular people
For enterprise IT: Cloud APIs will remain the default in the short term. Deploying local models drags in device compatibility, ops, and security audits — complexity goes up, not down.
For working professionals: Regular users don't need to rush out and tinker with local models. If ChatGPT, ERNIE, or Tongyi Qianwen already cover your daily use, a few hundred bucks a year for a subscription buys you a lot more than a new phone would.
For the consumer market: Over the next 1-2 years, phone makers will start advertising "built-in AI," but like today's "AI photography," most of it will be marketing fluff. The test is simple: ask whether it can work offline.