Drylab

Apps

Overview

Turn a Drylab analysis into an interactive app, share it with colleagues or your organization, and open apps from the Drylab Library.

An app is an interactive web tool that Drylab builds from one of your analyses and runs for you, such as a gene explorer, a dashboard or a small calculator. You describe the app in a chat, Drylab writes and starts it, and you get a link that opens it in the browser. (Earlier versions of Drylab called apps "Sites".)

What an app is

A figure or a table shows one view of your results. An app lets people choose their own view: search for a gene, change a cutoff, pick a sample, and the plots update on the spot. Nobody has to install anything, write code or ask you for another plot.

  • Built from your chat. Drylab makes the app from the data and results in the chat, so it shows your analysis, not a template.
  • Opens with a link. It runs in the browser, inside Drylab or in its own tab.
  • Private by default. Only you can open it until you share it yourself.
  • Each person gets their own copy. When you share an app, everyone who opens it gets a private copy that uses their own Storage and credits, so nobody sees anyone else's files.

Why use an app

  • Let collaborators explore the results themselves. Your PI or a wet-lab colleague can look up their favourite genes or try a different threshold without waiting for you to rerun the analysis.
  • Replace a pile of static figures. One app with filters can stand in for dozens of exported plots and spreadsheets.
  • Hand over a tool, not just a result. Share a small calculator or a QC viewer that people can run on their own data.
  • Start from a ready-made app. The Library has apps from the Drylab team that anyone can open with their own files.

Use cases

Each page starts with why you'd need it, then shows one lab app built for that job, with a short video and a prompt you can copy.

To let your PI explore a finished analysis, see Share Results with Your PI.

Plans

Publishing and sharing your own apps depends on your plan:

  • Your plan doesn't include Drylab Apps: the Apps page says "Apps come with Lab plans." and offers See Lab plans. On your plan the assistant makes the same thing as an interactive file in your Storage. You can still open apps shared with you and every app in the Library.
  • The owner's plan changed: if the owner's plan no longer includes Drylab Apps, their apps show a Paused badge. Nothing is deleted; the app comes back unchanged, with the same link and the same people, when they upgrade.

See Plans & Billing.

Open Apps

Click Apps in the left sidebar to see every app you can open. You can also press Ctrl + K and use the Apps tab of the search.

The Apps page, Library tab

TabShows
AllYour apps and apps shared with you
MineApps you made in your chats
Shared with meApps other people shared with you
LibraryReady-made apps from the Drylab team

Each card shows who can open the app, with Open, and your own apps also have Share. Paused apps stay in the list with a Paused badge.

Your app under Mine, with Open and Share

Create an app

Ask Drylab in a chat, for example:

  • "Build an interactive app to explore the differential expression results, with a searchable gene table and a volcano plot."
  • "Make this an app I can share with my PI."

Drylab builds the app, tests it and publishes it. It then appears under Mine, and in the chat's App tab (Apps from this chat), with Open, Share and a link to See all your apps.

The chat's App tab

Open an app

Click Open. The app runs in the main area, and its information panel opens on the right:

An open app with its information panel

  • About says what the app does and lists the steps under How to use, with its Link, where it was Made in (Open the chat), its Last change and Who can open it.
  • Sharing (your own apps) is where you choose who can open it. See Share an app.
  • Settings (your own apps) shows the app's Saved work in Storage, kept even if you delete the chat, and Delete this app.

Press Esc or click x to close the panel, and use the button in the app's top bar to open it again. For your own apps, the top bar also shows how many people have a copy running right now.

Only the owner can change an app or who can open it. Library apps say "Made by the Drylab team. Only they can change it."

The first time you open a shared app

Drylab explains what the app can do before it opens: it runs in its own workspace on your account, it can't see your files unless you pick one, and whether it runs paid tools on your credits. Click Open app, or Allow and open for apps that use your credits.

An app sleeps after 2 hours with nobody using it, and wakes when someone opens it again. Waking usually takes a minute or two; nothing is lost.

Share an app

Open your app and go to the Sharing tab of its panel (or click Share on its card on the Apps page):

  1. Under Add people by email, type a colleague's email and click Add. They appear under People with access.
  2. Under General access, choose who else can open it:
OptionWho can open it
Restricted (default)Only you and the people you add.
My organizationEveryone in your organization. Only on organization accounts.
Anyone signed in to DrylabAnyone with the link who signs in to Drylab.
  1. Click Save, then Copy link to send it.

Who can open it: a colleague added, General access Restricted

You can also ask Drylab in the chat, for example "Share this app with sam.rivera@example.com" or "Make this app public". Drylab shows a card such as Make this app public? and waits for you to approve it.

Drylab asks before it shares an app

People you add always keep access, whichever option you choose. Each person gets their own copy with their own files and credits, and your later changes keep the same link and the same people.

To remove an app, open its Settings tab and use Delete this app. The link stops working for everyone; the chat and your files stay.

How others use your app

When you share an app, every person who opens it runs it on their own data. Your files are never visible to them.

One app, everyone's own data: you build an app in a chat and share it; each colleague opens a private copy, adds files with Upload from device or Pick from Drylab vault, and saves results with Save here to their own Storage; your files are never shared

  • A private copy for each person. The copy runs on their account and has no access to your Storage.
  • They choose the files. When the app needs input, they click Upload from device or Pick from Drylab vault ("vault" is the older name for Storage). That option opens "Choose files from your vault", which says "This app is asking for a file. It only receives what you pick." They select files and click Use files.
  • They choose where results go. When the app saves a file, they see "Save to your Drylab vault", pick a folder, check the file name and click Save here. The file goes to their own Storage, ready for their next chat.
  • Files uploaded from the computer are used for that run. To keep a result, save it to Storage. Apps that run Drylab tools keep their inputs and results in their own folder in the visitor's Storage.
  • Tools use their credits. If the app runs Drylab tools, Drylab asks them to allow it before the app opens, and those runs count toward the visitor's usage.

If the file picker closes before you choose, click the app's button again: a request waits for a few minutes, then expires.

Get the most from apps

  • Name every control. Say which sliders, dropdowns and buttons you want and their defaults. "Interactive" alone gets a generic app.
  • Say where files come from. "Let users pick from their vault or upload" and name the file types (*.fastq.gz, .xlsx, .tif), so the picker shows only what fits.
  • Name the outputs. Ask for a save button and give the file names, such as qpcr_ddct.csv and foldchange.png.
  • Add a Load example button and a short help panel. First-time users see it working before they pick their own files. Ask Drylab to fill in How to use too.
  • Do the heavy work in the chat first. Settle the method there, then build the app. For big files, ask the app to use a sample (for example the first 200,000 reads) so it stays fast.
  • Test it yourself, then share narrowly. Run it on one good and one bad file, add one colleague, and widen access once it's stable.
  • Improve it in the same chat. Ask "add a heatmap tab" or "make the colors colorblind-safe". The link stays the same for everyone you shared it with.

On this page