Integration with Airtable to use as a basic database. This would make it very easy to spin up basic apps.
Logic module just like Bubble.io
As obvious from the title, Draftbit currently have nothing to define about what if and if then else scenarios. Take an inspiration from Bubble.io how they have nailed down the logic part. Without this feature, the ones who don't know how to code have no option except to look for some programmers who could build the login/signup.
Integration with Firebase would open up rapid creation of app backends and allow us to utilize the growth and analytics tools also included in Firebase. Specific integrations include: Firestore Storage Auth Push Notifications Analytics Realtime Database Functions And so on...
I would like to sync Figma design with Draftbit. As a designer I have to rely on a screen design tool, however I would like to reuse whatever I design in other apps. Being able to import designs and tweak UI in Draftbit would dramatically change and improve my workflow.
Local Storage Support
Having the ability to set and get local storage would be necessary to creating applications with sessions or other globally persisted data. For example, a login mutation would store a JWT token that would later be used by an authorized mutation or query by adding the token to the Authorization Header.
Be able to do some actions from keyboard shortcuts, like For Undo, Redo, Cut, Copy, Paste, etc.
Dark / Light Mode
User Story: As a user, I want to be able to select colours for dark/light mode so that I can easily switch themes. It would be great to provide a light and dark colour selection for components while designing. The final "controller" could be a dark/light mode switch that one can easily put into settings (of an app design)
GraphQL Schema Data Sourcing
The ability to globally supply a /graphql endpoint for the entire app could be the ultimate missing link here. GraphQL Yoga (Apollo) is exposing a query named "IntrospectionQuery" this could be where you can receive the schema. Once you have the Schema of the GraphQL server, all the different elements you add to your views would no longer be empty text fields and areas. There now would be a query / attribute selection available as the data source for each element. This feature would not only allow developers to build out a full featured app in hours, but the everyday non-technical user could build an app for any service that supports GraphQL with a click of a button. As a business, this could also be the answer to deploying apps straight from DraftBit. The ability to have real data wired up without ever pulling down the code with a single click deploy button would be extremely valuable. There is also services that are already supporting GraphQL APIs for third party services ( https://www.onegraph.com ). Being able to support multiple APIs in a single app would be extremely valuable for aggregation and integration apps.
Install 3rd party packages (NPM)
Since we have implemented custom code inside the platform it would be great the ability to install 3rd party packages (npm for example) in order to be used when needed. This feature would allow to use other platforms like AWS Amplify, Firebase or other services, or even use libraries to manipulate data when needed.