Skip to content

Ask for an inline app

Sometimes the useful answer is not something you read but something you poke at: a list you filter, a threshold you slide. An inline app is that — a small interactive app Ronja writes into the conversation in place of her written answer.

It is not an App. An App is published: it lives in a feature, has its own page, and others open it by a link. An inline app lives in this chat and nowhere else — no publishing, no approval, no address to send anyone.

  1. Ask an ordinary question, and say what you want to do with the answer. “Show me margin by product — I want to filter by region and change the discount assumption.”
  2. Watch the answer column. Ronja writes her finding as text first, then a panel marked Building names each file as she writes it. It says Refining and Patching when she changes an app you already have, and Fixing, beside the title Fixing the app, when she repairs something her own check found.
  3. Use the app as soon as it replaces the panel, marked Checking the app. Ronja is opening it to see that it renders, and her reply ends when that does; the box beside the composer says Checking the app… meanwhile.
  4. Wait for the header to settle on Interactive. If you can build, a Make it an App button appears beside it. That is the whole app.

You need not ask for one by name: “let me play with it” lands in the same place. It arrives styled like the rest of Ronja.

An inline app reads your data live with your own access — not Ronja’s, and not that of whoever asked for it.

That matters when you share the chat. A colleague opening the same conversation gets their own copy, reading as themselves: a table they may not see is refused for them and works for you, in the same app. A panel telling them they can’t reach that data is the app working correctly.

  • Sharing the chat does not share the data. Handing someone the conversation gives them the app, not your reach.
  • Stopping sharing stops the app. When you stop sharing the chat with a colleague, an inline app they already have open stops within 30 seconds.
  • Outside systems are reached as the reader too. If the app calls an outside API or database, the call goes out with the credentials of whoever opens it — and what that call does there is up to that system, so an app that writes to an outside service writes as each reader.
  • What it shows is live. Re-open the chat a month later and it re-queries; the numbers in the text above it are from the day it was written.

Ask for changes in the same conversation — “add a date range”, “sort by margin” — and the app is rewritten in place rather than stacking up beside itself.

If you explore a tangent from a chat that has an inline app, the branch inherits it — but the app itself still belongs to the conversation you branched from. It works for you there. Someone shared only on the branch, and not on its parent, gets This app is not available. in its place. Change it in the branch and the branch gets its own copy, which then opens for them; the original is untouched either way.

An inline app lives and dies with its conversation: delete the chat and the app goes too. To keep one:

  1. Click Make it an App in the frame’s header. It shows once the header reads Interactive, and only to readers with Build mode.
  2. Let Ronja build it as an App in the Build-mode branch that opens, seeded with the app’s source. This chat is left as it was.
  3. Click Approve when Ronja asks to Publish 1 app. Until then the App is a draft only you can see.

A reply that ended without the button, because you pressed Stop generating or it was cut short, never gets one. On a settled frame, no button means you don’t have Build mode; a colleague who has it can open the conversation and click it.

A published App has one set of powers for everyone who opens it, while an inline app gives each reader only their own. If people should see different things, keep it inline, or have the App’s server functions decide with Server-side data only on: see Show each person only their own data.

  • A second screen. One view, one thing to interact with. More than that is an App.
  • Changing anything in Ronja. It reads; it cannot change a table, send mail, or run a workflow.
  • Saving a file. An inline app cannot download anything, so its tables have no Export CSV. Ask for an App if you need the rows in a spreadsheet.
  • A number, a comparison, a trend or a ranking. Those are charts, easier to read and to forward.
  • Slack or Microsoft Teams. A bridged conversation gets the written answer only.