4 measurements spanning 14 days, net -6. 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 506–514 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)
Subscribers
Change
21 Aug 2026, 23:46
507
-2
14 Aug 2026, 22:48
509
-4
8 Aug 2026, 04:04
513
no change
7 Aug 2026, 23:12
513
first reading
Engagement
20 posts held, back to 21 July 2022 — 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 pageof 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 20 posts for this entry, the most recent from 7 August 2023. An engagement rate over an empty window would be a number about nothing.
Reaction mix
33 reactions across 11 posts, in 6 distinct kinds. The most used accounts for 60.6% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
👍
20
60.6%
❤
4
12.1%
🥰
3
9.09%
🎉
2
6.06%
👎
2
6.06%
🔥
2
6.06%
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 20 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 33reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 21 July 2022 to 7 August 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.
Generating Images using Stable Diffusion natively on iPhone, 100% offline and free using Expo & React Native! 🎉
I just published the expo-stable-diffusion module that I have been working on for the last few weeks! 👇
https://github.com/andrei-zgirvaci/expo-stable-diffusion
In case you want to dive deeper into this topic, you can read my in-depth guide on "How to Create AI-Generated Images on iOS in React Native Usi…
…
However, these features are only supported in iOS 17 and macOS 14, so we'll have to wait a few more months for those performance optimizations to be available to most Apple users...
I will write a short article on how I managed to write this library using Expo Modules API and also how to use it, probably next week...
If it sounds like something you would be interested in, you can bookmark my blog website and giv…
WIP: Generating Images using Stable Diffusion natively (Core ML) on iPhone 13 mini using Expo & React Native!
I am currently working on creating an Expo library using the new Expo Modules API which will allow me to run Stable Diffusion models on an iOS device!
Thanks to the Expo team, building native libraries using the Expo Modules API is easier than ever!
I am currently working on creating the API layer between …
Why I am not posting about React Native anymore!
Hey guys, I wanted to give you a quick update on this channel as you probably noticed that I am not posting here as often as before anymore…
This is due to me now not working with React Native as much as I am more focused on Next.js and React.js projects.
Now the question is, would you want me to also post Web Developement updates like: React.js, Next.js, Databases,…
Hey guys, thank you for all the love I received on my previous post! 🙏
Since then, I created a weekly Newsletter tailored for Software Developers seeking to reduce their stress and overcome anxiety in the workplace.
You can check it out below if you are currently struggling with stress and anxiety, I am sure you will find it helpful!👇
Next issue coming into your inbox this Sunday!
https://newsletter.andreizgirvac…
Hey guys, this is a little bit offtopic, but I thought I might share my story dealing with Anxiety as a Software Developer and how I managed to overcome it.
I know that I'm not alone in my struggles, and I've heard many other developers share similar stories of burnout, imposter syndrome, and perfectionism.
That's why I want to share with you my story in hopes that it helps other Developers who are struggling with …
Today, Expo is reimagining native routing!
✨ Automatically create (dynamic) routes with files
🚀 Zero boilerplate
🔗 Automatic deep linking
🧩 Nested layouts
🔥 Built on React Navigation for easy adoption.
Try the expo router beta now!
https://blog.expo.dev/rfc-file-system-based-routing-in-react-native-7a35474722a
Expo SDK 46 Has Arrived! 🎉
For anyone who missed this release, this is a quick summary of the main changes in this release!
🎨 Skia and FlashList in Expo Go
⚛️ React 18 and React Native 0.69.3
💨 Fast local CLI is now default
✍️ VSCode Expo adds IntelliSense for eas.json
💔 Final SDK to support classic builds
Read full release article below! 👇
https://blog.expo.dev/expo-sdk-46-c2a1655f63f7
File system-based routing coming to React Native! 🏗️
File system-based routing similar to Remix/Next-esque layouts and nested routes is finally coming to React Native!
If you build with RN, and you're frustrated with navigation, check this out! 👇
https://twitter.com/Baconbrix/status/1560353229241831425
@Baconbrix on Twitter: 😲👏
"⅔ of this goes away with the upcoming @expo router API, the other ⅓ is added conditionally when needed."
Less boilerplate, fewer app-wide re-renders."
🔗 https://twitter.com/Baconbrix/status/1571598878310375424
💬 Anyone else here has this "Provider's Hell" problem? 🤔
Showing the 12 most recent of 20 posts we hold for @React_Native_Status. 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.
Polls
The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.
Shares as published. No per-option vote count is published by Telegram, so none is shown.
Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.
The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.
Read from the 20 most recent posts we hold, published 21 July 2022 to 7 August 2023. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.
Handles this channel named that no longer answer
Dead references
1
handles named in this channel’s posts, vacant today
Evidenced gone
0
we ourselves saw one of these resolve, at some point
Never seen alive
1
vacant every time we have ever looked
@React_Native_Status named 1 handle that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@baconbrix named in 1 post, 9 August 2026 – 9 August 2026
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 21 August 2026 — this
entry's latest reading, not the date you are reading this.
“React Native Status” (@React_Native_Status), 507 subscribers as measured 21 August 2026. Telegram Register, tgregister.com/channel/React_Native_Status.
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.