Engineers tend to misuse “minimalist” when they mean “brutalist” or “spartan”.
Minimalist in the code doesn’t reflect on minimalism on the interface, and when you apply an adjective to the description of your product you are characterizing the overall experience and visible surface (UI)… not the “backend” that makes it possible!
You can have very baroque UIs without writing that much code, and it would still be considered “minimal” on the code side.
I think in this context, minimalism doesn't mean "lacking important parts" like a keyboard or mouse produced by apple, but rather, something you can use without a graphical server, not gobbling up memory by embedding your program in a locally running browser.
Minimalist in the code doesn’t reflect on minimalism on the interface, and when you apply an adjective to the description of your product you are characterizing the overall experience and visible surface (UI)… not the “backend” that makes it possible!
You can have very baroque UIs without writing that much code, and it would still be considered “minimal” on the code side.