The mobile app

The MakerOps app for iOS and Android is the day-to-day surface for most people in your space. The web app is where staff do deep configuration; the phone is where the floor happens.

Getting in

• From an invite: accepting your email invitation inside the app signs you straight in — one tap, no separate login step.
• Existing account: sign in with your email and password, or through your institution’s SSO where enabled.
• One account can belong to multiple spaces; the app keeps them separate.

What members use it for

• Run machines — scan the QR on a machine’s controller to start a session, see time remaining, extend, and check out. The app is also where a refused scan explains itself: which credential or waiver is missing.
• Training — take courses and see credentials, right on the phone.
• Schedules — space hours (including what access applies right now), machine booking, and event details.
• Report a problem — scan a machine and file an issue with a photo.
• Borrow tools — scan a self-serve tool’s tag to check it out, acknowledge a desk loan with a drawn signature, and see what you have out and when it is due. Your My badge code is what the desk scans to name you as the borrower. See Loans.

What staff use it for

• Front desk on the move — look people up, check credentials and waivers.
• Shifts — the rota calendar, shift swaps, and clock-in for spaces using time tracking.
• Equipment — mark a machine down for maintenance on the spot, work through maintenance tasks, and sweep the fleet with QR scans.
• Controller setup — provision new machine controllers onto Wi-Fi and bind them to machines (see the controller manual).

Notifications

Push notifications cover the things worth interrupting for — session warnings, shift reminders, maintenance due, @mentions — and each person tunes their own channels (push, email, in-app) in their notification preferences.

Phones and the web app

The full web app is built for desktop and tablets; on a phone it points you to the mobile app, which is built for that screen. Anything configuration-heavy — the permissions matrix, training authoring, label design — stays on the desktop.