Channel
@mobilehubvk
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
727subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003242611174 |
|---|---|
| Type | Channel |
| Username | @mobilehubvk |
| Created | Between 1 October 2025 and 31 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/mobilehubvk |
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 20 September 2026 and assigned it the closest of 31 fixed categories, at 100% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 14 Sept 2026, 15:01 | 727 | -1 |
| 7 Sept 2026, 09:41 | 728 | -6 |
| 28 Aug 2026, 14:57 | 734 | -2 |
| 22 Aug 2026, 03:54 | 736 | -1 |
| 8 Aug 2026, 07:01 | 737 | +3 |
| 8 Aug 2026, 02:04 | 734 | no change |
| 7 Aug 2026, 17:38 | 734 | first reading |
7 posts held, back to 16 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 7 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.
67 reactions across 7 posts, in 7 distinct kinds. The most used accounts for 31.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 21 | 31.3% | |
| ❤ | 17 | 25.4% | |
| 🔥 | 17 | 25.4% | |
| 👏 | 5 | 7.46% | |
| ✍ | 3 | 4.48% | |
| 🤮 | 3 | 4.48% | |
| 🤡 | 1 | 1.49% |
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 7 of the 7 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 67 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 16 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
Compose Layout API Row, Column и Box закрывают почти всё, пока не появляется макет, который в них не ложится: чипы со своими правилами переноса, футер, которому нужна высота хедера, колонки одной ширины по самому длинному тексту. Под тремя контейнерами лежит обычный публичный API: measure-политика, Constraints в целых пикселях и вторая фаза измерения для анимаций. В карточках рассмотрим шесть его кусков в порядке о…
👍2🔥2❤1
Июль в мобилке был про то, как обе платформы готовятся к финальным осенним релизам. Compose дошёл до rc 1.12, а самому фреймворку исполнилось 5 лет — Google в юбилейном посте пошёл дальше поздравлений и формально закрепил Compose-first, отправив View toolkit в maintenance mode. На iOS параллельно обкатывается версия 27 через беты со свежим Siri. 🟣Compose 1.12.0-rc01 29 июля вышел Compose 1.12.0-rc01. Release Candid…
❤2👍1
OkHttp interceptors — где какой ставить и когда нужен EventListener Interceptor в OkHttp — способ вмешаться в запрос между вызовом и ответом. Через них добавляют заголовки, логируют, ретраят, кешируют. Interceptor можно поставить в двух местах — Application и Network, и они ведут себя по-разному. Плюс есть EventListener для метрик, который путают с interceptor. Разберём, где что. OkHttpClient имеет два списка inter…
🔥4❤3👍3
Kotlin inline и reified — зачем это вообще нужно Про inline-функции в Kotlin многие знают только то, что «они быстрее» и стоят в стандартной библиотеке рядом с map и filter. На самом деле inline — это не про производительность в чистом виде, а про то, что можно сделать невозможное в обычных функциях: reified generics, non-local return из лямбд и полноценные DSL без runtime-оверхеда. Разберём по порядку. Базовое пов…
❤5👍3🔥3👏1
Анимации в Jetpack Compose — шесть инструментов на разные случаи В Compose анимаций много, и легко запутаться, что где применять. В карточках разберёмся с шестью основными, которые закрывают почти всё: 🟣 animate*AsState для одного значения 🟣 updateTransition для связанных 🟣 AnimatedVisibility для появления и исчезновения 🟣 AnimatedContent для смены контента 🟣 Crossfade для плавной замены 🟣 InfiniteTransition для по…
👍4✍3❤2👏1🔥1
Как ускорить старт приложения на 25–40% без переписывания кода Baseline Profiles — это метаданные, которые сообщают ART, какие классы и методы нужно AOT-скомпилировать заранее, ещё до первого запуска. Обычно ART компилирует «горячий» код JIT-ом уже во время работы приложения, и на холодном старте это добавляет секунды. Baseline Profiles сдвигают компиляцию с устройства пользователя на этап сборки. Как работает При…
👍4❤3🔥3🤡1
Как VK переезжали с XML на Jetpack Compose: базовые классы и паттерны В большом Android-проекте VK с сотнями экранов долго жила классика — XML-вёрстка, Dagger 2, Cicerone для навигации, MVVM. С ростом кодовой базы связка начала подводить: разрозненные MutableStateFlow для каждого поля состояния давали моргания интерфейса (isLoading уже false, а items ещё пустой), фрагменты обрастали обвязкой на 200 строк, ревью экра…
👍4🔥4👏3🤮3❤1
Showing the 7 most recent of 7 posts we hold for @mobilehubvk. 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.
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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Mobile VK Hub” (@mobilehubvk), 727 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/mobilehubvk.
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.