-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
I'm using Firebase Authentication and Firestore by an app I'm building and so far have been using the Firebase SDK and some hooks from usehooks.com to control authentication and data fetching/caching, but I'm concerned that this might lock me in to Firebase's SDK. I'm curious what everyones preferred method is when it comes to working with Firebase; do you use their SDK for data fetching or are you using packages like React-Query, Axios, etc, with Firebase Authentication and Firestore? The simplicity of their SDK has been the attraction so far but some of the other packages I've seen really don't seem too difficult to work with. But perhaps using their SDK creates an unnecessary vendor lock-in if I ever choose to use a different backend or need to query a different backend for portions of â €my application. I'm curious what other peoples thoughts are. I should also mention the one thing that I really like, and use frequently, within the Firebase SDK is its realtime updates. I've found that very useful for aspects of my app. Reading through some of the other packages it seems like they have the same function, but where you set an interval for how frequently they check the backend for an update. What my understanding of the Firebase SDK and Firestore is that they maintain a session and instead of querying on an interval basis, the backend is notifying the frontend when changes take place. Is the interval method pretty standard to follow or does it create a bit of an inefficiency that should be avoided?