Librarius app support, feedback, and what's new

When something does not fit in Librarius, a bug, an idea, or an account question, the short path is not a social comment or a random message. Three places are built for that: in-app feedback, the web form, and the FAQ. Updates ship through the official stores. This article says what to use in each case and what is not a support channel.

Librarius is a free app for iOS and Android with no mandatory subscription. The public web is for browsing and, if you sign in, for product feedback too. Joining a club, posting, or chatting stays in the app. If you only want the big picture, start with What is Librarius.

Start with the FAQ. Short answers live there: what Librarius is, whether it is free, how to add a book, how to delete your account, what happens if you change phones, which platforms exist, and how to contact us. If your question is already answered, you skip a round trip. If not, pick the channel by message type.

1. A usage or account question: FAQ first.
2. An idea or app bug: feedback (app or web, signed in).
3. If you cannot open the app: web contact form or the email the FAQ lists.
4. The app refuses to open or asks for a new version: update from the official store.

The account section on the product page summarizes sign-in, language, privacy, and that suggestions go from the app. It does not replace the form: it only tells you it exists.

In the app, contact or feedback lets you send a suggestion or report an error. You choose the type, write the message, and optionally attach screenshots (up to five). Screenshots speed understanding when something looks wrong on a specific screen; they do not need to be perfect, just show the step that fails.

Describe what you expected, what happened, and which screen you were on. If you can, note the device and whether the bug repeats. Skip unnecessary personal data: no passwords, ID numbers, or screenshots with someone else's email. The message has a length cap; if you exceed it, trim before sending.

• Type: suggestion or error / bug.
• Text: whatever the form requires; concrete beats long.
• Screenshots: optional, especially useful for bugs.
• After sending, you get a receipt: the team reviews when it can. This is not live chat.

Product feedback is not reporting someone's profile or an urgent deletion request. To block or report content, use the options on that post or chat. To delete your account, use settings. Mixing three topics in one message delays all three.

The web form (/feedback)

Try it in the app

Create a free account

Free, no subscription

The same URL, contact / feedback, behaves differently signed in or out. Signed out, it is a contact form: name, email, and message to support. Signed in, it is product feedback: type, message, and screenshots, like the app.

Use the signed-out version when you cannot open the app (lost access to login email, device will not launch Librarius). Include the account email and what you need. Use signed-in when you want to propose a change or attach a bug screenshot. The FAQ also links this form and an email; you do not need to write to both at once.

Response time is not a contract: the FAQ says it is usually brief. A send receipt is not a fix. If the topic is serious (security, harassment, data), say so in the first line and share the minimum needed; do not publish details in a club or on social media.

New Librarius versions publish on the App Store and Google Play. They bring fixes, compatibility tweaks, and sometimes features an old version cannot show well. Updating from your device's official store is the path; do not install from forum links or loose files.

If your install is very old, the server may ask you to update before continuing. Then the app blocks with a clear message and a store button. That is not punishment: it keeps what you see aligned with what the server stores, and avoids holes in old accounts. Update, reopen, and only then write if the bug persists.

1. Open Librarius on your system store (iOS or Android).
2. If a new version exists, install it and wait until it finishes.
3. Open the app and retry the flow that failed.
4. If it is unchanged, send feedback with device, screen, and steps; do not repeat "I already updated" without that context.

The web does not "update" like the app: reload and you have the published version. If something looks wrong only in the browser, say so (browser and page). If it fails only on mobile, do not assume the web is broken. And the reverse: a web bug is not fixed by reinstalling the app.

Librarius may have social profiles (for example Instagram) to show the community or news. That is not a help desk. A comment on a photo, a DM to that account, or a mention does not enter the feedback queue. Someone may never see it, or see it late without the context a form asks for.

• Social: outreach, not tickets. Do not send account data there.
• Chat with another reader or a profile that "looks official": not support.
• A post on your wall or in a club: for reader conversation, not reporting a bug to the team.
• Emails to made-up addresses or "info@" not listed in the FAQ or legal pages: they may not exist.

Store review threads are not support either. A public rating helps others decide whether to download; it does not replace the form if you want someone to reproduce a bug. If you already wrote in the store and also send feedback, you do not need to copy the same text on social "just in case."

A good message fits in one paragraph plus three facts: what you were doing, what you saw, what you expected. For an idea, state the problem you want solved, not only the solution you imagined. For a bug, a mid-state screenshot helps more than "it does not work." If it touches your account, use the email you sign in with.

We do not promise a fix date or that every suggestion ships in the next version. We do read what arrives on the right channel. Meanwhile, the FAQ and this guide keep an old-version or system-permission issue from looking like "the app does not listen." For legal or privacy topics, current text is in privacy policy and other legal pages on the site.

Summary: FAQ to orient yourself, feedback or contact to write us, store to update, social to browse, not to ask for help. Follow that order and your message arrives with context without depending on someone spotting a stray comment.

In real life, support and feedback shows up when you mix solo reading with clubs, events, or the marketplace. Librarius does not replace human judgment: it organizes information so you can agree on dates, status, and owners without losing messages in generic apps.

Before you touch advanced settings, check what is public and what is members-only. Many conflicts come from assuming a private club wall is visible outside.

Document agreements in the right space (club calendar, event page, swap chat) instead of splitting details across three parallel conversations.

When the club grows, name moderators and rotate tasks (book pick, spoiler control). Polls with a close date keep a vocal minority from always choosing.

For support and feedback, review each quarter whether the rules still work. An annual cleanup of lists and archived chats cuts noise.

If something breaks technically, screenshot and use support; do not post other users' personal data on a public wall.

Watch for pressure to buy, harassment in chat, or swaps without confirmed status. Pause the operation, report, and move to a public meetup.

If notifications overwhelm you, mute side threads and keep only club alerts and direct messages. Deep reading needs boundaries.

When support and feedback feels chaotic, return to one official channel per topic for a transition week.