What we’re working on next: making Spixor smoother, clearer and easier to use
Over the last phase, we spent a lot of time stabilizing the core builder experience. A big part of that work was focused on undo/redo, history handling, page switching, builder state consistency and several smaller bugs that could make the editing experience feel less reliable than we wanted.
Those fixes are important, because Spixor should feel safe to use before we keep adding more visible features.
Now we’re moving into the next step: improving the overall product experience.
This phase is focused on three areas:
A better public website: We’re reworking the Spixor website so it explains the product more clearly, feels more polished and better shows what Spixor is becoming. The goal is to make the website feel more alive, more visual and more useful for people who are discovering Spixor for the first time.
A refreshed Settings panel: The Settings panel is one of the most important parts of the builder, but it needs to become cleaner, easier to read and easier to work with. We’re improving the structure, spacing, labels, visual hierarchy and overall flow so users can understand their options faster.
A smoother and more readable Builder: We’re also improving the Spixor Builder itself. That means better readability, cleaner panels, smoother interactions, clearer controls and a more fluid editing experience. The goal is not just to add features, but to make the existing experience feel calmer, faster and more professional.
This is the phase we are working on now. For us, Spixor is not only about building a website visually. It is also about giving users a workspace that feels clear, reliable and flexible.
Before we move into bigger feature releases, we want the foundation to feel right. We’ll keep sharing updates as we improve the website, refresh the Settings panel and continue polishing the Builder experience.
As always, feedback is welcome. If there is something you think a visual website builder should make easier, we’d love to hear it.
Replies