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.
It's annoying to do, but if you can automate producing the initially wrong product for review it'd be easier.
End result: you end up having to redo the website. This tool helps get that Beta up even if just for the client to try it and show his friends/wife/boss
The benefit of automating the production of code is useful, and plenty of people would want that, but targeting the messaging at developers isn't going to work. I would have thought selling this tool to people who employ developers as a way to reduce the number of people they need is a far better route to market.
If designers have the ability to work closer to the web, more power to them. It should be our job as software engineers to make this as easy as possible and this tool could be one specific implementation.
If anything, by automating the process of producing code you're going to leave front end developers with nothing but meetings because the rest of the job is going to become a matter of pushing an AI-powered button. They won't thank you for that.
I've done something similar in the past (building models that translated paper drawings into HTML+css) and ultimately found it usually didn't save me much time.
Translating a look into code is much less labor intensive than it once was and code reuse and stylesheet preprocessers and the ilk (webpack, etc) save tons of time.
I'd get something reasonable out of the model but then the actual look and feel work came into play.
My next step was to be able to reference other sites for styling hints but ultimately I wasn't getting enough utility out of it to continue.
Do you find the same with this approach? If so, what plans do you have to take it the next few yards so it's a more comprehensive front end tool.
1. Something I made and let people use but nobody uses: https://comic2gif.com
There is one. If you click on "show today's" button. But I guess default should be changed to show instead of hidden.
> Plus, it would be neat if panels with more text were visible longer.
There is some logic in code to do that, amount of white pixels (in mask) is proportional to the time it appears. But maybe it needs tweaking.
If you do share I'm happy to give you feedback here if I have any!
I've used a few tools over the years that automatically generate code, mostly in C, but I've usually had to rewrite it as it never fits in with any decent coding standard
I would really love to see the output zip file, any change you have something less complicated that goes responsive to show?
The next step up has been pushing ML/DL/AI to do more sophisticated tasks and that means more sophisticated tools.
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 plate automatically for me. I learned a lot in the process, the actual site builder is a mathematical interpretation of a Sketch file and the DL model outputs what elements to include in what section.
To be completely transparent I'm not quite there yet. I'm only able to have ~90% of the site right. The other ~10% are misinterpretations or incorrect positioning of the elements. In order for this to work properly, it requires manual validation - which for my own projects I’m more than happy to do.
Even at this stage I think this tool can help others as well, so please let me know if you have any questions.
We can be more productive without repetitive tasks.
[1] Demo: https://zecoda.com/#demo
[2] Request early access: https://zecoda.com/#subscribe