This is not the sort of repo I would present to the public. * There are no instructions on how to actually run the thing. * There is no requirements.txt or similar, so I have no idea which version of dependencies I'd need. * The repository is strewn with unnecessary files (.pyc/.ds_store/.so...), random-looking images with names like "plswork.png", a HTML file from some "starter kit"... * I can't seem to find the Rea…
Show HN: Don't code your UI, draw it
21–30 of 148 posts
Re: Show HN: Don't code your UI, draw it
#22Re: Show HN: Don't code your UI, draw it
#23Interesting idea, but I'm not sure I see any advantage over dragging movable/resizable components from a toolbar, but there are several obvious disadvantages.
Re: Show HN: Don't code your UI, draw it
#24This is not the sort of repo I would present to the public. * There are no instructions on how to actually run the thing. * There is no requirements.txt or similar, so I have no idea which version of dependencies I'd need. * The repository is strewn with unnecessary files (.pyc/.ds_store/.so...), random-looking images with names like "plswork.png", a HTML file from some "starter kit"... * I can't seem to find the Rea…
Re: Show HN: Don't code your UI, draw it
#25Interesting idea, but I'm not sure I see any advantage over dragging movable/resizable components from a toolbar, but there are several obvious disadvantages.
What if you could sketch your UI with a stencil, paper, and pencil. Then take a picture of it and have it translated into native components?
flow:success f1:s1->f1:s2->f1:s3
flow:error f1:e1->f1:e2
edit: another thought is that this concept could encourage people in your org who struggle with wireframe technology to express their ideas. Generationally and across culture, smartphone use is now accepted. People also know how to draw on pencil and paper. Now all you are asking them is a final DSL to express their thoughts. Lower barrier?
edit2: there is also something to be said for having someone step through their wireframe and flow control by taking pictures. It may take the abstract and create something tangible as they can logically piece their work together with actual pieces of paper?
Re: Show HN: Don't code your UI, draw it
#26It may not seem like much right now, but the fundamental idea behind this sort of stuff is the future, especially for front-end code.
Re: Show HN: Don't code your UI, draw it
#27Interesting idea, but I'm not sure I see any advantage over dragging movable/resizable components from a toolbar, but there are several obvious disadvantages.
What if you could sketch your UI with a stencil, paper, and pencil. Then take a picture of it and have it translated into native components?
Unless you mean just sketch using graph paper and translating coordinates. Not sure why I need a camera for that. :(
Re: Show HN: Don't code your UI, draw it
#28Earlier quoted context omitted.
From the readme, "This is not a prodution worthy piece of software,it is only meant for demo purposes"
It’s not that the code is not production ready. It’s more about first impressions. There are some really fundamental issues with the presentation. The first thing you do when starting a new git repo is create your .gitignore. I’m also not a Pythonista and I’ve only been working with Python for about a year, but including required packages in the requirements.txt is like Python 102.
Certainly there's a lot to be improved in terms of git hygiene and publishing an easy-to-try-out project, but it seems a bit excessive to say that the author shouldn't have posted it at all.
Re: Show HN: Don't code your UI, draw it
#29Earlier quoted context omitted.
What if you could sketch your UI with a stencil, paper, and pencil. Then take a picture of it and have it translated into native components?
Odds are high, mine would look worse. I'm not exactly an artist. Unless you mean just sketch using graph paper and translating coordinates. Not sure why I need a camera for that. :(
Re: Show HN: Don't code your UI, draw it
#30I think this is great. I see a future where designers can draw and create an interactive prototype. Anything beyond that is, my (educated) guess, long way off. Anybody hoping this will remove the need for designers or front end devs will be disappointed.
We are already there with Framer X and competitors pending launch in the near future. There is a learning curve that most designers are not super comfortable with yet, but I expect that will improve quickly. We also are limited currently to React for Framer X but I think opening it up to other front-end frameworks is on the horizon. Exciting times!