Auto-Save Configuration Changes
The save button is a concession to unreliability. In a reliable system — one where changes persist immediately and correctly — there's no reason to make users explicitly commit each change. The act of making the change should be the act of saving it.
Configuration auto-save in Swifty eliminates the save button.
Changes Persist Immediately
When you make a configuration change — add a field, adjust a column, change a status option, modify a layout — the change is saved immediately. No button to click, no confirmation needed for routine changes.
The next time anyone loads the affected page or form, they see the updated configuration. There's no publish step, no "apply changes" workflow. Configure and move on.
No Lost Work
The most common cause of lost work in editing interfaces is closing a tab or navigating away before clicking save. Auto-save eliminates this risk entirely. Because every change is saved as it's made, there's nothing to lose when the browser closes.
Recovering from a browser crash, closing a tab accidentally, losing a network connection — none of these scenarios result in lost configuration work. What was saved is what was done; what was done was saved.
History as the Undo Mechanism
Without a save button, there's no "cancel and discard" action. Changes are committed immediately. The question becomes: how do you undo something you didn't mean to do?
The answer is configuration history. Every change generates a history entry, and every history entry can be reverted. The history system provides a complete, granular undo mechanism — more powerful than a simple cancel button because it works across multiple changes and is available long after the session ended.
Visible Confirmation
Auto-save doesn't mean silent save. A brief confirmation indicator — a checkmark, a brief "Saved" flash — confirms that a change was persisted. The confirmation is subtle enough not to interrupt the flow of configuration, but visible enough to provide confidence that the change was received.
When auto-save encounters an error — a conflict, a validation failure — the error is shown prominently so the issue can be resolved. Silent failures don't happen.