121–128 of 128 posts
I'm curious how you are handling ambiguity in the original design. Does the algorithm create multiple variants when something could be interpreted in multiple ways, and then the manual validation part of the process involves picking from among the different variants that the algorithm created?
Hi John, great idea but the demo didn't really convince me. How much of the system relies on engineers cleaning up the code? And I can't get past the fact that it becomes a responsive site, is the logic in the responsive design in the Sketch file too?
Your rates are higher than paying someone (offshore) to convert the artboards - why? Should be much cheaper if it's automated.
Hi John, great idea but the demo didn't really convince me. How much of the system relies on engineers cleaning up the code? And I can't get past the fact that it becomes a responsive site, is the logic in the responsive design in the Sketch file too?
Hey! No worries, I'm starting to like the skepticism, it makes the job funnier. Right now we are doing it right ~90% of the whole page. The responsiveness is done by the system automatically (it makes decisions on its own, therefore they could be wrong). No need to have it on the Sketch file.
But seriously, I hope you guys do well, thanks for responding to all these skeptical comments
This is very interesting. I love the approach to the problem that you are trying to solve. However, there are few questions that I will try to answer with respective to the product. Q. Will I pay to use your problem? A. Probably not, with the current version Q. What problems I see with the platform? A. I seriously don't know how you'd proceed forward with the platform. If it would only be used for creating static web…
Even if you wouldn't pay for this I know a lot of high-revenue generating businesses that would. The time savings afforded by this tool (if it works) would be incredible.
Earlier quoted context omitted.
Cool, thanks for the reply. For me making components is the hard work, anything that helps automate organizing / naming / and synchronizing a component library with sketch sounds intriguing to me. Is the output intended to be code-edited by a developer to add hrefs, interactivity? Is it intended to generate pseudo components for later finessing or is it intended to produce the final outcome of a site directly from sk…
It's intended to be code-edited by a developer. The goal is to have an advance starting point. You'll start with "everything" ready to work on the fun stuff. If you curious enough to see the output I'm happy to share the code from our demo. If it makes sense drop me a line at john [@] zecoda.com
Your rates are higher than paying someone (offshore) to convert the artboards - why? Should be much cheaper if it's automated.
Wow, do you know developers that convert artboards to full webpage for $9? But I understand your point, we are intentionally pricing it at a high point. Hopefully we'll be able to decrease it in the future.
Is the home page itself built with this? Can you share the input file and an estimate on how long it took to work with the output to make it production ready?
Most of the website was started with the model. However I was learning along the way, so most pages were fairly changed. 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.