Book Dragon Support

Something is not working, something is confusing, or you found a place where Book Dragon is doing something it probably should not be doing. That is what this page is for.  Before sending a message, it may be worth checking the FAQ, Known Issues, or User Guide once those sections are available. If the problem is new, strange, difficult to explain, or simply easier to show us than to diagnose yourself, use the form below and send it along.

The more useful detail you can give us, the easier it is to understand what happened. You do not need to write a technical report or know the right terminology. Tell us what you were trying to do, what you expected to happen, what happened instead, and anything else that seemed unusual. If the issue only happens with one particular book, edition, shared collection, or device, include that too.

What to include

For most support requests, the form should collect enough information to reproduce the problem without asking users to guess at technical details they do not know. I would include the following fields:

Name Optional. Some people would rather just send the problem.

Email address Required if they want a reply.

Subject Required. A short description of the issue.

What do you need help with? A dropdown can make routing easier. Suggested options:

• Adding or editing books
• Scanning or book lookup
• Editions or copies
• Collections
• Shared collections
• Syncing
• Search or filtering
• Series
• App crash or freeze
• Accessibility
• Incorrect book information
• Feature question
• Feature suggestion
• Something else

Tell us what happened Required. This should be the main message field.

What were you trying to do? Optional, but useful when the problem is hard to understand from the description alone.

What did you expect to happen? Optional.

What happened instead? Optional.

Those last three could also be combined into one larger message field if you want the form to stay shorter. I would probably do that at launch and use helper text inside the field rather than making people fill out several boxes.

Device information

A few technical details can save several rounds of email when the problem depends on a particular device or software version. I would include:

Book Dragon version Preferably filled automatically if the form is opened from inside the app. If the form is only on the website, make it optional.

Apple device For example, iPhone 17, iPad Air, or whatever the user knows. Optional.

iOS or iPadOS version Optional.

Does the problem happen every time? Suggested choices:

• Every time
• Sometimes
• Happened once
• I am not sure

Is this related to a shared collection? Yes / No / Not sure

That last field is especially useful because shared-library problems may involve Apple synchronization rather than the local Book Dragon interface.

Screenshots

Allow users to attach screenshots if practical.

A screenshot can explain in seconds what might take several paragraphs to describe, especially for layout problems, incorrect metadata, duplicate editions, missing covers, or unexpected results. I would allow common image formats and keep the attachment optional.

I would also add a short reminder:

Before attaching a screenshot, check whether it contains anything you would rather not send us, including personal information or book collections you do not want included in the support request.

We should not encourage people to send their entire collection database or diagnostic files unless we later build a specific export designed for support.

Book lookup problems

If someone is reporting incorrect or missing book information, the form could reveal a few additional fields:

ISBN If available.

Book title

Author

What information is wrong or missing?

This will become particularly useful as we build the Archive Nine metadata layer because support reports can help identify bad records without requiring access to anyone's collection.

What happens after you send the form

Your message is sent to Archive Nine so we can review the problem and reply to the email address you provide. Information submitted through the support form is separate from your Book Dragon collection. Sending a support request does not give Archive Nine access to the library stored in the app unless you choose to include information from it in your message or attachment.

We may ask for more information if the problem cannot be reproduced from what you send. We may also use reports to identify bugs, improve documentation, or decide which parts of Book Dragon need attention, but support messages are not an excuse to quietly turn your correspondence into an analytics system.

If several people report the same problem, it may eventually appear on the Known Issues page so other users do not have to wonder whether they are the only person seeing it.

Feature ideas are welcome too

Support does not have to begin with something being broken. If Book Dragon almost does what you need and one small change would make the difference, tell us.

We cannot promise that every suggestion will become a feature, and sometimes an idea that sounds simple from the outside turns out to involve considerably more than one button. Still, Book Dragon is being built for people who live with books, and people who actually use the app will eventually notice things we did not.

That is useful information.

Send us a message

[Support Form]

If Book Dragon is doing something strange, tell us what you saw. If it is doing something annoying, tell us that too. There is a decent chance somebody else will eventually run into the same thing, and fixing it once is considerably better than making everyone discover it independently.