https://tproger.ru/news/claude-code-2-1-282-ispravil-owibki-razrewenij-vosstanovleniya-s
https://github.com/anthropics/claude-code/releases/tag/v2.1.282
https://android-developers.googleblog.com/2026/09/wireless-debugging-adb-wifi-2.html
Wireless debugging on Android is now faster, more reliable, and easier to set up than ever. With ADB Wi-Fi 2.0, we’ve introduced a new server stack and smarter network handling to directly address developer feedback around usability gaps.
https://twitter.com/kotlin/status/2102006181589864861
Ktor 3.6.0 is out! 🎉
The release brings new experimental features, including:
🔶 Typed authentication
🔶 The OpenID Connect plugin
🔶 HTTP/3 support for the Netty engine
🔶 Simpler client setup for Kotlin Multiplatform
Read the blog post for more details ⬇️
Preparing your app for broader memory limits
https://android-developers.googleblog.com/2026/08/app-broader-memory-limits.html
A great user experience is central to Android’s mission, and delivering on that promise requires keeping devices fast, responsive, and reliable. This is why memory optimization is more critical than ever. Across the ecosystem, new devices are maintaining or even decreasing their physical memory capacity in response to memory price increases, yet users continue to expect the same seamless, high-performance app experience.
In Android 17, we introduced per-app memory limits, starting with Pixel devices, to help protect the overall user experience from applications using excess memory and causing system-wide slowdowns. Over the coming year, an increasing number of manufacturers will leverage the Android per-app memory limits across their portfolio of device RAM configurations from 4GB to 16GB+ devices. If your app exceeds these limits, it will be slowed down and may be terminated. Optimizing your app’s memory footprint is essential to preventing OS throttling and maintaining a seamless user experience.