PenPot and native input elements

Hello everyone! I stumbled upon Penpot after listening to a Whiskey Web & What Not podcast, the app sounded amazing to me. I’ve been a long time advocate for better design / dev collaboration, and better design to dev hand off. I’m also a huge advocate for something I like to call “Codotyping”, aka building functional prototypes with code to make the user testing process that much better.

Which leads me to my question. I’ve been hearing a lot about the penpot flexbox/css grid implementation which is going to use both of those layout tools under the hood, this is amazing in my opinion. Will designers also be able to create real input components as well (text fields, selects, checkboxes, radios, etc)? One of the most annoying things about all of the static design tools out there (figma, invision, sketch, XD, etc), is that nobody has figured this out. I work with teams that build very dense form based applications, and user testing those apps with static design elements is not great. This is why I codotype with stackblitz or astro, and host my prototypes in Stackblitz or Netlify. I can put together a prototype super quickly with code, adjust it, toss it away if needed, and so on. It also allows users to actually tab through the form, type things, and it feels more real, which is key for user testing IMO.

Anyways, sorry for the long winded post. I Can’t wait to dive into Penpot!

3 Likes

At the moment, penpot does not use native input components. I created an request for this a while back. I guess that the only thing such elements would do is allow typing in user testing; more complex interactions would demand a Axure/Flash style application and are often quicker to realize in code in the first place.

2 Likes

(updated the issue with some more information and links to existing tools)