Adding AI to Flutter used to mean two roads: stuff the model key into the app and call it directly, or hand-assemble requests with http. The first is handing over the keys; the second has you hand-crafting a shoddy framework by day three, patching in retries, streaming, tool calls and structured output one at a time.
On-device search used to be assembly work. Images had to go through a captioning model to become text, audio had to be transcribed, video had to be frame-extracted and subtitled, and then all of it got thrown at a text embedding model. Every modality you added meant another chain, another slice of latency, another pile of intermediates.
An engineer was doing size optimization on his own iOS build and found that one extra compiler flag shrank the bundle by 15 MiB. He filed an issue with a reproduction on a public project and data from real devices, and opened a pull request that same night.
By the time a cross-platform project reaches release, there is usually more than one distribution path. One through Google Play, one straight from your own site, and sometimes a test build for the QA folks. Android’s developer verification reprices the entry cost of each path, and the three bills are not calculated the same way at all.
If you have friends in Brazil, Indonesia, Singapore or Thailand, after September 30 they may run into something new: tap install in some app store, get a prompt saying the developer isn’t verified, and it won’t install. At the same moment, the China-market Android phone in your hand installs anything with no change at all.
On October 6, JetBrains’ Amper blog published its final post, titled Amper Is Now the Kotlin Toolchain. The name carries a line underneath, Moving to the Kotlin Blog, and it means what it says: that blog stops updating as of that day and merges into the Kotlin blog.
On October 5 JetBrains published a short announcement with a blunt title: IDE support for the Swift language is ending in the KMP plugin. The effective versions are specific: IntelliJ IDEA 2026.3 and Android Studio Rabbit 2 | 2026.2.2.
You ask the agent to add a date picker. It installs a calendar library, writes a wrapper component, adds a stylesheet, and then starts discussing time zones with you.
It is two in the morning, the machine has started swapping, you have hit later on the update prompt three times, and you still will not reboot.
If you write Kotlin Multiplatform you have probably hit this: the line is red in the IDE, underlined with a cannot find symbol, you hesitate for ages and do not dare commit, then you build and it is green, and it even runs correctly.
I have three agents installed in my terminal right now: claude, opencode, gemini. A few days in and I hit a new annoyance. Once there are several sessions, I have no idea who is running, who changed which files, or who spent how much. I end up scrolling through terminal history to figure it out.
On the morning of September 30, DeepSeek announced on its official WeChat account that it is open-sourcing infrastructure components for Huawei’s Ascend compute platform: a TileLang high-level language compiler tool, a high-performance compute library, and a distributed communication library. Their wording was that these correspond one-to-one with the components previously open-sourced for NVIDIA’s platform.