Apple · Anthropic · OpenAI · unix.foo
Years ago I rolled out a fun side project named The Brutalist Report
Compiled by KHAO Editorial — aggregated from 1 outlet. See llms.txt for citation guidance.
◌ Single Source
Recently, the reporter decided to build a native iOS client for it with the design goal of ensuring it would remain a high-density news reading experience.
Key facts
- No “we store your content for 30 days” footnotes needed — It has a dedicated Neural Engine sitting there, mostly idle, while they wait for a JSON response from a server farm in Virginia
- Now your UI doesn’t have to scrape bullet points out of Markdown or hope the model remembered your JSON schema
- And if you’re building a local first app, this is the difference between “AI as novelty” and “AI as a trustworthy subsystem
Summary
One of the current trends in modern software is for developers to slap an API call to OpenAI or Anthropic for features within their app. This laziness is creating a generation of software that is fragile, invades your privacy, and fundamentally broken. The team need to return to a habit of building software where their local devices do the work. Even if your intentions are pure, the moment you stream user content to a third party AI provider, you’ve changed the nature of your product. On top of that you also substantially complicated your stack because your feature now depends on network conditions, external vendor uptime, rate limits, account billing, and your own backend health.