Hacker News

I think a successful product strategy can be "build something you love, see if others love it too". If that's enough customers, you can judiciously expand out from there. The "fail honestly" method.

I think the Apple II is one example of this.

> Joel Spolsky said (I'm paraphrasing) that everybody only uses 20% of a given program's features, but the problem is that everyone is using a different 20%, so you can't ship an "unbloated" version and expect it to still work for most people.

To me this is an argument for more apps that do less extremely well instead of a handful of apps that do everything poorly. There's nothing wrong with a tool that's honed for very specific user. They'll never hyperscale, but that's also fine.

Or then again maybe they can. Google Docs is plenty popular despite being closer to WordPad or TextEdit in terms of functionality than it is to MS Word.

"everyone is using a different 20%"

In my experience, what people use is very malleable to how easy/good the flows are they are presented with. Given 100 equal options, they might use 20, and nobody picks the same 20, but given 25 options, 20 of which present a very good experience, almost 90% will go with those 20 without complaints.

A quick web search suggests that you are probably paraphrasing a newsletter [1] that Joel Spolsky published in 2001. He was talking about software like Excel (of which he was the Product Manager) and Word. Maybe a tool that is more focused on a narrower task (like UI design) can be less "bloated"?

[1] https://www.joelonsoftware.com/2001/03/23/strategy-letter-iv...

Makes me wish more apps had feature toggles

I feel like HTML and CSS could remove 90% of the functionality and only affect 1% of developers, then we could get some actually good web browsers.

I think you’re missing the point a bit. Not every tool needs to be Figma, and honestly, that’s a good thing.

I’ve been using Figma for a while, and true, it’s powerful. At the same time it becomes increasingly complex, difficult, bloated overall. Simple tasks now require navigating through multiple menus, and the learning curve for new users is steep (took me a while to understand it, and the same experience had it acquaintances of mine). Sometimes I just want to sketch out an idea or make a task without dealing with all that overhead.

The no plugin support thing actually makes sense to me. I’ve had Figma slow down or crash because of poorly maintained plugins. Having a tool that just works, consistently, without worrying about plugin compatibility or security issues? That’s valuable. And yeah, it’s a solo developer versus a massive company (that’s my understanding) but that is why it’s beautiful. Also it’s an uneven comparison if you ask me (but didn’t :)) ).

However, the fact that this is even being compared to Figma shows the quality of what’s been built. Not everyone needs enterprise features. Some of us just want a clean, fast canvas without the friction. Every new feature of Figma feels like an attempt to monopolize the entire market.

I think he did an incredible job. Good work. This has value.

People ship stuff that doesn't make sense at first blush all the time. But how are they ever supposed to even get into the space if they don't try something? Try to get some customers, see what people want. On day one, he's not saying he's going to compete with Figma. He's just getting it out there. Your comment—You could say you're just asking questions or giving constructive criticism, but it just assumes the negative on so many levels. I can criticize your viewpoint. Why do you think someone should have a product that's ready to compete with Figma on day one? Do you seriously expect him to have an answer for that?

There is space for this. The things you list as negatives are positives. Feature parity or similarity to a big competitor? A plus. Single developer? For a certain kind of consumer, a plus.

Thank you, and I know exactly what you mean. I myself have rewritten the entire engine ar least three times until I was happy with the performance and the overall outcome. It’s been a long learning experience. As a developer at heart, this project scratched every itch I had from a software engineering perspective :)

Are any of your prototypes published or available to view?

If you're looking for an open-source and self-host option then you might to checkout https://penpot.app/

Sketch is offline first but has a really stellar online app as well.

An MCP server is definitely on my radar. I've seen some really cool workflows coming out of Figma too. Being a one-man show though, prioritizing what to build next is always the tough part. But it's on the list, appreciate your suggestion!

Thanks for reporting, I'm looking into it.

It's a wireframing tool akin to figma. You create the design for your website/app there, then hand it over to a programmer who implementd it in html/react/flutter/wpf/etc

Thanks for this question. I'm humbled by the comparison. I have been following penpot for a while and I appreciate the work they've been doing.

The main difference lies in the rendering engine. Penpot relies on an SVG engine, which limits performance as project complexity grows.

Vecti is built on canvas and WebAssembly (the same architecture used by Figma). This gives us raw performance advantages, allowing you to handle complex, heavy design systems without the lag you might experience in SVG-based tools.

Thanks a lot. I appreciate it. It’s been quite a journey.