Below are some frequently asked questions (FAQs) about data apps in Displayr. See Get Started With Data Apps for information about the workflow and features available to build a data app.
Questions:
- Do you have examples of data apps built in Displayr?
- How much does it cost to make a data app with Displayr?
- What security do you have in place? Do you comply with GDPR?
- As an independent contractor or consultant working for a client, how can I build and deliver the app to my client?
- What options or programming languages can I use to customize my app?
- Can I use my own R server with Displayr?
- What R packages are available in Displayr, and how do I add a new package?
- Can I use Displayr to run and host my already-built Shiny app?
- Can I create Webhooks or use JavaScript libraries within the Data App to trigger actions? Such as creating an Export or Submit button?
- Can I export my data app as a package and host it elsewhere?
- Is there a limit to how much data I can import?
- Do you have guarantees for uptime on published data apps?
- Can I choose the server size to cater to usage spikes or do parallel processing?
Do you have examples of data apps built in Displayr?
Yes, a list of example data apps is here and include dashboards, infographics, simulators, and more.
How much does it cost to make a data app with Displayr?
To build a data app in Displayr you will need to buy both:
- An editing license.
- Server time to host your data app.
See our pricing page for the latest prices.
What security do you have in place? Do you comply with GDPR?
Almost all of our users work with confidential, sensitive data, so we take security around our system very seriously. We do comply with GDPR and are SOC2 compliant. See our Trust Center to view details around our compliance, policies, reports, and status.
As an independent contractor or consultant working for a client, how can I build and deliver the app to my client?
There are a couple scenarios of how to do this depending on your needs:
- The developer buys a license for their own personal account and builds the data app there. They can share the published data app with the client via URL, or they can send a QPack file for the client to upload and host on their own Displayr account (this requires the end-client to have a license).
- The end-client can purchase a license for the developer on the end-client's account, and all work and hosting is done within the end-client's account directly. The end-client can access the published data app via URL, or via their own license in edit mode from their Documents page.
What options or programming languages can I use to customize my app?
You can customize tons of things about your data app via Displayr's menus using point and click. For more specific customizations, Displayr supports:
- R code - for data prep, creating variables, items on a page, analyses, and visualizations.
- JavaScript - for creating variables, customizing tables, automating tasks within the tool, and GUI controls for R-based analysis tools.
- HTML - for custom HTML outputs on a page and the account HTML header.
- CSS - for styling and configuring the navigation pane, header strip, and body sections of your app.
While Python is not supported within Displayr, you can use Python to interact with the Displayr API.
Can I use my own R server with Displayr?
No. Displayr is already integrated with R via R servers on the cloud.
What R packages are available in Displayr, and how do I add a new package?
We have over 1,000 libraries loaded, and you can see the most up-to-date list here.
If you find that there's a package you're particularly familiar with, contact our Support team, and we'll pass it through our quality control process before adding it. Keep in mind that if you have a custom or proprietary package and request it to be added to Displayr, it will be viewable by any other users. As an alternative, you can create a pseudo package that will only be available to documents on your account, see How to Share Custom R Functions in Displayr.
Can I use Displayr to run and host my already-built Shiny app?
No, Displayr cannot host and run existing Shiny apps as Shiny has its own deployment and hosting processes built-in. However, individual items from your Shiny app, such as custom calculations and visualizations, can be recreated in Displayr for your Data App.
Can I create Webhooks or use JavaScript libraries within the Data App to trigger actions? Such as creating an Export or Submit button?
When a user changes an interactive control in the Data App, all dependencies are recalculated/executed automatically. While Displayr does not have buttons to trigger actions, you can trigger recalculations based on using one of our other supported input controls and create an image of a button for users to click on that will confirm they are done editing their inputs. Using outside JavaScript libraries and webhooks in the Data App is not supported due to security risks.
Can I export my data app as a package and host it elsewhere?
No, Displayr documents, including data apps, can only be exported as QPack, which is a file format native to Displayr. You can use your data app elsewhere via an embedded iframe.
Is there a limit to how much data I can import?
You will need a paid license if your data set has more than 1,000 rows and 100 columns. With a paid license, there are other limits depending on how you are importing the data. In general, the maximum size is 2GB (though a zipped version under 2GB works), and the data must be loaded in Displayr in 2 minutes or less.
Do you have guarantees for uptime on published data apps?
We guarantee a 99.5% uptime excluding downtime for scheduled and emergency maintenance. See our terms for more details.
Can I choose the server size to cater to usage spikes or do parallel processing?
Displayr does this automatically as required. Generally, our R servers have at least 16GB of RAM and up to 32GB in some regions. Because Displayr knows which R calculations and outputs are dependent on one another, it can process calculations concurrently, if they aren't dependent on one another.