497 karma · joined June 29, 2019
https://twitter.com/joaodmj
It was the best decision I’ve ever made. In the last 3 months I found too many bugs and had incorrect assumptions. But learned so much because of all manual validation required to deliver projects. I now understand better my target market. Most importantly I’ve learned from actual paying customers [2].
We still don’t have the whole process 100% automated though. We are delivering projects, on average, within 48 hours (too much time IMHO). Our goal is to decrease the delivery time for 12 hours in the next quarter. To achieve this we need more training data and a better human validation workflow.
Because we have more under control - but really far from knowing it all - we are ready to launch publicly. Zecoda it’s a payed product because:
- We still have human validation
- We are solving a real world problem that has intrinsic value
- We are in the business of making our customers happy and will never ship bad code
What we guarantee is that, if you are unhappy with the results, we'll refund you. Hopefully we’ll be able to open a free tier in the future. Just need to reduce human verification to the minimum.
I’d love to hear your feedback and questions. This time you can actual try it :)
We can be more productive without repetitive tasks.
//
Sign up: https://zecoda.com/register
Demo: https://zecoda.com/#demo
Follow our journey: https://twitter.com/zecodahq
[1] https://news.ycombinator.com/item?id=20624140
[2] https://zecoda.com/#customers
PS - Have a great Thanksgiving everybody!
Regarding the output, it's great to know your thoughts on the frameworks. We actually went for a framework to make it simple for our users. In the future we want to allow our users to chose what output they want. So, it makes total sense.
Regarding the time for the optimization of the output, we are estimating ~20/30 minutes per page. It could be very faraway from the reality or pretty close, not sure yet.
Trying to answer all your questions:
- Our models learnt website's components visually (e.g. what is a navbar, an input, a button, etc)
- The output is a .zip file with the .html files and directories for css, js and img
- All Vue components can be found in main.js inside the js directory
- Vue components are built when 'duplication' is recognized (e.g. a sequence of cards or several links for a navbar). Nothing fancy
- CSS is vanilla, trying to ditch as many inline style as possible (working on it as we speak :) )
- All SVGs are imported with the img element.
Let me know if you have more great questions.
1. What's not enough in this current version for you to pay? What would make you be able to pay?
2. Do you have this problem recurrently? i.e. going from design to code.