Splync v1.6 — Question and Answers Enriched

Being intuitive is part of Splync’s vision as the simplest shared budget tracker app. If new users understand how to use Splync without reading anything, that is the best: completely stress-free. However, one of the hardest things as an app developer is being objective about “intuitiveness.” To me, every action in the app feels obvious, because I designed the interface based on my own intuition — and in the end, I am the one who created it. For new users, though, some features are not immediately clear. As mentioned in the previous article, Splync v1.5 introduced a major upgrade: customizable split ratios per project and per category. It was a powerful feature, but naturally it added a layer of complexity to the interface. To keep things approachable, we added information buttons that guide users to concise Q&A sheets. With v1.6, we expanded on that idea. This update deepens the helper content both inside the app and around it — a step toward reducing confusion, answering silent questions, and making Splync feel intuitive even as the feature set grows.

I added a section-wise list of Q&A items. In the create and edit project views, the questions include things like “How can I add my friends to the project?”, “Can I set different shares for each category?”, “How do you handle rounding differences?”, “How do I sort categories?”, and “How can I adjust the number of decimal digits displayed?” I tried to list as many questions as possible, but it’s easy to imagine that it may be impossible to cover all the possible questions. For now, the Q&A is written purely in text. It works, but I’m starting to think illustrations or small diagrams might make the answers even more intuitive. The key is that users should never feel stressed while searching for an explanation — the structure itself should guide them smoothly to what they need. I’m still experimenting with other layouts and even dynamic approaches so that answers appear naturally when questions arise.

Unlike a fun puzzle you want to sit with, most app users expect their questions to be resolved instantly. Back when I worked as a Customer Experience Manager in global companies, the KPIs (Key Performance Indicators) and SLAs (Service Level Agreements) were broadly divided into two groups. One group measured speed — waiting time in the queue, response time, and resolution time. The other group measured quality — customer satisfaction and dissatisfaction rates. Both matter, but one principle was always clear: the most satisfying support experience is the one the user completes on their own, before they even think of reaching out. That idea shapes how I design Q&A inside Splync. If someone wonders “How do I add my partner?” or “What does Settle actually do?”, they shouldn’t need to send an email or wait for a reply. The answer should already be there: clearly written, calmly placed, easy to notice. Q&A becomes the first and most efficient contact point, reducing friction and helping the app feel lighter, friendlier, and more intuitive.

Even as I continue enriching the Q&A, I still believe intuition is the real foundation of a stress-free app. Q&A is the first contact point when questions arise — but the ideal state is one where questions never arise in the first place. That is the direction I want to take Splync in future versions. There are several approaches I’m exploring. One is lightweight onboarding guidance: not a long tutorial, but a gentle first-time flow that highlights only the essential actions so users feel oriented from the start. Another is subtle in-place hints that appear only when needed — tiny signals inside the UI that guide users without interrupting them. I also want to refine microcopy throughout the app, because a single clear phrase can prevent a question from forming at all. Adding an escalation button may also be useful for users who prefer direct reassurance. The goal is to gradually raise Splync’s intuitiveness so that the app explains itself, quietly and naturally. Q&A will continue to grow, but it is only one layer in a broader journey toward eliminating friction and making every interaction feel effortless.

And there is another layer I look forward to: community. Once Splync gains more users, people will naturally start sharing tips, shortcuts, and best practices with each other. Intuition can become collective — a shared understanding that emerges not from documentation, but from how real people use the app and help one another. That, too, is part of the long-term vision for a truly stress-free experience. In that sense, Splync grows together with its users — shaped not only by code, but by the community that gathers around it.