Earlier quoted context omitted.
I hate to say it, but this looks like the sort of thing a CEO told their team to build on Monday morning in a panic because they are grasping for ways to participate in the AI craze. And the team did just that: they built it that morning using Claude Code. There is truly nothing original here and the product doesn't have a chance in hell of earning money. Local LLMs on-device will be dominated by the device vendors,…
Wanted to share a message here with the CEO not to feel too bad because little is more common than getting caught by this tech But where are they! https://ente.com/about Small team, rooting for them
Ensu – Ente’s Local LLM app
121–130 of 198 posts
Re: Ensu – Ente’s Local LLM app
#122Re: Ensu – Ente’s Local LLM app
#123Re: Ensu – Ente’s Local LLM app
#124Re: Ensu – Ente’s Local LLM app
#125Re: Ensu – Ente’s Local LLM app
#126Earlier quoted context omitted.
This seems to be a general chat app, but otherwise small models can be very effective within the right use cases and orchestration.
> otherwise small models can be very effective within the right use cases and orchestration very limited amount of use cases, perhaps. As a generalized chat assistant? I'm not sure you'd be able to get anything of value out from them, but happy to be proven otherwise. I have all of those locally already, without fine-tuning, what use case could I try right now where any of those are "very effective"?
You can use a small coding model to produce working code with a deterministic workflow (ex: state machine) if you carefully prune the context and filter down what it can do per iteration. Instead of letting it "reason" through an ever growing history, you give it distinct piecemeal steps with tailored context.
I think this can be generalized to:
Anything that can be built from small, well understood pieces and can be validated and fixed step by step. Then the challenge becomes designing these workflows and automating them.
(I'm not there yet, but one thing I have in mind might be a hybrid approach where the planning is produced by a more expensive model. The output it has to produce are data driven state machines or behavior trees (so they can be validated deterministically). Then it offloads the grunt work to a small, local model. When it's done, the work gets checked etc.)
Re: Ensu – Ente’s Local LLM app
#127Re: Ensu – Ente’s Local LLM app
#128I just tried it. It downloaded Qwen3.5 2B on my phone and it's pretty coherent in its sentences, but really annoying with the amount of Ente products mentioned in every occasion. Other than that it's fast enough to talk to and definitely an easy way to run a model locally on your phone.
>but really annoying with the amount of Ente products mentioned in every occasion https://github.com/ente-io/ente/blob/f254af939ff6950b63edf5f... Here is the system prompt, kinda embarassing
Re: Ensu – Ente’s Local LLM app
#129Given how the blog is presented, I assumed this was something novel that solved a unique problem, maybe a local multi-modal assistant for your device. I installed it and it's none of that. It is a mere wrapper around small local LLM models. And, it's not even multi-modal! Anyone could've one-shotted this in Claude in an hour (I'm not exaggerating). What's the target audience here? Your average person doesn't care abo…
It’s a platform play so they can get people onto their defunct photos platform. “Big Tech” in a little suit.
(Though I think this announcement is sufficiently unpleasant I'm starting to reconsider)
Re: Ensu – Ente’s Local LLM app
#130Given how the blog is presented, I assumed this was something novel that solved a unique problem, maybe a local multi-modal assistant for your device. I installed it and it's none of that. It is a mere wrapper around small local LLM models. And, it's not even multi-modal! Anyone could've one-shotted this in Claude in an hour (I'm not exaggerating). What's the target audience here? Your average person doesn't care abo…
I hate to say it, but this looks like the sort of thing a CEO told their team to build on Monday morning in a panic because they are grasping for ways to participate in the AI craze. And the team did just that: they built it that morning using Claude Code. There is truly nothing original here and the product doesn't have a chance in hell of earning money. Local LLMs on-device will be dominated by the device vendors,…
But sure, making money with standalone "local first is our headline feature" will be incredibly hard against those, no doubt about that. In light of the limited quality of what local models can achieve, the privacy bonus just won't compel many to pay. But that only means that this "morning with Claude" you are suggesting might be just the right amount of investment for the result you'd realistically expect. But is that so bad? I'd argue the reverse: bundling up the low hanging fruit but not by some hobbyist who will lose interest two weeks on but by a company big enough the keep it going while small enough to not be a VC furnace that will inevitably turn on users once the runway runs out (*), that's an opportunity to fill a niche few others can. Valuable for users who don't want to roll their own deployment of open source models (can't, or unwilling to commit to keeping them up to date, assuming that Ente does keep that ball rolling), and also valuable for the company of the investment actually is so low that it pays by raising awareness for their other products that apparently do earn them money.
(*) I was googling around a little wondering if they actually are as close to bootstrapped as they seem on the surface, and yes, that's supposedly the core idea [0], but despite that they also took 100 kUSD in "non-diluting" (basically a gift then?) from Mozilla with the explicit goal "to promote independent AI and machine learning" [1]. So not a CEO whim but following up to a promise made earlier. If they actually did avoid spending all that money on a one-off but went smaller planning to keep it current for a longer time horizon, I'd congratulate them on an excellent choice.
[0] https://ente.com/blog/5-years-of-ente/
[1] https://ente.io/blog/mozilla-builders/
The hn discussion for [1] seems to be completely missing the point, that Mozilla program isn't about funding an image host (yeah, I'd also prefer if Mozilla focused on the Browser and perhaps Thunderbird, but the foundation is what it is): https://news.ycombinator.com/item?id=41681666