Repository navigation
Replies: 1 comment
|
Appreciate the feedback. kodeWeave moved away from a CodePen style layout because it is designed for mobile first development. Split pane interfaces work well on desktop, but become cramped and less usable on phones and tablets. Instead, it uses a single responsive workspace where editing, preview, and tools adapt to the screen size. This keeps one consistent experience across mobile, tablet, and desktop rather than separate layouts or modes. That does make it less immediately familiar compared to tools like CodePen or Liveweave, but it is intentional and tied to supporting cross-device workflows. I’m open to ideas for improving clarity and onboarding, as long as they stay aligned with that direction. The tradeoff is intentional, but the first-time experience can still be improved. |
Uh oh!
There was an error while loading. Please reload this page.
It seems like a nice project, but its interface is terrible and unintuitive (disorganized, lacks labels, has a poor layout).
On top of that: the X logo. I hate criticizing developers—especially for an open-source project.
Yet why not adopt a layout similar to CodePen or Liveweave? Those interfaces require no learning curve; they are smooth and usable out-of-the-box.
This project feels like it’s ruined by this aspect, but I think there’s potential.
There aren’t many open-source tools on the market—maybe Playground (Linux GNOME but workstation only) is one exception.
All reactions