We have an ambitious set of features planned for CloudTables and want to share our plans with you, as well as asking for your feedback on what would make CloudTables more compelling as a product and easier to use. Get in touch with any thoughts you have about our road map, even if you just want to chime in with which features you would like to see prioritized. Then we can let you know when they are available.
This is a list of features we are working on at the moment or intend to ship in the near term.
Being able to configure a single data set and then share it amoung your clients, without them exposing data to each other, is an important aspect of any multi-tenent application. After all you don't want to keep setting up the same data set multiple times! We will be adding a condition option to the embed API that can be used to limit what data is loaded. It will also provide the ability to set values when creating or updating rows, ensuring the separation of data between clients.
We feel this is a key missing input type at the moment. When available you will be able to configure an input field that accepts one or more files for upload (with validation for the file type - e.g. limiting to images). You will also be able to present download and view options for the files in the display table.
At this time a single account is all that can be used to adminsiter a CloudTables application (note - if this is a problem for you, please get in touch as we can setup multiple user access manually). We will be introducing the ability to invite your team members to adminsiter your CloudTables application, have them sign up and optionally manually verify that you wish to give them access.
While our hosted CloudTables takes all the pain out of database and computing host environments for you, we recognise that some of our customers would either prefer to host their database themselves, or are required to do so by law (e.g. for HIPAA). We will be offering an installable version of CloudTables that can operate with a Postgres database you host (note that CloudTables will still use its own data schema) on servers you manage. Most likely this will be offered as a Docker container, but we are actively looking for feedback and if your are interested in self hosting, please get in touch to discuss your requirements.
The above discusses our immediate priorities, but we also have a long term vision of how CloudTables should evolve.
Our data architecture allows for massive data sets (millions of records), and we intend to expose that ability so you don't need to worry about hitting any artifical limits. We are keen for this to be a seamless experience for both you, the developers using CloudTables, and for the end user.
You might wish to have a notification whenever an edit is performed on data set - webhooks will provide exactly that capability. Set an end point (http) and you will receive a request with information about the action performed, letting you automate other actions (e.g. an e-mail notification or data refresh for a static page).
The table view we use is rich in features thanks to DataTables, but a table view isn't right for every data set. For time series data, you might wish to display the read / write interface to your end user as a calendar. With this ability in CloudTables, displaying a calendar will be as simple and configurable as it already is for a table.
We already provide API libraries for various server-side environments (including PHP, .NET, NodeJS and Java) which can be used to embed data sets securely into your own web-pages and also for data retrival from a data set. We intend to expand upon this ability to allow records to be created, updated and deleted through the API. This is primarily to allow automation with your own systems (e.g. event reporting), but can also be used to provide a custom interface for data submission if required.
CloudTables records an audit history so you can see what changes have been made and who by. We will expand this capaiblity in future by adding the ability to undo a specific change, or to roll a record back to a specific version of its data.
Of course, not everything about running CloudTables can be compartmentalized into in individual headings such as those above! As on going work we will be exposing more of the features that DataTables makes available, monitoring and improving performance of the application and general maintence of the software.
As noted above, we are keen to work with you, so please do get in touch to discuss how CloudTables can work better for you.