Subscribe
Sign in
  1. Discussions
  2. What are the biggest pain points you have faced with the...

What are the biggest pain points you have faced with the no code website builders?

Pixelesq Team
7 replies
Would love to get your thoughts, opinions on how the experience has been with ever evolving no-code website builders. Couple of starter thoughts: - With google's emphasis on Core Web Vitals, performance and speed has been most critical to get ranked higher - Most of the No code builders offer freehand page building (design) - user is expected to be a designer to produce anything consistent and eye-pleasing. - The editors are way too daunting to use to milliard of options. - For the customizations each tool provides, the markup semantics go for a toss, so the html which is generated is not essentially optimized and semantic. What are the some of the pain-points you have faced and how are you solving it?

Replies

Gaurav verma
Substor
Substor
You are limited by the things they provide. If their website is down, so as yours. You need to play by their rules. I've used many tools to build websites but one thing which I hated the most was the limitations in every respect of website building. Switched to python and never looked back.
Share
Pixelesq Team
@gaurav_verma10 Great point about the coupled nature of these builders and the site which is deployed. The performance of the website also gets degraded, when you add more content or have more pages to serve. There's no doubt developing it yourself has the maximum control, but it also consumes ton of time, to build everything, optimize everything, to maintain. When you say python, is there a specific framework in python you chose? or was it all vanilla coding and managing the hosting/deploy on some providers?
Share
Gaurav verma
Substor
Substor
@devanandb I have used both django and flask. Personally I like flask. Super fast development. And you can use pythonanywhere to host it. They are dedicated for python. I agree that when you develop website on your own, there is tonn of work which needs to be done. But, only once. If you use a third party tool, you need to do this work everytime you do anything to it. Second, if the platform do any changes and it is not compatible with your build, you need to build again. This has happened to me. It's better to take headache of hosting than to check your website all messed up.
Share
Gaurav verma
Substor
Substor
/@software_guy @software_guy aarvy, substor, have you forgot about it? You've already done a great job. Thanks once again.
Share
Patrick Prasquier
I have built apps on Mendix and Bubble, neither of which being freehand-based. Although they have big advantages, they do share some pain points, among which: -Scalability: on the one hand, you DO have quick and easy access to scalability (both functional and technical); but on the other, you're limited by the range of how high it can grow. -Lock-in: if you want to move away (because you're not satisfied with the service, or whatever), you have to build your product again from scratch (although with a valuable experience of what did/did not work) -Access to high-quality developers may be hard. That's because the barrier to entry being low, anyone may market themselves as an expert after just a few weeks of using the platform; and independent certifications are not as common as for open platforms. Plus, those tools are not the best suited for efficient collaboration. My conclusion is: -No-code MAY be a fantastic solution depending on your use-case. If it fits exactly the ones the no-code framework was meant to serve, you should be fine. Anything a little extravagant and you should look at another solution -In most cases, no-code is still a fantastic tool for rapid-prototyping and testing your ideas on the market quickly.
Share
Pixelesq Team
@patrick_prasquier Thanks for sharing that. 1. Scalability: Completely agree with you on the scalability part, it is because of the way most of these tools serve and deploy the website. With JAMStack getting more main stream, there should be solutions to deploy static pages directly to edge, so they are lightning fast to load and can be scaled to thousands of pages without breaking your bank and sweat :) 2. Vendor Lock-in: Great point! You are right, there should be way where you can easily export or have it migrated to any other usable form, without re-building the entire stack! 3. Access to high-quality developers may be hard: Yeah if the appeal is for someone non-technical, why are the editors so daunting, and why do we have to be designers to come up with something which looks good enough. Again thanks for sharing your experience and views @patrick_prasquier . Please checkout and follow us (https://www.pixelesq.com) and do share any feedback you have, these are the exact problems we are trying to solve for no-code website builders.
Share
Software Guy (Aarvy)
@patrick_prasquier Hi, excited to know more about your tool. If you want me to review your product ping me at thesoftwareguy1994 at gmail.com with your name and product name as the subject.
Share