5 ms·
It would be interesting to see the quality of the code. Way back in the 90s Macromedia had a product called Fireworks, which Adobe subsequently bought (along wi
by monkeynotes 7y ago
It would be interesting to see the quality of the code. Way back in the 90s Macromedia had a product called Fireworks, which Adobe subsequently bought (along with Flash, Dreamweaver etc.). It could turn designs into HTML+CSS but the code was horrible and no-one used it professionally.
I know we are decades past that, and the machine learning algos may do a better job but without seeing some code examples it has limited appeal to me.
I don't really know the kind of person that has to turn around so many websites that the boilerplating exercise is a big enough problem to pay to solve. I can see the appeal to people who have no experience building websites and a company like Wix might be interested in the tech. But professionals who need a monthly subscription has to be a tiny niche.
Impressive all the same though, what you have learned in doing this will lead to other great things I am sure.
- johndamaia 7y agoThanks so much for your words. Happy to share our demo code, would love your feedback. If you think it makes sense, drop me a line at john [@] zecoda.com
- halostatue 7y agoIt might be easier, since this is targeted at developers, to make a GitHub repo with both the Sketch files and the generated code so that we can determine whether this is something that we’d benefit from. From my perspective, one of the difficulties I’d have is that we already have a pretty extensive Vue application, but we _still_ have problems with translating updates in place. So, we’d want to be able to compare one of the screens we have with one of the screens generated (and our designers tend to create multiple Sketches to illustrate different state possibilities). The next question would be how updates might be flagged to minimize code churn after initial generation.