How Splync v1.12 Envisioned Better Communication Infrastructure

Splync v1.12 marks the foundation of user-to-user communication within the app. Although the initial vision for this upgrade was to improve user-to-developer communication, it became clear that Splync needed to better support communication between users themselves. One of the most important steps toward this goal was enhancing the notification system. In earlier versions, notifications were limited to friend requests and project settlement requests. While functional, this was not sufficient for smooth and timely collaboration. With v1.12, Splync introduces new notification types, including friend acceptance notifications and project invitation notifications. These additions ensure that users are immediately aware of important actions taken by others, without needing to manually check each screen. Furthermore, new “New” and “Updated” badges now appear when project members add new expenses or edit existing ones. This helps project members stay in sync with ongoing changes.

Previously, when a friend request was accepted, the sender received no explicit confirmation through a notification. Users often discovered the change only by revisiting the friend list, which could feel unclear and ambiguous. This behavior remained unchanged since Splync’s debut on the App Store as an MVP (Minimum Viable Product). At launch, friend request notifications were considered essential, while friend acceptance notifications were treated as a lower priority. As Splync evolved, however, it became clear that the app needed to be more socially responsive. In v1.12, Splync now sends a clear notification when a friend request is accepted. We believe this small change improves clarity and trust between users. Every new connection now has a visible “moment,” allowing users to feel acknowledged and connected. In hindsight, it’s a little surprising Splync didn’t have this from the beginning.

When Splync v1.0 launched, we assumed that most users would communicate outside the app. As a result, project invitation notifications were also treated as a lower priority. However, there are situations where users rely on in-app notifications. More importantly, this is not just about functionality, but also about emotion. Being invited to a project is more than a technical action. It is a social signal. Since collaboration in Splync revolves around projects, a project invitation represents a key moment. With v1.12, Splync introduces project invitation notifications, ensuring users are immediately informed when they are invited to join a project. This reduces friction, prevents missed invitations, and makes onboarding into shared budgets smoother. We have also received early user feedback requesting the ability to explicitly accept or decline project invitations, and this is a feature we are likely to introduce in a future version of Splync.

Some users expressed a desire to receive notifications when project members make updates within a project. This feedback made sense. We initially thought about adding a new type of notification. However, receiving notifications every time an expense is added or edited could be annoying. Instead of increasing notification volume, we explored an alternative approach. In Splync v1.12, “New” and “Updated” badges now indicate changes within a project, allowing users to understand what has changed at a glance without unnecessary interruptions. To support this, I introduced a mechanism to track each user’s last project view. By comparing this timestamp with the latest expense updates, the app determines whether an item is new or updated. After refining the design and simplifying the badges to symbols only, the result became a clean and intuitive visual cue. This approach strikes a balance between awareness and calm, keeping users informed while respecting their attention.

Splync uses MariaDB as its primary database, and notifications are treated as first-class data, not ephemeral events. Each notification record stores the sender ID, receiver ID, notification type, read/unread status, and creation timestamp. This structure allows Splync to reliably reconstruct what happened, when it happened, and who should be aware of it. Rather than relying on real-time messaging systems or external notification services, Splync intentionally keeps notification logic simple and deterministic. Every meaningful social action—such as accepting a friend request or inviting someone to a project—creates a concrete record in the database. This makes notifications auditable, debuggable, and resilient, even if a user opens the app days later. On the other hand, the badge system for project updates follows a different approach. Instead of generating a notification for every expense addition or edit, Splync records when each user last viewed a project. To support this, a new column was added to the project member table to track each member’s last viewed timestamp. By comparing this value with the most recent expense updates, the app can logically determine whether an item should be marked as “New” or “Updated.”

With the introduction of new notification types and the New/Updated badge system, Splync v1.12 becomes more socially responsive and interactive. These changes help users stay connected and aware, making shared expense management feel more natural and collaborative. We hope you enjoy sharing expenses with your partner, friends, and family through Splync. Looking ahead, we plan to continue refining communication features and may introduce additional notification types to further improve clarity, trust, and overall user experience. Your feedback is always welcome.