Регулярная подборка актуальных статей по UX
Профессиональный гугл и крупнейшее UX СМИ в Рунете
В канале @uxdigest публикуются зарубежные статьи
Чат ограничен из-за засилья ботов, со всеми вопросами и комментариями сюда @lightmaker
7018117386
Created
4 December 2016 — measured — cross-checked against a third-party dataset (ext.tg_channel)
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 95% 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.
Growth
33 measurements spanning 43 days, net -152. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 21,457–21,655 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)
Subscribers
Change
17 Sept 2026, 19:36
21,480
-5
15 Sept 2026, 15:39
21,485
-9
13 Sept 2026, 21:41
21,494
-7
12 Sept 2026, 06:36
21,501
-3
9 Sept 2026, 22:39
21,504
-16
6 Sept 2026, 17:37
21,520
-11
4 Sept 2026, 06:40
21,531
-5
2 Sept 2026, 19:54
21,536
-9
1 Sept 2026, 20:54
21,545
-2
1 Sept 2026, 00:15
21,547
-3
30 Aug 2026, 00:34
21,550
-4
28 Aug 2026, 23:26
21,554
-7
27 Aug 2026, 23:47
21,561
-2
26 Aug 2026, 23:04
21,563
-2
25 Aug 2026, 23:58
21,565
-8
25 Aug 2026, 03:05
21,573
-2
23 Aug 2026, 20:27
21,575
-4
22 Aug 2026, 01:29
21,579
-1
20 Aug 2026, 18:23
21,580
-6
18 Aug 2026, 17:12
21,586
first reading
Engagement
40 posts held, back to 6 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 60 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
6.83%
avg views ÷ 21,480 subscribers
Avg views / post
1,470
18 posts measured
Reaction rate
0.503%
reactions ÷ views · ER floor
Posts in window
18
of 40 held
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
What these figures were computed from
Window
Rolling 30 days · latest post in window 27 September 2026
Posts held
40 (6 July 2026 – 27 September 2026)
Views total
26,423
Reactions total
133
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
27 Sept 2026, 17:09 UTC
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
What this channel posts
Photos
≈242
Videos
≈13
Links
≈2,540
Lifetime counters from Telegram’s own channel header, read 27 September 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Video runtime
22s
Average length
22s
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
321 reactions across 36 posts, in 10 distinct kinds. The most used accounts for 67.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
215
67.0%
🤝
39
12.1%
⚡
23
7.17%
✍
11
3.43%
🤓
7
2.18%
🕊
6
1.87%
🫡
6
1.87%
🎉
5
1.56%
🤩
5
1.56%
👀
4
1.25%
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 38 of the 40 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 336 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 40 most recent posts we hold, published 6 July 2026 to 27 September 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.
Telegram Stars
Stars received
6
across the posts below
Posts paid on
2
of 40 we hold a reading for · 5%
Most on one post
5
single highest reading
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @uxhorn. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 40 most recent posts we hold for this entry, published 6 July 2026 to 27 September 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
Advertising
Ad load
2.50%
1 of 40 posts carry an ad marker
Regulatory tokens
1
posts carrying an erid · 1 distinct token
Median views · ads
1,350
over 1 measured post
Median views · rest
1,870
over 39 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
CQH36pWzJqEgzwpVptJf4orEDwHfXyiJsqNrG6Lew3AHUC
1
15 September 2026
15 September 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 40 most recent posts we hold, published 6 July 2026 to 27 September 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
#мероприятие
29 сентября (среда) с 17:30 (Москва) пройдёт оффлайн Ночной UX — цифровая вечеринка от Сбера
Необычные решения, творчество и ошибки делают нас уникальными в мире ИИ-слопа и сгенерированных картинок. Идём праздновать неидеальность на вечеринке 29 сентября!
Ребята подготовили 3 кейса от Купера, Cloud․ru и Сбера. Как команды сделали всё неправильно — и правильно!
🎉 А после — вечернее шоу с шутками, конк…
Почему вам приятно узнать, что вы лучше 92% людей. Подписался на канал автора, увлекательно
Социально-сравнительная обратная связь мотивирует сильнее, когда показывает результат относительно других, а не просто выдаёт сухую оценку. Но тот же приём легко превращается в манипуляцию, если выборка непрозрачна или убедительный график маскирует слабую методологию
Проектирование: Основы дизайна - руководство по визуальной …
#партнеры
Кто вошёл в шорт-лист ADCR Awards 2026?
ADCR Awards опубликовали шорт-лист 22-го сезона. Первый этап голосования позади, и теперь можно посмотреть, какие проекты жюри выделило в рекламе, дизайне и категориях для молодых авторов. Всего в списке 150 позиций, причём некоторые работы представлены сразу в нескольких номинациях
Изучайте шорт-лист по ссылке, находите проекты знакомых команд и присматривайтесь к…
Проектирование: Контрастные пятна в дизайне - как фокус управляет вниманием и смыслом
Контраст помогает выстроить визуальную иерархию и направить внимание пользователя на действительно важные элементы интерфейса. Но когда акцентов слишком много, они начинают конкурировать между собой и превращаются в визуальный шум
ИИ: Мы сняли три старых ограничения исследований
По следам разговора с Мишей Правдиным делюсь странице…
Фреймворк “Персоны”: хочу их выделить, но как?
Простой способ выделять персоны после исследования: раскладывать респондентов по осям с ключевыми параметрами поведения и мотивации. Такой подход помогает быстрее увидеть реальные группы, когда различия между пользователями неочевидны
Исследование: Результаты Mobile Web Banking Rank 2026 про мобильные веб-приложения банков для частных клиентов от команды Markswebb
Систе…
Первый выпуск второго сезона UX Horn Podcast — с Михаилом Правдиным, основателем и руководителем Cloud Research, экспертом по исследованиям
И второй сезон начинаем с AI. Не потому что теперь без него нельзя начать ни одну статью, презентацию или подкаст. Просто сегодня - да и, кажется, в ближайшем будущем - он будет постоянно всплывать и в разговорах, и в жизни
Лёгкой прогулки не получилось, зато получилось чертовс…
Где писать отчет по результатам исследований? Немного про выбор
PowerPoint, Miro, таблица или обычный документ — выбор зависит не от привычки исследователя, а от того, как команда будет использовать результаты. Например, Miro хорош для совместной работы, а презентация — когда выводы нужно именно защищать вслух
Проектирование: Зачем я добавил диван в калькулятор ремонта
Почему иногда пользователю важнее увидеть резул…
#мероприятие
Если вы всё ещё используете ИИ примерно по схеме «написал промпт → получил ответ → забыл», то вот хороший повод копнуть чуть глубже
На ResearchExpo в этом году будет отдельный трек GENERATOR — не про «послушать, как кто-то классно автоматизировался», а про сесть за ноутбук и собрать что-то своё
2 октября будет два AI-воркшопа:
10:00–14:00 — Игорь Волошин
ИИ в управлении research-проектами
Как собрат…
Взболтать, но не смешивать: зачем UX-исследователю навыки проектирования
Навыки проектирования помогают исследователю давать конкретнее рекомендации, быстрее собирать прототипы и лучше понимать дизайнеров. Но есть обратная сторона: тестируя собственное решение, легко начать защищать его вместо того, чтобы исследовать (свежий интересный ресурс с сайтами, по мере прочтения буду делиться статьями отсюда)
Дизайн: Как ос…
#мероприятие
17 сентября (уже в этот четверг) в 16:00 — «Разговоры с UX Feedback»
Тема: сколько на самом деле стоит искать респондентов среди своих же пользователей
Собирается невероятная компания:
⏺ Оксана Половинкина — UX-исследователь | Циан
⏺ Варвара Ленева — UX-исследователь | Hoff
⏺ Анастасия Диденко — руководитель аналитики UX | S7
⏺ Дарья Рогачева — UX-исследователь | T2
У каждой — свой продукт, своя ауд…
Как составить сценарий удалённого немодерируемого UX-исследования
Как связать цель исследования, исследовательские вопросы и путь участника, не превращая сценарий в инструкцию «нажмите сюда». Полезный приём: формулировать задания через цель пользователя, а после каждой правки обязательно повторять пилот
Мероприятие: 17 сентября (четверг) в 16:00 пройдёт Разговор про внутренний рекрут респондентов
С экспертами из Циа…
🌐 Ожидание VS реальность. Можем ли мы повысить качество рекрута? - Анастасия Черкашина. VKVideo
XVI международная Грушинская социологическая конференция. 26-27 марта 2026 года. Как будет меняться роль респондента социологических, маркетинговых исследований в будущем?
Проектирование: Почему лучше скрывать необязательные поля в форме для заполнения
Необязательные поля в формах не должны отвлекать: вместо подписи «(нео…
🔥5✍1
Showing the 12 most recent of 40 posts we hold for @uxhorn. 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.
Forward network
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.
Mentions
Named by 12 registered channels — 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.
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.
Channels Telegram recommends alongside this one
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 23 September 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
UX Notes @uxnotes · 23,715 Telegram ranks this channel #3 of 97 here — alongside 96 others — read 17 September 2026
Дайджест продуктового дизайна @pdigest · 49,453 Telegram ranks this channel #5 of 97 here — alongside 96 others — read 25 August 2026
Hard Client @hardclient · 22,892 Telegram ranks this channel #6 of 97 here — alongside 96 others — read 19 September 2026
UI/UX Designer @uxidesign · 20,725 Telegram ranks this channel #13 of 97 here — alongside 96 others — read 26 September 2026
Дизайнер, привет @jun_hi · 23,435 Telegram ranks this channel #15 of 96 here — alongside 95 others — read 18 September 2026
Книги для дизайнеров 📚 @dbooks · 63,360 Telegram ranks this channel #16 of 95 here — alongside 94 others — read 21 August 2026
Адовый UX @uxfromhell · 50,316 Telegram ranks this channel #36 of 95 here — alongside 94 others — read 25 August 2026
Игорь Кузнецов о темных паттернах @brainshare · 21,960 Telegram ranks this channel #39 of 93 here — alongside 92 others — read 22 September 2026
Оди @awdee · 33,522 Telegram ranks this channel #43 of 97 here — alongside 96 others — read 4 September 2026
Now How Channel @nowhow · 24,611 Telegram ranks this channel #53 of 98 here — alongside 97 others — read 15 September 2026
Дизайн-переводчик @design_translator · 20,919 Telegram ranks this channel #55 of 97 here — alongside 96 others — read 25 September 2026
UI_UX inspiration @uiux_design · 21,259 Telegram ranks this channel #55 of 97 here — alongside 96 others — read 24 September 2026
Designdealer @designdealer · 86,726 Telegram ranks this channel #55 of 93 here — alongside 92 others — read 17 August 2026
Figma Design @figmadesign · 105,902 Telegram ranks this channel #61 of 94 here — alongside 93 others — read 15 August 2026
Secret Design @secretd · 22,350 Telegram ranks this channel #70 of 95 here — alongside 94 others — read 21 September 2026
СПNЗЖУ DESIGN @thedesigner · 29,931 Telegram ranks this channel #72 of 92 here — alongside 91 others — read 7 September 2026
Вакансии дизайнерам @jun_hi_vacancies · 42,790 Telegram ranks this channel #75 of 97 here — alongside 96 others — read 29 August 2026
Job for Designers @fordesigner · 24,592 Telegram ranks this channel #76 of 94 here — alongside 93 others — read 15 September 2026
Easy Figma @easyfigma · 25,456 Telegram ranks this channel #85 of 93 here — alongside 92 others — read 14 September 2026
Kostya Gorsky’s Channel @desprod · 25,894 Telegram ranks this channel #85 of 97 here — alongside 96 others — read 13 September 2026
Веб дизайн в Figma @figmaweb · 40,843 Telegram ranks this channel #86 of 95 here — alongside 94 others — read 29 August 2026
This channel appears in 21 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
Cite this entry
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 17 September 2026 — this
entry's latest reading, not the date you are reading this.
“UX Horn 🌀” (@uxhorn), 21,480 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/uxhorn.
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.