Splync 1.16 Enables Project Soft Delete

Users had been asking for a simple way to delete projects, especially when a project was created by mistake or used only for testing. Technically, there was a workaround. Users could settle the project and then archive it, which removed it from the active project list. However, this process was not intuitive and did not truly solve the problem. The project still existed. It was only hidden from the active project list. For users who wanted a clean slate, this created unnecessary friction. Deleting something should not require multiple steps or leave lingering data behind. With Splync 1.16, that changes.

Instead of permanently deleting a project right away, Splync now uses a soft delete system. When you delete a project, it is removed from your active project list immediately and kept in a deleted state for 30 days. During that period, you can filter your project list by Deleted to find and restore it at any time. This approach gives you more flexibility without adding risk. Accidental deletions no longer need to become permanent mistakes. Even if another project member deletes a project without your consent, you will still receive a notification that the project was deleted.

After 30 days of retention, the project is fully removed from the database. Behind the scenes, Splync manages project data with MariaDB. Deleted projects are stored in a soft-deleted state for a limited retention period, and MariaDB’s event_scheduler automatically removes the project data after 30 days. This cleanup process does not require any manual action from you or the developer. The retention period and final deletion are handled automatically at the database level. Once the retention period ends, the project is completely deleted from the database and from your app. This design keeps your workspace clean while still giving you a safety buffer.

Splync has been gradually making common actions faster and simpler. In version 1.14, I added expense deletion with a left swipe on the expense list. In version 1.15, I added project cloning with a left swipe on the project list. In Splync 1.16, project deletion follows the same idea. From the active project list, just left-swipe the project you want to delete. You will see two options: Delete Project and Copy Project. Once you tap Delete Project, the project status changes to Deleted and it disappears from your active project list. But because this is a soft delete system, the project is still recoverable. If you filter the project list by Deleted, you can find it again at any time during the 30-day retention period. Restoring it is just as simple as deleting it: left-swipe the project and restore it from there.

On the surface, deleting a project sounds like a small and obvious feature. It is the kind of thing many users expect to be there from the beginning. But in practice, implementing it properly is not as simple as adding a delete button. A good deletion feature has to balance several things at once. It has to feel simple in the moment, because users should be able to remove an unwanted project without friction. At the same time, it has to protect data, because accidental taps and unapproved actions in shared projects can happen. Splync is designed to help people manage shared spending with ease and trust. That means users need to feel confident that their data is handled in a predictable and responsible way.

Splync learns and grows through user feedback. Splync is highly user-focused. Every insight matters, and every comment helps improve the app. User feedback is one of the most valuable parts of developing Splync. It shows what works well, what feels confusing, and what users want next. Many improvements come directly from these voices. In upcoming versions, Splync will make it easier for users to share their opinions, ideas, and bug reports. The goal is to improve the app faster and build a stronger Splync community. Spend Better Together!