Support

Common questions

A crate will not compile

Crabrix compiles to wasm32-wasip1 with a bundled compiler that has no linker for native code. Crates that need C code, procedural macros, or a build script generally cannot build on device, and Crabrix marks them as unsupported rather than failing halfway. The Packages screen says which of your dependencies are verified, expected to work, or blocked, and why.

A build is slow

The first compile of a project is genuinely doing the work — a real compiler, running in a WebAssembly interpreter, on a phone. Identical repeat runs come from a local artifact cache and are much faster. Large dependency trees take longer on first fetch; after that they rebuild offline.

I ran out of health or energy

Both refill on their own, and faster at a higher rank. Training — Quick Practice, Term Train, and Code Recall — never costs either, so there is always something to do while they come back. Re-reading a lesson page you have already opened is always free.

Where are my projects stored?

In the app's own container on your device. Save a project to Files or iCloud Drive from the Projects screen if you want a copy you control, or use Archive & Share for a plain ZIP. Deleting the app deletes everything that was only inside it.

Does it work offline?

The compiler, curriculum, and local projects work offline. Cached dependencies rebuild while iOS retains them; Pin for Offline keeps their exact verified archives durable after a cache eviction. First-time package downloads and GitHub imports need a connection.

Do I need an account?

No. There is no sign-up, no password, and no email address to give. Crabrix 1.0 has no public board and no online profile: your rating stays on your device.

Bugs and feature requests

The shortest route is inside the app: Settings → Help & problems → Report a problem. Pick the area, say what happened and what you expected, and it opens a mail draft with the version, iOS, device model and toolchain already filled in. Nothing is sent by the app — you read the draft and send it yourself, and you can turn the attached details off before you do.

Otherwise use the form below, or open an issue on GitHub. For a build problem it helps enormously to include the Rust code and the compiler output from the Problems tab.

What is it about Building or running code The editor Packages and crates.io Lessons and courses Projects, import, or export Buying, refunds, or the App Store Something else What happened Open this in your mail app

This form does not send anything and stores nothing. It fills in a draft in your own mail app, which you read and send yourself.

Refunds

Purchases are handled by Apple, so refunds go through Apple rather than through me: reportaproblem.apple.com. If something about the app is broken, write to me too — I would rather fix it.