About TechX
An independent Apple publication that measures instead of reports. One person, one machine, and a rule that nothing gets published unless we ran it.
What this site is
TechX covers the same subject as the large Apple sites and uses the opposite method. There are no rumours here, no supply-chain reports, no leaks, no coverage of unreleased hardware, and no news feed. What there is instead is a set of articles built around numbers produced on hardware we physically have, with the conditions and the run counts published next to the result.
The reason for that choice is straightforward. An announcement gets covered by two hundred sites within an hour of it happening, and the two hundred and first version adds nothing. A measurement that nobody bothered to take is still missing weeks later. This site aims at the second category, which is slower to produce and considerably more useful once it exists.
Who writes it
Teja Pagidimarri writes everything here. 11+ years in content marketing and SEO, based in Hyderabad, India. That background is in content and search rather than in systems engineering, which shapes what this site is good at and what it is not.
What it means in practice: the questions asked here tend to be the ones people actually type into a search box, and the answers are structured so the answer arrives before the explanation. It also means the work leans on published, reproducible commands rather than on privileged access or specialist instrumentation. Every measurement in every article can be re-run by a reader on their own machine using tools that ship with macOS, and the exact commands are printed in the article so they can be pasted.
There is one byline on this site and it is on every article. If something here is wrong, there is exactly one person to correct it.
What we measure on
One MacBook Pro with an Apple M4 Pro, 24 GB unified memory, running macOS 26.3.1 (25D771280a). That is the whole rig at present, and it is described in detail with its limitations on the how we test page. One machine is a genuine constraint. It means coverage is narrow, it means every article here is about the Mac rather than the wider Apple range, and it means we decline topics regularly because we cannot run them. We would rather publish less than publish an estimate dressed up as a result. As devices are added to the rig they will appear on that page before any article relies on them.
How the sections work
Concepts explains one mechanism at a time, carried by a diagram we drew, with a reading from the machine to show the explanation holds. Guides walks a complete task and reports how long it actually took, including the steps where the official instructions turned out to be wrong. Fixes documents a single failure with its exact error text and what resolved it. Teardowns takes a claim apart, reproduces the conditions that would make it true, then runs the same test under the conditions people actually live in, and publishes both numbers.
What this site will not do
- Publish rumours, leaks, or anything about hardware that has not shipped.
- Present a number we did not measure as though we measured it.
- Use a screenshot or a diagram we did not make.
- Review a device we do not own.
- Run a story because it is moving quickly.
Independence
TechX is not affiliated with Apple Inc., not endorsed by it, and has no relationship with it. No hardware on the test rig was supplied by a manufacturer. Nothing here is sponsored, and no article has been paid for or reviewed by a third party before publication. If that ever changes, it will be disclosed on the article itself and not solely in a policy page. The full position is in the editorial policy and the disclaimer.
Getting in touch
Corrections are the most useful thing you can send. If a number here does not reproduce on your machine, that is worth knowing and it will be checked. The contact page has the address and describes what happens to what you send.
How to read a measurement here
Every figure on this site carries three things next to it: what was measured, how it was obtained, and how many times it was run. That last one matters more than it looks. A single reading of something like battery capacity or network latency moves with temperature, with what else is running, and with when you happened to look. Where a number here is described as measured, it was taken more than once and the article says how many times. Where a value can only be observed once, such as a build number or a cycle count, it is described as an observation instead.
Where readings varied between runs, the spread is published beside the mean rather than averaged into something tidier. A figure with a wide spread is itself a finding, and smoothing it away would misrepresent how much confidence the result deserves. Several articles here exist specifically because a number turned out to be far less stable than the tools reporting it imply.
Everything is stamped with the exact operating system build rather than the marketing version. Apple changes behaviour in point releases, and a result that was accurate in one build can stop being accurate in the next. When something is re-tested, the stamp and the numbers change together and the change is noted on the article.