Overview
PanelUI Studio is the hosted backend behind PanelUI's Feedback — reports, screenshots and two-way conversations, with an inbox for your team.
PanelUI draws the screens. Studio is where what your users send ends up: an inbox your team reads and replies from, and an API the app talks to with nothing more than a publishable key.
It is optional. Every PanelUI component works without it, and PanelUI stays free and open source. Studio is a hosted service with a free plan, for when you'd rather not build the backend yourself.
What it does
- Feedback. A message, a rating, tags, the screen it came from and the device context — collected by the SDK, not typed by the user.
- Screenshots. Uploaded straight from the device or browser to private storage.
- Conversations. Every report is a thread. You reply from the inbox; the app shows the reply and the user can answer.
- Support. Users start a conversation themselves, into a Support inbox.
- Announcements. Write a message once and show it in every app.
- Custom forms and webhooks. Extra questions on a report, and signed events for your own backend.
- Identity, optionally. Anonymous by default, so apps without accounts work. If your app has sign-in, attach the user to their reports.
How the pieces fit
Your app ── panelui-studio (SDK) ── Studio API ── Inbox (your team)
│ │
└─ your screens (PanelUI or your own) └─ email, Slack, LinearThe app ships a publishable key, which is public by design: it can only submit to its own project.
Each install registers itself once and keeps its own token in secure storage, so no secret is ever bundled into the app. The SDK works in Expo, bare React Native and Expo's web target.
Each browser registers itself once and keeps its own token in localStorage,
so no secret is ever bundled into the site. The SDK works in Next.js, React,
Vite and any other web bundler. PanelUI's components are React Native
components and don't run in a browser yet, so a website draws Studio's screens
with its own.
When to reach for it
Use Studio when you want feedback and replies working without a database, an
upload pipeline and an admin screen of your own. If you already run a backend
and want the data there, Feedback posts to any
onSubmit you give it — Studio is one destination, not a requirement.
In this section
- Quickstart — from a new project to the first report.
- Feedback — what a report can carry, screenshots and limits.
- Custom forms — extra questions, checked answers.
- Conversations — showing replies in the app.
- Support — conversations your users start.
- Announcements — messages you publish into the app.
- Webhooks — signed events for your backend.
- Identify users — anonymous installs and signed-in users.
- API reference — every method, hook, type and error code.