https://android-developers.googleblog.com/2023/10/androidx-minsdkversion-19.html #jetpack #minsdk
👍12👌1

Channel
@AndroidResId
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,193subscribers
-8 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001035057990 |
|---|---|
| Type | Channel |
| Username | @AndroidResId |
| Created | Between 1 March 2016 and 31 May 2016— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/AndroidResId |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 14:34 | 6,193 | -1 |
| 9 Aug 2026, 04:11 | 6,194 | -7 |
| 6 Aug 2026, 03:21 | 6,201 | no change |
| 5 Aug 2026, 22:16 | 6,201 | first reading |
19 posts held, back to 17 September 2021 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 9 pagesof Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 19 posts for this entry, the most recent from 17 October 2023. An engagement rate over an empty window would be a number about nothing.
109 reactions across 12 posts, in 11 distinct kinds. The most used accounts for 32.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 35 | 32.1% | |
| 🔥 | 17 | 15.6% | |
| 🍾 | 16 | 14.7% | |
| ❤ | 10 | 9.17% | |
| 🤔 | 9 | 8.26% | |
| 😱 | 8 | 7.34% | |
| 👎 | 7 | 6.42% | |
| 🤓 | 4 | 3.67% | |
| 🎉 | 1 | 0.917% | |
| 👌 | 1 | 0.917% | |
| 😁 | 1 | 0.917% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 13 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 109reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 19 most recent posts we hold, published 17 September 2021 to 17 October 2023, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
https://android-developers.googleblog.com/2023/10/androidx-minsdkversion-19.html #jetpack #minsdk
👍12👌1
🥳
🍾16👎5🤔5🤓4❤2👍2
Android migrates away from C/C++ to Java/Kotlin/Rust In Android 12 we announced support for the Rust programming language in the Android platform as a memory-safe alternative to C/C++. Since then we’ve been scaling up our Rust experience and usage within the Android Open Source Project (AOSP). In Android 13, about 21% of all new native code (C/C++/Rust) is in Rust. https://security.googleblog.com/2022/12/memory-sa…
🔥17👍13😱8🤔4❤2👎2😁1
Kotlin Multiplatform Mobile in Beta now! https://blog.jetbrains.com/kotlin/2022/10/kmm-beta/ Guide video from JetBrains: https://youtu.be/2yd6rVJdICU #kmm
👍4
#compose #kaspresso #testing Kaspresso 1.4.0: Jetpack Compose support Latest 🔥 Jetpack Compose support [Early access] 🛠️ Bugs fixes
#proguard ProGuard Playground Beta Graduation ProGuard Playground allows you to check the effect of your ProGuard configuration in real time. With the release of Beta, new features were added: 👉 Naming your playground 👉 Support for Kotlin Metadata 👉 Integration with AppSweep (find and fix security issues in your Android app’s code and dependencies)
❤1
#android12 #androiddevsummit 12L and new Android APIs and tools for large screens Announced a preview of a special version of Android 12 for devices with large screens: tablets, foldable and Chrome OS - Android 12L (L - large as I understand it).In this version, the UI of the system for large devices has been updated, multitasking has been improved, new taskbar, etc. Android 12L will be release early 2022. Google …
👍2❤1🎉1
#compose Snapper is a library which brings snapping to the Compose scrolling layouts Snapper can be summarized as SnapHelper for LazyRow & LazyColumn, adding item snapping, maximum fling distance, snap position, and more
❤1
#kotlin #native #multithreading Kotlin Native. Multithreading with Coroutines Kotlin Multiplatform provides common way to implement the multithreading. It uses Kotlin, so we can use Coroutines for all our targets. In the article you will find how to do that
👍1
#compose Always provide a Modifier parameter Any composable you write which emits layout (even a simple Box), should have a modifier: Modifier parameter, which is then used in the layout. Why? More details in the article
Meet the new Kotlin mascot and help choose a name for it
👍1
#kapt #ksp Kotlin Symbol Processors (KSP) KSP becomes stable. JetBrains said that KSP better understands the syntax of Kotlin and does not need to take extra steps compare to KAPT. The main news is that KAPT switch into support mode. No features or improvements. New features will only be in KSP and other Kotlin compiler plugins. They didn't say anything about KSP support in IDE.
❤1
Showing the 12 most recent of 19 posts we hold for @AndroidResId. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
Citation-graph rank — 818,400 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 12 August 2026 — this entry's latest reading, not the date you are reading this.
“Android ResId” (@AndroidResId), 6,193 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/AndroidResId.
Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.