Royco | wapps

Royco turns a team’s meetings into planned work. A team uploads a meeting or records it live, on the web or on an iPhone. Royco writes the transcript and drafts the decisions, the action items and the requirements.

It is for software and product teams. The team assigns the drafts, tags them and moves them on a board.

We write the recording to the phone first.

The iPhone writes the audio into one-minute files as it records. Live transcription is a layer on top, and the files are written whether or not it runs. If the app stops, at most the open minute is lost, and the upload queue survives a relaunch.

We built a demo mode with no backend.

Demo mode swaps only the edges, with an in-memory backend, a scripted microphone and a fake uploader. Every feature runs the same code as live mode. A unit test fails every network request while the demo runs, to prove that it sends nothing.

We fall back to our own model when a team's key fails.

An organisation can bring its own model key. If the key is missing, cannot be read or names an unknown model, the server uses our default model. So the analysis never fails because of a customer's key.

We refresh a session once, however many requests fail.

On the iPhone, 100 requests that get a 401 at the same time cause one refresh. A sign-out during a refresh is never undone by it. No request carries a cookie.

We keep every animation value in one file.

Spring and easing values may appear only in the app's motion file. A lint script fails the build when one appears anywhere else.