Integration with Airtable to use as a basic database. This would make it very easy to spin up basic apps.

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.

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...

The ability to use SVG as graphics. benefits would be scalability and responsiveness.

Having the ability to see an overview of all screens like in say Sketch or Figma would be ideal too. Even if the overview is in a read-only state perhaps with export to PNG as an option too. Furthermore, Integrating the Navigation tab’s connection/linked functionality into the suggested Screens Overview page for a quick and easy visual language to see how each screen interacts with each other would be ideal.

For Integrated authentication and other services.

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.

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.

Rather than click-to-add, Draftbit components should be drag & drop onto Web Preview or into the Layer Tree.

Create template apps for common use cases.