This page is an independent guide, not a support forum and not a contact route for any app. It contains no archived posts, profiles or personal data.
Record the facts first
Write down the device family, operating-system version, app version and approximate time. Then list the actions in order. “Import fails” is hard to diagnose; “a ten-row UTF-8 CSV stops after choosing the date column” gives a developer a place to begin.
A compact report
- Expected: what you thought the action would do.
- Observed: what appeared instead, including the exact error text.
- Steps: the shortest reliable route to reproduce it.
- Scope: whether it affects one book, one format or the whole library.
- Safety: whether any data seems missing or exposed.
Remove personal information
Crop screenshots to the relevant interface. Hide names, email addresses, profile images, private book notes, barcodes tied to purchases and notification previews. Never post an authentication code, recovery link or export file in a public thread.
Use the current official route
Find support from the product's present store listing or website rather than an old forum link. Apple explains how to contact an app developer, and Google provides guidance on contacting an Android app developer. For billing disputes or suspected fraud, use the store's official purchase-support route instead of a public review.
Separate bugs from feature requests
A bug report describes behaviour that conflicts with the interface or documentation. A feature request explains a need and a use case. Both are useful, but combining ten requests with one crash makes the urgent issue harder to isolate.
Keep a local copy of the report and any case number. If a problem risks data loss, stop repeating destructive steps and export or back up what remains before further testing.