Frequently Asked Questions
Last updated: August 17, 2026
The app won't load, even though my internet is working
The usual cause is a network that blocks one or more of the addresses the app needs. This comes up most often on school, workplace and government devices, where a content filter or firewall sits between the device and the internet. Web browsing still works, so the internet looks fine — but the app can't reach the servers it downloads the dictionary from, and gets stuck on the launch screen.
The app keeps its own copy of the dictionary on your device so it can work offline. It only needs to download that copy when it doesn't already have one: the first time you ever open the app, and occasionally after an update that changes the format of the stored copy. That is why a device can run happily for months and then suddenly stop working after an update — the block was always there, but until then the app had a local copy and never needed to go and fetch one.
Some things to try:
- Open the app once on a different connection. A home wi-fi network or a personal phone hotspot is ideal. Once the dictionary has downloaded, it's stored on the device, and the app should work on the restricted network again afterwards.
- Wait for the error screen. Current versions of the app show a download progress screen on first launch, and if the download can't get through they give up within a minute or two and show an error screen with a Try again button and more help. If you're on an older version the app may instead sit frozen on its logo for a few minutes before an error appears — updating the app fixes that.
- If your network uses a proxy, as many managed networks do, turn on Use system HTTP proxy and try again. On current versions the switch is right on the error screen and takes effect when you press Try again; it's also in Settings → Network inside the app, where changing it needs an app restart. The app doesn't use the device's proxy settings unless you ask it to.
- Ask whoever manages the network to allow the addresses below. This is the real fix on a managed device. The list is written so you can forward it straight to an IT department.
Which domains does the app need to reach?
If you administer a network or a fleet of managed devices, these are the domains Auslan Dictionary connects to, all over HTTPS on port 443. The first group is required for the app to start at all.
Required for the app to start
raw.githubusercontent.com |
Where the dictionary data is downloaded from |
|---|---|
cdn.auslandictionary.org |
Backup copy of the same data |
Required to play the sign videos
object-store.rc.nectar.org.au |
The video files themselves, hosted by Auslan Signbank |
|---|---|
cdn.auslandictionary.org |
Backup video host (same as above) |
Optional — the app works without these
api.auslandictionary.org |
Signing in and shared word lists |
|---|---|
share.auslandictionary.org |
Opening a shared list link someone sends you |
analytics.auslandictionary.org |
Anonymous usage statistics (see the Privacy Policy) |
www.auslan.org.au |
The "view on Signbank" links, which open in a browser |
In practice raw.githubusercontent.com is the one most often blocked, since filters tend to treat all of GitHub as a code-sharing site.
Does the app work offline?
Mostly, yes. Once the dictionary has downloaded, searching and browsing work with no internet connection at all.
The sign videos are streamed, so playing a sign you haven't watched before does need a connection. Videos you have watched recently are kept on the device for 21 days, so revisiting a sign usually works offline too. You can turn this caching off, or clear it, in Settings.
Is the app free?
Yes — completely free, with no ads, no subscriptions and no in-app purchases. It's also open source; the code is on GitHub.
Where do the signs come from?
All of the sign information and video in the app comes from Auslan Signbank (Johnston, T., & Cassidy, S. (2008). Auslan Signbank, Sydney: Macquarie University & Trevor Johnston). The app is an alternative way to browse and revise their dictionary; it isn't a separate source of Auslan. New and updated signs published to Signbank flow through to the app automatically.
A sign is missing, or looks wrong
Because the content comes from Auslan Signbank, corrections need to go to them rather than to us — that way the fix reaches everyone who uses Signbank, not just app users. Use the Signbank feedback form. The same applies to a definition that seems inaccurate, or a sign that's missing entirely.
A video that won't play for a specific sign is usually a problem with the source media as well, though if lots of videos are failing it's worth reporting to us too.
Something else is broken. How do I report it?
For anything that's a problem with the app itself — a feature that doesn't work, a crash, something that looks wrong — either open an issue on GitHub or email [email protected].
Two things make a report much easier to act on: a screenshot of what you're seeing, and the app's background logs (Settings → Background logs), which record what the app was doing at the time. Mentioning your device and whether you're on a home, school or work network helps too.