# Request an app


> What customers ask for is what gets built next. How to ask, and what makes a request more likely to land.
There is a **Request App** button next to your apps, and you can also ask through the {{< support-link "support portal" >}}.

## What to include

Say what you would put on screen and why, not just which product you want connected. "A Jira board" is a product; "the current sprint's blocked tickets, on a wall in the engineering area" is a use case, and the second is far more useful to us.

Where it would run, and how many screens, helps too. So does saying whether it needs to be live to the minute or whether a refresh every few minutes is fine, because that changes what we would build.

> [!NOTE]
> A request is not a commitment. We review them all and prioritise by what customers across industries are asking for. If something you asked for is being built, we can tell you.

## While you wait

Two things often cover the gap.

**A web page.** If the tool already has a display or kiosk view, point a screen at that URL. See [Web pages](/docs/content/web-pages/).

**Zapier.** If the data has to move rather than be displayed live, Zapier can push content into Screenly when something happens elsewhere. See [Going further](/docs/integrations/beyond/zapier-and-the-api/).