Talk to the people who wrote the code.
There's no support desk and no ticket queue. Messages go straight to the studio, and the person who reads yours is the person who can fix it.
Anything, honestly
It all goes to the same address. These just help us reply usefully.
-
Something's broken
The most useful thing you can send. See below for what to include — it turns a guess into a fix.
-
Something's missing
A plant the app doesn't know yet, a setting you keep wishing for. Tell us what you were trying to do.
-
Everything else
Press, partnerships, or telling us the studio name is ridiculous. All read, all welcome.
What to include
None of this is required — send what you have. But a report with these four things in it usually gets fixed in one go, instead of three emails of us asking which phone you're on.
A crash report tells us something broke, but rarely why. What you write is usually what turns it into a fix.
-
Which app, and which phone
Which app, and whether you're on an iPhone or an Android phone — plus which version, if you know it.
-
What you were doing
The steps before it went wrong, even the boring ones.
-
What you expected instead
Sometimes the bug is that the app is working as designed and the design is wrong.
-
A screenshot, if you have one
Worth a page of description, especially for anything about layout.
Two things we get asked a lot
-
"Can you see my collection?"
No — what you add stays on your phone, and there's no account and no copy kept anywhere else. The apps do send crash reports and basic usage figures, so we can see when something has broken or which screens people open. More on the about page.
-
"How long until you reply?"
We're a small studio, so it depends on what else is on. We read everything. If something is badly broken, say so in the subject line and it goes to the top.