We recently found one of those bugs users may never fully see but immediately feel.
Under a very specific timing condition, an inactive view could wake up and create two internal generations during what should have been a single loading transaction.
Read the update post here: https://spixor.com/updates/25-fl...
We originally planned to release Flex Forms earlier, but we ve decided to postpone the launch.
During the final testing and approval process, additional Google OAuth verification and security assessment requirements were introduced for some of the integrations we were preparing. Rather than rushing the release or launching a feature that depends too heavily on third-party permissions, we re taking more time to rethink parts of the architecture.
We ve been working on a stability and usability update for Spixor focused on two important areas: the builder context menu and Google login.
A smoother context menu inside the builder
The context menu is one of those features that should feel invisible when it works well. Right-clicking inside the builder should give you the right actions at the right time, whether you are working on the canvas, inside a view, on an element, or inside the layer tree.
Over the past weeks, we have been working on Spixor Redefined: a cleaner, more polished version of Spixor that improves the public website, dashboard, builder experience, authentication flow, light mode, support pages and overall product consistency.
This update is not about adding a huge new feature. It is about making Spixor feel more reliable, clearer and more ready for real users.
