What You Can Do with Splync - MVP Features

On July 1, 2025, Splync v1.0 was released on the App Store. Releasing an iOS app means more than just coding—it also means passing Apple’s review process. Before an app appears in the store, Apple’s team carefully checks whether it meets their guidelines for functionality, design, performance, and safety. This review can be both exciting and intimidating, especially the first time. The good news is that your app does not need to be perfect. As long as it complies with Apple’s guidelines and includes minimum functionality without crashing, it will most likely be approved within a few days. The key is to launch first, see how it performs in the actual market, and then keep improving.

MVP stands for Minimum Viable Product. It’s a customer-focused approach rooted in lean startup, built around the build–measure–learn cycle. This cycle prioritizes validated learning, continuous improvement, and data-driven decision-making. I set out to build Splync v1.0 as an MVP because chasing “perfect” first can waste years only to discover there’s no real demand. So I planned to launch a minimal, reliable version—a simple budget tracker for couples that lets you enter and split expenses quickly—then watch how people actually used it. Don’t aim for perfection before launch. Instead, release your app, gather real user feedback, and use it to improve step by step.

At the same time of implementing minimum functions, I didn’t want potential users to find the app boring immediately. What could be a few aadditional key delights that differentiate my app from others? Splync envisions to be a budget tracker for couples to share expenses easily and enjoy living together. It should be a stress-free app: fast entry, frictionless splitting, and zero cognitive load. The UI design must be simple and intuitive. Data should sync in real time so partners always see the same numbers. And with a single tap, the app should auto-calculate and summarize who owes whom how much. Oh wait. What about security? Security isn’t a “later” feature.

Even for an MVP, Splync sticks to a few basics you shouldn’t skip. First, all app–server communication uses HTTPS/TLS—think of it like sending a sealed envelope instead of a postcard, so people along the route can’t read it. Second, we label users and projects with UUIDs—very long, random-looking IDs. “Guessing” a UUID is effectively impossible in practice. We also publish a clear privacy policy, like a sign at the entrance that says exactly what we collect and why. And for server maintenance we use SSH. You can picture it as a locked staff door that only people with the right key can open. In short, the foundation of Splync’s security was designed with care from day zero—and we’ll keep strengthening it as the app grows.

Splync works a bit like a private group SNS for money. You can add other Splync users to share expenses, and v1.0 already includes a QR code reader to connect quickly. Once your partner or friends are on your friend list, you can create a project for any money topic—monthly household budgeting, a holiday trip, a wedding ceremony budget, and more. You add expenses as they happen in just a few seconds. The project members see the same numbers in real time. In fact, Splync isn’t only for two people: solo projects and larger groups are also supported. At the end of a project, you can settle it to see who owes whom and how much. By default, splits are 50/50; custom splits (e.g., 60/40) are planned for later versions.

Imagine you’ve just paid at a sushi restaurant and you’re standing there while the staff prints your receipt. Splync says, “Don’t waste your time—or paper.” Open the app, tap “Add Expense”, enter the amount, pick a category, and you’re done in seconds (the date defaults to today). If you like, add a short memo, then tap “Save”—you’ll often finish before the receipt is even handed over. Splync v1.0 doesn’t include receipt photos or bank linking. Instead, it’s optimized for speed. Our purpose is stress-free shared expenses to help couples live more happily together. Fast entry now—Splync does the rest.

The MVP was ready, so I submitted the app to Apple. It was rejected once—nothing dramatic—because I needed to include valid iPad screenshots. I fixed the images, resubmitted, and two days later Splync v1.0 was approved and released on the App Store. There’s still a long roadmap ahead and more features are coming in future versions. For now, the app is free so as many people as possible can try it. Please share your feedback—what works, what doesn’t, and what you want next—so we can grow the Splync community together!