On your phone

Orazaka in your pocket: four steps

The mobile app is for running your work from anywhere — start a Studio, ask the model, and see where your jobs stand — against the same edge, services and interceptor pipeline as the web client. Four screens, in the order you use them. Press play; nothing starts by itself.

Recorded on the iOS 27 simulator (iPhone 17) against the local Orazaka stack, signed in as Eric, the demo persona.

  1. Step 1

    Sign in to your workspace

    One screen, one account: you sign in with the same credentials as on the web and go straight to your Studios, with nothing to configure on the phone.

    What to notice

    • Sign in stays disabled until both the e-mail and the password are filled.
    • No separate step after signing in: as soon as the session exists, the app swaps the sign-in screens for your Studios.
    • Forgot password and Create an account sit on the same screen, one tap away.

  2. Step 2

    Run a Studio from your phone

    A Studio is a ready-made workflow. The catalogue shows what each one costs, you fill in what it needs, press Run, and follow it to its results without opening a laptop.

    What to notice

    • A Studio that is not in your plan stays in the catalogue, marked “locked” — you see what you would get — and its page has no install button.
    • The form comes from the Studio itself: its own fields, required ones starred, so a run is not refused for a missing input.
    • The run is followed step by step, refreshed every two seconds, until the results appear.

  3. Step 3

    Ask the model, and read the answer as it is written

    When you only need an answer, not a workflow, you just ask. The reply arrives word by word instead of after a long wait, and the request goes through Orazaka's own pipeline.

    What to notice

    • The answer streams in as it is produced, so you can start reading right away.
    • The welcome text says each request runs through the local interceptor pipeline, on the stack you chose.
    • Leaving the screen mid-answer closes the request; Send is disabled while an answer is being written.

  4. Step 4

    Follow your jobs without opening the console

    Images, videos, voice and text are produced in the background. This screen tells you what is done, what is running and what failed, so you know where things stand from your pocket.

    What to notice

    • Two charts above the list: the last seven days split into succeeded and failed, and the share of each kind of work.
    • Each job shows its state, a progress bar while it runs, and the reason when it failed.
    • It is read-only on purpose: approving or purging a job stays in the console, never one tap away in a pocket.