The odd thing is that this disguises as some bare metal, hackable device.

Their TUI[1] is planned to use react(!), to share logic with their BrowserUI[2]. In the repos you can see how they struggle to get anything gpu backed done (which is required by the browser). Then falling back to wayland to do it for them. (This all seems a mess that LLMs can't figure out.)

Anyway, it does seem to end up in a custom linux desktop environment, with lots of sharp edges that makes it less hackable.

[1] https://docs.flipper.net/one/cpu-software/flipctl [2] entirely unclear why a terminal is insufficient for networked TUIs

> First one is simple and focused

First time I've heard anyone call the Flipper Zero "simple" and "focused", most people seemed to have considered it a "swiss-knife" meant to just house a bunch of features and radios, meanwhile the One has less features but more connectivity and I/O.

But apparently you're not alone in feeling this, but I don't understand what from the submission makes you and others believe so, what exactly gave you this impression?

Agreed. This will likely never ship with all the bloat. Custom AI model, custom OS, extremely custom architecture (2 "main" processors running independently...), barely reuses any of the previous work from Flipper Zero.

They're very explicit that Flipper 1 isn't a "v2", but a device that targets different use cases.