What are some common backend functionalities you find yourself implementing over and over again?
https://getboost.dev
Hi, folks,
my friend and I have been working on a drag-and-drop editor builder for backend. We are trying to find out what are common backend functionalities across different (web)apps so we implement the right set of features.
As a small experiment, we created a website where you can send us a task you need to have built and we'll code it. If it's your first task, we'll code it for free!
Feel free to ask any questions!
I'll automate things if I find myself doing them over and over again. That's one of the major reasons to code at all!
The major exception is things that are moving targets like integrations with quickly changing 3rd party APIs.
For me I would like to see seemlesss database configuration and integration. Example connecting ionic app to Firebase. Connecting ionic to Stripe. Deploying to host server with one simple process. Is that something you could do?
Could you elaborate more about what are painful steps when integrating Firebase into your project?
Essentially when I create the base project in Ionic I would want a Firebase service created and I just would supply my account credentials, and each page I create in the app could call the Firebase service.
It's doable, but it's not easy. Surely someone can call Firebase for each base, but what do they do with the data elements in the page? When you create a page, those elements are undefined. Which ones go to Firebase? Where in firebase? ... and where does the data come from? Wiring up UI to backend does require some logic and decision and that's why it's a manual process. Even the nocode movement will have to deal with that. Anyways, I see you're a UX person, how good are you with design in Ionic? I'm more of a backend person, terrible with design, but good with the wiring, perhaps we can trade skills?
I probably would just want the boilerplate logic as a template and would configure the data elements. I’m working on the front end for an Ionic app now. Making pretty good progress. I’m down to discuss trading skills. I’ll send you a message.
This comment was deleted 4 years ago
It's operating on top of existing cloud platforms.
Right now, we are using Javascript.
Given that the rest of my app isn't in JS, why would I want to call outside my code base, add extra communication overhead, increase latency, etc?
It seems to me like this would work best if your were plugging into a specific, popular platform that has strong conventions, like Rails or WordPress. Then the overhead interfacing with your code would disappear.
There isn't really one for back-end JS, but there sure is for Gatsby. Niching down like that might help you.
I think there's a misunderstanding. You sign up on our website and link your existing account from either AWS, Azure, or Google Cloud.
Then you can use our editor.
We function as an abstraction layer on top of existing cloud platforms.
This still sounds like increasing latency, adding an extra layer of communication and calling outside my code base (which is hosted on Digital Ocean).
It doesn't increase latency. We deploy the code onto the cloud platform you're using. You just don't have to manually code features every time and can ship much faster with us.
Of course, if you're using a cloud platform we don't support yet, you can't use our tool.