Orazaka in your pocket

Recorded on the iOS 27 simulator (iPhone 17), in dark and light, against dev.orazaka.com, signed in as the QA user. Typing is sped up and waits are cut — each cut says how long it was.

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 extra step after signing in: as soon as the session exists, the app swaps the sign-in screens for your Studios.
   • The four tabs — Studios, Chat, Jobs, Profile — speak the language of the phone, in light or dark.

2. Step 2

   Make an image from a sentence

   A Studio is a ready-made workflow. The catalogue shows each one, you describe what you want, press Launch, and follow it to its result without opening a laptop.

   What to notice

   • The result is the run's own output from the platform: the image, and beside it the seed, the model and the time it took — nothing drawn by the app.
   • Tuning (seed, model, things to avoid) stays under More options; the sentence and the format are all most runs need.
   • The wait is cut from the recording and the label says how long it was; the app itself shows a progress bar while it runs.

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 chips under the answer are the interceptors that really ran for this request, as the router reported them — not a canned list.
   • The model chip says which model answers. The line "0 bytes left your network" appears only when that model runs on your own server — never otherwise.
   • Leaving the screen mid-answer closes the request.

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 a sentence when it failed — never a stack trace.
   • It is read-only on purpose: approving or purging a job stays in the console, never one tap away in a pocket.