Live data from Hacker News

Why build another website builder?

makeswift.com

41–50 of 89 posts

Re: Why build another website builder?

#41
post #28

I 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…

We're in the early days of Makeswift but extensibility is a big part of our vision. The way we've built the core technology of our product is such that every component used in the builder is just a React component (and could be a Vue component or Svelte component), and even the controls in the sidebar, which we call panels, are also just React components. With this architecture, we plan to expose a public API where developers can just build their own Makeswift components and share them with the world. Someone could build a Stripe Checkout component, for example. Somebody else could build a table component that pulls the rows from Google Sheets, or Airtable, or from a Zoho API?

We've spent a lot of time thinking about the right architecture to pull this off. Today, we're focusing on removing bottlenecks for marketers so that they can build beautiful websites with flexibility, fast. So because of that we are making all the components ourselves. In the future, though, we expect most components to be built by other people.

Re: Why build another website builder?

#43
post #40

Isn’t Squarespace or Wix aimed at people building websites with no code experience? Or is that not extensible enough?

Extensibility is a good way to sum it up, but there's many specific issues with each. The biggest problems we hear about with Squarespace are responsive layout overrides. The templates are also generally pretty rigid.

Wix's current editor is based on fixed position (think photoshop / illustrator). This approach works great for banners, graphics, icons etc, but is inherently at odds with web design. The solution for fixed position builders is to hardcode breakpoints, but there are too many devices. It's better to just design a UX around the box model, as that's how we code for the web anyways.

Editor X has potential but there's a little too much magic happening in the layout for my taste.

These are just a few of the many pain points. From our research, companies rarely keep using Wix / Squarespace after a certain stage. I personally haven't tried scaling a Squarespace or Wix site, but I also have never gotten them to a point where I was happy with all of the details before deciding to just code it myself.

Re: Why build another website builder?

#44
post #13
post #7

From 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.

Also Wix, Squarespace, and Weebly.

I didn't realize that all these services are actually presentations and not websites. Whatever that means.

The value of a tool like this without the backend and infrastructure is minimal. If you need to setup your own host and generate new HTML/CSS every time you'd like to update the site, the market for this product drops close to zero.

Re: Why build another website builder?

#45
post #38

How does this compare to other solutions in this space like WebFlow, Squarespace, or Wix?

I like to say it's 75% easier to learn than Webflow with 80% of the capabilities. Over time, we want to get that up to 95%. Webflow has an amazing product if you already know how to code. You can make award winning websites in Webflow, but it will take you time. Makeswift sites may not be winning any AWWWARDS (yet), but you'll be able to build something good in a fraction of the effort. In addition, other people on your team can learn it as well, parallelizing your throughput. If speed is top priority, then our product is for you.

Squarespace and Wix are great for people who want to set up a template, skin it, and forget it. Their focus on wizards and templates optimizes the user experience for beginners, but at the cost of flexibility for advanced customization. There are a lot of people that this makes sense for.

Makeswift is designed for opinionated people who are constantly tinkering with design, layouts, and new ideas, but don't want to climb a giant learning curve. We're focusing on making a generic, flexible user experience with composable components that doesn't have opinions about how you build your pages.

Re: Why build another website builder?

#46
I built the website builder in WeBase [1] mainly because I felt like current solutions were just so bloated.

Another reason I think WeBase is unique is that it also supports custom data models (think Airtable) that you can integrate with a website which often requires multiple tools with other platforms.

Even in mature markets there can be great opportunities for innovation.

All the best with Makeswift!

[1] https://www.webase.com

Re: Why build another website builder?

#47
post #42

Jerry from Walking Dead in the Request Access page?

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?

#48
post #40

Isn’t Squarespace or Wix aimed at people building websites with no code experience? Or is that not extensible enough?

Extensibility is a good way to sum it up, but there's many specific issues with each. The biggest problems we hear about with Squarespace are responsive layout overrides. The templates are also generally pretty rigid. Wix's current editor is based on fixed position (think photoshop / illustrator). This approach works great for banners, graphics, icons etc, but is inherently at odds with web design. The solution for f…

Wix has a responsive layout from what I've seen as a casual maintainer of a rather large Wix site, which was originally built by a non-coder. Maybe it was part of the template he used, but a row of 3 images on Desktop automatically becomes a column of 3 images on mobile, and the top menu turns into a hamburger. You can also switch to mobile mode while editing to adjust the layout of the mobile version.

Re: Why build another website builder?

#49
post #35

Earlier quoted context omitted.

Thanks for sharing your project, certainly looks like an interesting start! Quick feedback, it seems you forgot to answer the question "Why build another one" before submitting your comment, I'm still awaiting your answer :)

I'm guessing they are referring to the article linked on this submission.

Yep, that's right. I can see how that would be confusing though, thanks for the feedback.
Post reply on HN