Telegram RegisterThe public register of Telegram
Telegram profile photo for iOS engineer

Channel

iOS engineer

@ios_engineer

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

37subscribers

-2 since we began measuring on 14 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001370294566
TypeChannel
Username@ios_engineer
CreatedBetween 1 April 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live2 October 2026
Measurements held4
Confirmed unchanged1 time, most recently 2 October 2026
On Telegramt.me/ios_engineer

Topic

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 2 October 2026 and assigned it the closest of 31 fixed categories, at 77% 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

37393814 August 2026 — 39 subscribers14 August 2026 — 39 subscribers23 August 2026 — 38 subscribers2 October 2026 — 37 subscribers14 August 20262 October 2026
4 measurements spanning 49 days, net -2. 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 37–39 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
2 Oct 2026, 12:2037-1
23 Aug 2026, 07:0638-1
14 Aug 2026, 08:3139no change
14 Aug 2026, 08:1839first reading

Engagement

20 posts held, back to 9 December 2023 — 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 20 posts for this entry, the most recent from 2 April 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 6 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍450.0%
🔥225.0%
❤112.5%
🤩112.5%

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 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 8 reactions 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 9 December 2023 to 2 April 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.

Recent posts

22 Dec 2025, 11:49 UTC244 views1 reactionsread 14 August 2026

https://essentialdeveloper.com/book-suggestions/

🔥1

21 Dec 2025, 13:38 UTC198 viewsread 14 August 2026

What to do when you find hidden requirements while coding Once you’ve accepted and started working on an assignment, you may find missing/hidden requirements. You should be fine as long as you follow a process to manage the hidden complications accordingly. If the newly found work is doable within the agreed deadline, notify your team, document the newly found requirements within the current task to make it visible…

19 Dec 2025, 09:54 UTC175 viewsread 14 August 2026

https://almostengineer.medium.com/ios-ci-cd-workflow-with-github-actions-tests-deployment-to-appstore-codeclimate-integration-6f2954015e39 Source Code

16 Dec 2025, 18:16 UTC152 viewsread 14 August 2026

Demystify SwiftUI Peek behind the curtain into the core tenets of SwiftUI philosophy: Identity, Lifetime, and Dependencies. Find out about common patterns, learn the principles that drive the framework, and discover how you can use them to guarantee correctness and performance for your app. Source

19 Aug 2024, 13:12 UTC519 viewsread 14 August 2026

A Swift DSL for navigation in iOS and tvOS apps with a simplified, chainable, and compile time safe syntax https://github.com/hhru/Nivelir

6 Aug 2024, 06:56 UTC481 views1 reactionsread 14 August 2026

https://useyourloaf.com/blog/add-resources-to-swift-packages/

👍1

18 Jul 2024, 16:26 UTC427 views1 reactionsread 14 August 2026

#interview DispatchQueue(QoS: background) bo'lsa qaysi vaziyatda ishlamiydi. Javob: Low power mode`da

👍1

18 Jul 2024, 12:56 UTC383 viewsread 14 August 2026

#interview 1. CALayer vs UIView 2. Animate border. using UIView.animate possible? 3. Multithreading issues? Deadlock, Race Condition, Priority inversion, Data race, Starvation, LiveLock

17 May 2024, 18:26 UTC406 viewsread 14 August 2026

Andersen Lab Knowledge matrix https://people.andersenlab.com/knowledge-matrix

Showing the 12 most recent of 20 posts we hold for @ios_engineer. 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.

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 2 October 2026 — this entry's latest reading, not the date you are reading this.

“iOS engineer” (@ios_engineer), 37 subscribers as measured 2 October 2026. Telegram Register, tgregister.com/channel/ios_engineer.

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.