Support

Something not working?

Email hello@labbee.app and you will reach the person who wrote the app. There is no ticket system and no bot.

It helps to include your iOS version, your device, and what you expected to happen. If it is about a timer, say whether the app was open, backgrounded or closed at the time. That single detail usually identifies the cause.

An alarm did not sound

Work through these in order; the first three cover almost every case.

How many timers can run at once?

iOS caps how many pending notification requests an app may hold, so LabBee budgets them: every running timer is guaranteed its mandatory end alarm first, and the optional early warnings are filled in with whatever room is left. If you are ever at the ceiling the app tells you rather than silently dropping an alarm.

A calculation looks wrong

Please tell us. A wrong number in a lab tool is the most serious kind of bug there is. Send the inputs you used, the result you got and the result you expected. Every calculator is covered by tests written against textbook values, so a report like that turns directly into a new test case.

Two things worth checking first: that the unit selector is on the unit you think it is, and that molecular weight is entered for the compound you mean. Where a value cannot be derived, for instance a polymer with no single molecular weight, LabBee leaves the field blank rather than inventing a number.

Counting and export

Where is my data?

On your device, and only there. See the privacy policy. This also means that if you delete the app, the data goes with it, so export anything you want to keep first.

Requesting a tool

The roadmap on the home page lists what is already being built. If what you need is not there, write in and say what you would calculate and how often. Requests that come with a real bench workflow attached tend to get built first.

Reporting something urgent

If you find a result that is wrong in a way that could damage an experiment, put WRONG RESULT in the subject line. Those are read first.