Why build another website builder?
71–80 of 89 posts
Re: Why build another website builder?
#72Re: Why build another website builder?
#73Earlier quoted context omitted.
You could use their APIs to pull your product catalog out, but IIRC their terms of service says that's not allowed if you're migrating to another system. l.o.l.
Yeah, you can't do that right now. But we do have plans to support self-hosting. We believe it will be table stakes for various customers. We're a small team of 5 right now, though, and decided to focus on the core experience right now.
Re: Why build another website builder?
#74Tangential: Does anyone know what the name of this latest design trend is that makes heavy use of illustrations with shapely people? Does anyone know where it originated? It's taken over everything.
At least if I understand you correctly to mean the cartoony faceless curvy people.
Re: Why build another website builder?
#75I realize this sort of tool targets a completely different audience, but what we desperately need is not more no-code builders, but a robust, DB-backed builder with an object-based workflow, and with code-behind for custom workflow logic. Like something that can compete with Zoho Creator, but is actually engineered in a sane manner, and offered at a sane price. It would take the market by storm. Most of the solutions…
Static files are stored in S3 and served by cloudfront. API endpoints are served by AWS Lambda, so it's quite fast and scalable.
It's also supporting advanced features like SSR and translations.
It's a low code solution, easy to use for non coders, and full access to source and advanced backend features for devs.
Disclaimer: I am the CTO ;)
Documentation: https://support.appdrag.com/
Re: Why build another website builder?
#76The question should be: Why don't we create a website builder focused in web performance?
Re: Why build another website builder?
#77I realize this sort of tool targets a completely different audience, but what we desperately need is not more no-code builders, but a robust, DB-backed builder with an object-based workflow, and with code-behind for custom workflow logic. Like something that can compete with Zoho Creator, but is actually engineered in a sane manner, and offered at a sane price. It would take the market by storm. Most of the solutions…
Re: Why build another website builder?
#78Earlier quoted context omitted.
Probably did some stock photography gig back in the day and now it's come to bite him -- looks like an endorsement.
He's actually childhood best friends with our co founder, Andrew! We needed a celebrity endorsement and Russell Crowe priced us out.
Re: Why build another website builder?
#79From https://www.makeswift.com/early-access : > Can I host a Makeswift site elsewhere? > Makeswift code can't be exported. Every page created in Makeswift is securely hosted and served via Google Cloud. I'm sorry, maybe I'm just being absolutist and cranky, but this doesn't sound to me like it's a 'website builder' - it's a tool that allows users to create presentations that can be displayed on the web. I get why you…
I consider Shopify a website builder, but I can't export my website to other hosting services.
Re: Why build another website builder?
#80Your own landing page takes 5.8!!!! seconds to load and makes 32 request: https://www.webpagetest.org/result/201020_Di60_34c239a225fda... The question should be: Why don't we create a website builder focused in web performance?