What the reviewer runs it on
A mid-range Android, a normal connection, and reduced motion switched on for one of the passes. Test that yourself first.
Reviewers open submissions on whatever they have, which in practice means a mid-range Android phone on a normal connection with a cold cache, and a desktop pass with reduced motion enabled. Almost every returned submission in this phase fails one of those two rather than failing on craft.
Do the same passes yourself before you submit: throttle the network and CPU in devtools, load with an empty cache, leave it running for five minutes to reach the throttled state, and switch reduced motion on at the operating system level rather than trusting a devtools toggle. Finding the problem yourself is a great deal faster than a round trip.
You should now be able to
- Test your own work under the conditions it will be judged in
- Find the failure that only appears on a cold load
Loading…