ba9607f2e640454697ddcd46b78aaa98Q: Hi - I’m honestly clueless with the description of this offer.
On the one hand, you said: “ toddle is for building complex web applications, like facebook or appsumo.”
Then, on the other hand, you stated: “toddle does not have a database or user management built in, since each application you build with have different requirements”.
Where I am at lost? How can we make “ complex web applications, like facebook or appsumo” with toddle, if it does NOT provide the backend as part of the solution?
I get that I may integrate with whatever I want as backend using REST API. But then, I wonder:
1. How much code will be required for the integration and management on the backend? Toddle only deals with the frontend, right?
2. How much of a headache would be dealing with a second vendor when I run into any problems - I just could see the emails from toddler stating it is something at the other vendors end, and viceversa!
3. Dealing with breakups when either toddler or the backend provider update their APIs. Back to the second concern!
In conclusion, this is essentially an offer for ‘frontend template engine’ (as NOT many templates are ready yet) + hosting of the frontend. The backend is our responsibility!
Am I missing something?
Are you considering including the backend in the roadmap?
PS: Then there is the 1-dev only regardless of the Tier. Most of the sumos would be expecting an increase in dev accounts in accordance with the provided apps per tier 🤦🏻♂️!
Great questions. It is correct that toddle is "bring your own backend"
It's a good observation, but we truly believe that toddle is much more than a templating engine. For example, we have tools to help you connect to your backend API. You can see, work, map, and post to your backend inside the editor, and you can pick the backend(s) that is best for your project. In the toddle editor (which is built in toddle 🤯) we actually use multiple backends ourselves (!) Contentful to keep track of content-specific data, supabase for our structured data, and our own custom backend for live sessions between teams. That being said, most of our logic is handled by toddle itself, so our backends are mostly just simple data stores; but stores with different architectures and interfaces to handle different problems.
We currently have no plans to introduce our own backend, however, with toddle you often don't need more than a simple data store like Google Sheets, firebase, or Xano, as toddle can handle all the logic for you and we always work on creating better integrations to whatever backend you decide on.
Hi Jacob! Thanks for your reply.
But this is precisely my point:
“ with toddle you often don't need more than a simple data store like Google Sheets, firebase, or Xano,”
If that is the case, why NOT partnering with a backend provider and make this transparent for your users?
This way, toddle would be providing an end-to-end solution (at least) for most use-cases…while improving user experience (and service) and still providing the REST API integrations for more complex use-cases.
Here is an idea,… Recently there was another offer here in AS that may be a good fit - Retable. They likely may power your backend!