Apps
Share an App with Your Lab or Clients
Share an app so lab mates or core-facility clients run it on their own data, with a sequencing core's FASTQ QC app as the example.
A tool is most useful when others can run it without you. Share an app with people by email, with your organization, or with anyone signed in to Drylab. Each person gets a private copy that works on their own files, so your data is never exposed.
Why you'd use it
- Stop being the bottleneck. Clients and lab mates run the tool themselves instead of waiting for you.
- Their data stays theirs, yours stays yours. Each person's copy only sees the files they pick, and saves to their own Storage.
- Everyone uses the same rules. Thresholds and plots are the same for every client and every run.
Example: a sequencing core's FASTQ QC app
After every run, clients ask the core "can you send me the QC?". The core builds a QC app once and shares it with all clients. Each client opens it, picks their FASTQ files from their own Storage, reads a pass, warn or fail table, and saves the summary next to their data.

Prompt to build the app
Build a FASTQ QC app for our sequencing core's clients. Let the user pick one or more *.fastq.gz files from their Drylab vault, or upload them from their computer. For each file show per-base quality, GC content and adapter content, an estimated read count, and a summary table with pass, warn or fail (fail if the median per-base quality drops below 28, warn if adapter content is above 5%). Check the first 200,000 reads of each file so it stays fast, and estimate the total read count from the file size. Let them download or save the summary as qc_summary.csv, and add a Load example button and a short help panel that explains each plot.Check a sample sheet before submission:
Build a sample sheet checker our clients run before they submit. Let them pick samplesheet.csv or .xlsx from their vault or upload it. Check that sample IDs are unique and use only letters, numbers, - and _, that i7 and i5 indexes are valid DNA of the right length, that no index pair repeats within a lane, and that the columns Sample_ID, Index, Index2, Lane and Project are present. Show errors by row and let them save samplesheet_validated.csv once everything passes.For a flow cytometry core:
Build a QC app for flow cytometry files. Let the user pick *.fcs files from their vault or upload them. For each file show the event count, an FSC-A vs SSC-A density plot and the channel names, and flag files with fewer than 10,000 events. Let them save fcs_qc.csv.Steps for you
- Build the app and test it on one good run and one run you know has problems.
- Open the app (or click Share on its card in Apps) and go to Sharing:
- Under Add people by email, add each client's email.
- Or set General access to My organization (on organization accounts) or Anyone signed in to Drylab.
- Click Save, then Copy link.
- Send the link, for example with each data delivery. Clients need a Drylab account on any plan. The app opens for them as long as your plan includes Drylab Apps. See Share an app.
You can also ask Drylab in the same chat, for example "Share this app with client@university.edu". Drylab asks you to approve, for example "Invite people to this app?", and notes: "Your files stay private: everyone who opens this app gets their own copy, running against their own storage."
If you open your shared app inside a chat, its file dialog opens inside Drylab and the button reads Use selection instead of Use files.
Steps for people you share with
- Open the link, or find the app under Apps > Shared with me. The first time, Drylab shows what the app can do; click Open app (or Allow and open if it runs tools on your credits).
- Click Pick from Drylab vault, open the run folder, tick the files and click Use files. Or click Upload from device.
- Read the results, then save them with Save to Drylab vault > Save here.
Good to know
- People need a Drylab account. They sign in to open the app. See Plans.
- Big files belong in Storage. Multi-GB files such as FASTQ are much easier to pick from Storage than to upload through the browser; upload is for small files.
- A private copy for each person. It runs on their account; their copy stops after a while without activity, and starting it again takes a minute or two.
- Tools use their credits. If the app runs Drylab tools, Drylab asks "Allow this app to use your credits?" before it opens.
- Changes keep the same link. When you improve the app, everyone you shared it with keeps the same link.