Aussie Gamefront · Behind the guide
Meet the editorial team
Useful comparisons start with clear questions. What can you play, how easily can you find it, and what should you check before choosing a platform? Our editorial roles bring research, readable explanations and everyday browsing needs into the same conversation.
We write for Australian readers exploring online gaming platforms. The people and biographies below are authored team profiles describing how Aussie Gamefront divides its editorial work; they do not represent independently verified professional credentials.
People behind the comparisons
Three complementary roles help turn a collection of platform details into a guide readers can actually use. Each brings a different question to the review.
Editorial lead
Maya Collins
Maya organises platform coverage, checks clarity and coordinates corrections. Her interest in strategy games shapes a patient approach: explain the choices, identify the trade-offs and give readers enough context to decide for themselves.
She reviews introductions, comparison wording and disclosures before publication. When a description sounds more certain than the evidence allows, Maya narrows the claim. She also keeps terminology consistent, so a feature described in one guide means the same thing elsewhere on the site.
Platform researcher
Ben Hartley
Ben compares public game information, content categories and discovery tools. He looks at how a platform describes its catalogue, how games are grouped and whether a reader can follow a useful path from an overview to a specific title.
Documenting limitations is central to his role. A public feature list does not establish performance on every device, and a catalogue can change. Ben records what the available material supports, flags conditions that matter and passes unresolved questions into the editorial review rather than filling gaps with assumptions.
Usability editor
Elise Nguyen
Elise reviews navigation, readable layouts and keyboard journeys. She brings mobile browsing needs into editorial discussions, including whether headings make sense on a small screen and whether the next useful action is easy to find.
Her reader tasks include moving through a comparison, finding an explanation and locating a contact route. She checks whether labels describe their destinations and whether instructions depend on a mouse. These practical checks inform our writing; they are not a claim that every game or platform has passed a comprehensive accessibility audit.
Research → reader tasks → review
How the team works together
Ben begins with public evidence and records the scope of each observation. Elise then checks the reader tasks behind the comparison. Maya reviews the wording and disclosures, making sure that observations, interpretation and limitations remain distinguishable. A useful handoff explains both the finding and the reason it matters.
Our comparison discussions use seven review areas: game selection, content categories, discovery tools, navigation, mobile readability, keyboard access and clarity of platform information. These areas keep the work focused on practical decisions. A strong catalogue, for example, is less useful if a reader cannot discover relevant games or understand the conditions attached to a feature.
We revisit material corrections when platform information changes or a reader identifies a problem. The team checks the affected wording and related comparisons, rather than treating a corrected sentence as an isolated task. Our guides do not imply comprehensive game testing, external accreditation or identical experiences across devices. Where evidence is limited, the explanation should be limited too.
