Company
Performance work is mostly a measurement problem.
IOPEX TECHNOLOGIES PTY LTD works on frame pacing, thermal behaviour and battery in mobile games, on the low-end Android hardware most players actually use. What follows is the argument driving that work, the pipeline every number comes out of, and who we are not.
Name collision. iOPEX Technologies, Inc. is a separate and considerably older business working in enterprise IT and business process services. It shares no owner, no staff and no system with this company.
The overlap is in the spelling and nowhere else. This entity is registered in Australia under ACN 696 561 609, works on mobile game performance, and has never traded in enterprise IT services. Neither business speaks for the other or answers for what the other does.
The argument
Almost every published mobile performance number is measured wrong.
Not dishonestly. Measured in a way that happens to flatter, because the easy measurement and the useful measurement diverge and nobody has a reason to take the harder one.
The easy one is an average frame rate on a fresh, cool, recent device over a short run. The useful one is a distribution taken on an old device that has been playing long enough to get hot. The first is a number you can put in a store listing. The second is what someone holding the phone will feel.
Once you take the second one seriously, the work changes. It stops being about making the fast path faster and becomes about finding the rare slow path: the garbage collection pause, the shader compiled on first use, the texture upload that blocks, the allocation that triggers reclaim on a device with no headroom. Those are the frames people notice, and they are invisible to an average.
Why low-end Android specifically
Because it is where the gap between the two measurements is widest, and because it is where most installs come from in most markets. A game that runs well on a four year old midrange handset runs well everywhere. The reverse is not true, and working the other way round is how a title ends up with good reviews in one country and one-star reviews in five others.
Pipeline
Four pieces, and every number comes out of them.
Each one is made to be re-run rather than quoted. A measurement you cannot reproduce next month is an anecdote with a decimal point in it.
| Piece | What it does | Why it is made that way |
|---|---|---|
| Capture harness | Records per-frame presentation timestamps and thermal state on the handset itself, then exports the raw series | The whole series is kept, not a summary of it, so a run captured today can be re-read against a question nobody had thought to ask yet |
| Scripted session runner | Replays one fixed 20 minute input sequence identically on every device and every build | Two captures then differ by the hardware and the code, and not by how somebody happened to play that afternoon |
| Device set | Older Android handsets, each held at a recorded cycle count and state of health | A battery figure means nothing without the age of the battery it came off. Small on purpose, and named rather than implied |
| Own titles | Built to the methods above and measured with the harness and the runner listed here | The instrumentation is pointed at our own work first. Anything we would not run against ourselves does not go on this page |
Register
The verifiable part.
- Legal name
- IOPEX TECHNOLOGIES PTY LTD
- Entity type
- Proprietary company limited by shares, registered in Australia
- ACN
- 696 561 609
- ABN
- 54 696 561 609
- ABN status
- Active from 25 March 2026
- GST
- Registered from 25 March 2026
- State
- Victoria
- Where to check it
- ASIC holds the ACN record. The ABN, the GST registration and the current status of both are searchable at no cost on abr.business.gov.au, no account required
- Service of documents
- ASIC holds the registered office against ACN 696 561 609, and that is the address carrying legal effect. A second address published on this page would carry none, so none is published
Send us a trace
Send one gameplay trace — engineering@iopex.co.im reads it.
One capture off the oldest handset you care about, with the device model and the operating system build in the mail. An engineer reads it and answers inside five business days with where the tail sits and what to instrument next. An argument with the methods above reaches the same inbox and gets the same clock.