31–40 of 128 posts
Earlier quoted context omitted.
Can you please clarify what you mean by "single one"? You'd pay $30/40 for how many pages of one site?
As in using it a single time - I guess maybe at most 2/3 pages from one design?
Hi. Wish you had one-off pricing. I'm sure there are agencies that do that kind of volume. I would love to use your service a few times a year.
I built a thing like thi, and went quite a long way down the commercialization path. The problem is that round-tripping is what almost everyone wants, and it's really hard to get to work.
Can you elaborate on what you mean by round-tripping please?
At least that was one issue i thought about reading OP.
This is really cool, it is really hard to evaluate the value of Zencoda without the code output of the demo. I get that the full product is not ready but being able to see the input and one good output would tell us a lot.
There's a useless vertical scrollbar on desktop.
Founder here. As a front end developer, I turn design files into front-end code regularly. But it's a repetitive and demotivating task. It takes time, lots of meetings and boring back and forth questions. I want to change that. So I tried to automate this process. I trained a deep learning (DL) model to visually understand what elements are in a webpage (e.g. input, button, nav, etc) and build the front-end boiler pl…
So I tried to automate this process.
The reason for all the meetings and questions is that the designs you're working from are ambiguous, and you don't really have enough information to turn the design files in to working code. I can't quite see how a deep learning model solves that problem. By the sounds of it you've automated turning the original, ambiguous, wrong designs the you have at the start in to code and tried to remove the discussion process that takes those files and turns them in to the right solution to the customer's problem. This is not going to lead to better front end code.