8 ms·
Hey all, I made this myself and am looking for feedback from anyone with time to spare some Thanks in advance!
by steve8708 7y ago
Hey all,
I made this myself and am looking for feedback from anyone with time to spare some
Thanks in advance!
- jklepatch 7y agoCool! You should post this on indie hacker as well. How long did it take you to complete this?
- steve8708 7y agoOh interesting I haven't heard of indie hacker, I'll check it out So far I've been working on this product for about a year and a half, though I did spend almost a full year beforehand just trying to figure out how to approach/solve this problem in the first place
- SteveMR 7y ago...I did spend almost a full year beforehand just trying to figure out how to approach/solve this problem in the first place I wanted to point out how smart this approach is for a project/idea this big. You hardly ever hear about the background work that goes into projects before the MVC is started. I can't imagine how many little problems/questions you needed to address before you made your first "official commit" Great job on this - it is seriously impressive work.
- o-__-o 7y agoContrast to my current job where they say “we don’t plan, we just build and iterate as needed” I point out swamp code and it’s “yeah I’ve been meaning to fix that but I don’t have time [fixing these 20 other debts we created]”
- MetaPrem 7y agoQuite nice! You may want to submit to 10words.io and producthunt.com also.
- quickthrower2 7y agoOne concern for you about pricing. If I stick a varnish cache or cloudflare in front of my site (or your api), I’m unlikely to need a big plan. Free plan could do for a very popular site. Maybe consider pricing by amount of content and requests?
- steve8708 7y agoYeah, your concern is totally valid. One thing that would hit people who cache the API is they would also be subject to fair use policies for bandwidth usage (namely serving the images used). Pretty much all CMSs have some form of this that basically requires large bandwidth users to pay for one of the higher price plans anyway so not to be losing money on customers That said if someone wanted to get real fancy they could comb through the content and replace the image URLs with some of their own. You are right, this will have to be sorted out if this becomes a common way people use the product. Thank you for the feedback
- quickthrower2 7y agoNo problems. What made me think of it wasn't so much trying to avoid paying for the service, but because I'd want to run a cache for speed of the initial page load. If you are serving your images from a CDN that would be compatible with my goal to keep the site fast. I don't think anyone would "could comb through the content and replace the image URLs" to save a few dollars, as the development effort would far outweigh the cost savings. So maybe you are OK there.
- abhishektwr 7y agoLooks great. Is this embeddable (editor) in other SaaS applications? This can open new opportunities.
- steve8708 7y agoThanks! And yes - this is actually totally doable. I've done it so far for platforms like Wordpress, Shopify, and Magento, as well as a couple custom internal admin tools of customers so far. It isn't something I have standard pricing and docs on yet but I am totally open to doing that. Do you have a use case in mind?
- darrenwestall 7y agoI’d also like to discuss this use case with you
- steve8708 7y agoHappy to, shoot me an email at steve@builder.io and we can talk more
- FlorianRappl 7y agoI also see this use case. Why? Ongoing "battle" between a large CMS (AEM) and a more modern SPA using microservices. Our claim is that the SPA is actually a superset of everything. It can SSR (like the CMS), it can also get data to display (like the CMS). All that is missing is a service for such data (we have other services delivering domain specific data). Now the problem is not in a data service, but rather in the whole infrastructure around it - to make it easy for an content editor to use. These people like drag and drop and they would love your solution. Great job!
- leesalminen 7y agoJust reached out to you on your intercom.io widget. Also interested.
- cityzen 7y agoYou should be proud of yourself.
- gitgud 7y agoAs in a single person made this? Even for a team of 10 that is simply amazing: - Attractive and professional landing page - Fully featured demo site, free to try - [1] Over 10 SDK's built for all popular platforms (react, vue, angular... etc)?!! I would be happy to have implemented just a fraction of what you've done... Like a sibling comment said; you should be very proud of yourself Get ready to scale :) [1] https://github.com/BuilderIO/builder/tree/master/packages https://github.com/BuilderIO/builder/tree/master/packages
- quickthrower2 7y agoYeah damn it’s good, I was assuming this was a company posting? Also the plans are good value. And backend/front end integration is well thought out. My concern for you is there are a lot of GUI site builders out there. So I wonder how this stands out?
- steve8708 7y agoThanks! I'm not sure what a company posting means but yes? Haha the company is just me anyway Your concern is totally valid, and I perhaps need to make this more clear on my landing page. But Builder is different because it works like a headless CMS. It can hook into any site to power page building, regardless of what tech stack that site was made with. So as opposed to other site builders that lock you into their system completely and can't hardly be extended with real code and engineers, Builder does this in reverse. Companies come to use my product when they have already built some kind of custom website, but need to provided non-dev users with the ability to quickly build and test pages. It just takes one simple API integration to make all that possible and retains your freedom to completely own your tech stack. Anyway, happy to elaborate further if you like! Edit: typos
- steve8708 7y agoThank you so much for the encouragement, it really does mean a lot
- codesternews 7y ago