AndroidPhrophet

🔥🌟 Just here to build some dope android shi!!!! 🌟 🔥

After years of waiting for this feature, we finally have it in Kotlin! Collection literals are supported as an experimental feature since Kotlin 2.4. The idea is simple: You can create a collection using a box bracket. Based on the specified type, a different collection type might be created, like a list or a set. If no type is specified, a list is created by default. Collection literals associated with the of operator on a companion object. You can make them work for custom types by defining this operator. It mustn’t be an extension. Collection literals require Kotlin 2.4 (such as "2.4.0-Beta2”), "-Xcollection-literals” compiler argument, and IntelliJ IDEA 2026.2 (which should be released in EAP around May 5th). Here you can see them used in the KotlinConf application: github.com/JetBrains/kotl…

Exposed supports `upsert`? Insert or update rows with ease. Explore this and other features in the docs 👇 kotl.in/jeansi

Aurora Borealis! Still on to visit list👌

Words to live by first Create then you can iterate 👌

Last pull request of the sprint merged! It's Vacay Season BAAAABYYYYYY!!!

Using Column to display a long list loads all items at once, which slows down applications 📉 You should use LazyColumn, which only loads elements that are needed❗

aaahhhhhhhhhhhhhhhhh! this crazy annoying pipeline today! freaking hate when these things decides they wanna stress you near deadlines.....

Don't wait until the September 2026 deadline, prepare your Wear OS apps for the 64-bit devices today. goo.gle/4v4yHr7 Follow these steps to assess your app: 🔍 Inspect APKs for native .so files using APK Analyzer 📦 Ensure parity between 32-bit and 64-bit architectures 🆙 Upgrade third-party SDKs to 64-bit compliant versions

Just released: Media3 1.10! Check out the latest feature enhancements for playback and editing: 🛠️ New Material3-based playback widgets 📺 Expanded format support in ExoPlayer ⚡ Improved speed adjustments in Transformer Learn more → goo.gle/3PxgQZI

List operations meet navigation logic. 🤝 Nav3 allows you to navigate by simply adding items to a list backed by Compose state. It's a straightforward approach that gives you full control → goo.gle/46zyLo1

Have you tried desktop mode yet? 📱➡️💻 Connected display support has reached general availability with the release of Android 16 QPR3. Connect a compatible device to an external display via USB-C, and you'll get a desktop-like multitasking experience → goo.gle/46AJ4bz

Supercharge your Android development 💪🏾

Interesting 👌

👨‍🍳 Master deep links with these Navigation 3 recipes → goo.gle/nav3-recipes This repository provides specific recipes for common navigation use cases, where each recipe introduces a single concept to keep implementations clean. Get cooking! 🍳

If you need to persist identity of a component that changes place, that can be achieved with movableContentOf. It allows using the same composable objects as children of different parents. That is especially useful when we define adaptive layouts.

🛠️ Swift Package Manager support is now available in Kotlin Multiplatform. Try importing iOS dependencies from Swift packages or migrating from CocoaPods. See how to try out this experimental feature ➡️ kotl.in/kmp-swiftpm-im… Share your feedback ⬇️🧵

Destructuring has been a popular feature in Kotlin, but since it's been based on position, it comes with some risks. But with Kotlin 2.3.20, you can eliminate many of those risks! Here's what I mean... Since destructuring is based on position, the order of your variables needs to match the order of the components (such as the data class constructor properties). If you accidentally swap around a few of them, you could end up with some surprises, and it's easy to do, especially when several of the components have the same type! But with Kotlin 2.3.20, you can now enable an experimental feature to use name-based destructuring instead! When activated in "complete" mode, the syntax we've been using up until now will match based on name rather than position. This means you can get them out of order, and it still works. If you use a name that doesn't match, you'll get a compiler error. But for those cases where you actually wanted a different name, you can use a new syntax to assign the component to a different name: val (title, cost = price, author) = book Prefer to use the classic, position-based destructuring? You can use brackets instead of parentheses, like this: val [author, cost, title] = book The bracket syntax brings along some connotations of collections, which seems fitting, since position-based destructuring could still be helpful for things like Pair and List. It's still experimental, and there's a full migration path planned out, but you can activate it today with a compiler argument. What do you think about this feature Do you like the new syntax? Have you run into issues with position-based destructuring in the past? #Kotlin #AndroidDev

There is no other feature that shaped so strongly what Kotlin looks like today! Extension functions, one of the most beloved Kotlin features, turned out to be likely the most influential one. Let me explain briefly 👇🧵

Dex thinks you should try out the new features in Android Studio Panda 2. And you don't want to disappoint Dex, do you? 😉 Download the newest version to see what's new → goo.gle/412Bd3a

Whewwwww we're sooooo smmmmaaaallllllllll in the Grand Scale of thinggggggssss!