We have several actions laid out on the screen with colliding priority. We have a fallback to the previously published state, a Save, a Publish and a Preview.
Another layer to the problem is navigating from the embed settings page to check the URL Parameters on the URL tab discards all changes, forcing the user to memorise all of the exact names of URL parameters.
Moreover, we develop the platform by focusing on features, and we often fail to improve on recurring patterns regarding mechanics.
The most common persona expected is a CX/Market research expert or someone with developer skills to fill in the dev-related parts of the settings. These two personas will probably cooperate and it is necessary to do so without publishing the settings.
Problem to solve: The feedback that the user CAN modify this settings while the live settings remain untouched.
We agreed on not implementing the Autosave functionality as building this would require introducing a massive system rather than using what we can currently implement with the most improvement by the least effort.
We went with no grouped primary actions, as a better button layout worked better.
I'm a product designer specialising in SaaS web-app solutions. I enjoy working in all parts of a product's cycle and am comfortable taking concepts from a whiteboard to a highly detailed prototype flow, keeping the End-User in mind.
Cheers,
I'm looking forward to working with you!
