Splync v1.12 Introduced a Tip Jar

While Splync v1.12 focused on enhancing user-to-user communication through new notifications and badges, the next step is to strengthen communication between users and the developer. In upcoming versions, we plan to introduce dedicated feedback buttons so users can easily share their needs, suggestions, or concerns. Splync aims to grow in a user-focused, community-driven way, and open communication is essential to that goal. As a first step toward this direction, Splync v1.12 experimentally introduced a Tip Jar to support the developer. This marks the first time Splync has offered voluntary payment options. The app remains fully usable for free, and tipping is entirely optional. The Tip Jar does not unlock features, remove limitations, or provide any in-app rewards. Tipping in Splync is exactly what it sounds like—a simple gesture of appreciation. If you enjoy using the app and would like to support its continued development, we are grateful for your tip. It is a one-time, optional contribution, offered purely as a way to say thank you.

To clarify, Splync is built by a single individual. I design, develop, maintain, and promote the app as a solo entrepreneur. This blog is also written by one person and automatically translated into 42 languages with my Python + OpenAI API scripts scripts to save time. For now, I enjoy building everything end-to-end as a solo full-stack engineer. I am not yet sure how far I can go alone. One day, I may form a team to make Splync even stronger. There is a saying: “If you want to go fast, go alone. If you want to go far, go together.” Splync may eventually follow that path. While Splync is presented as a product with a collective voice, its development is currently driven by one person. For consistency and professionalism, this blog and the app often use “we” instead of “I.” Depending on the context, I may switch between the two. Regardless of wording, any support you offer through the Tip Jar is deeply encouraging and directly helps sustain continued development.

Implementing a Tip Jar in an iOS app may sound straightforward, but it requires careful consideration—both technically and philosophically. In Splync v1.12, the Tip Jar was implemented using Apple’s In-App Purchase (IAP) system with non-consumable, one-time products. From a technical perspective, the process starts with defining tip products in App Store Connect. Each tip option is registered as a separate product with a fixed price, clearly labeled as a voluntary contribution. No features are gated behind these products, and no in-app content is unlocked after purchase. This distinction is important, as Apple strictly reviews whether in-app purchases provide digital goods or functionality. On the app side, Splync fetches available tip products using StoreKit and presents them on a dedicated Tip Jar screen. When a user selects a tip, the purchase flow is handled entirely through Apple’s secure payment system. After a successful transaction, the app simply displays a thank-you message—no flags are stored, no user state is changed, and no privileges are granted.

Implementing a Tip Jar is not just about writing StoreKit code. It also requires clear communication with users, proper legal and financial preparation, and careful alignment with Apple’s App Review Guidelines. Even for a simple tipping feature, developers need to ensure that relevant agreements are in place and that a valid bank account is configured to receive payouts through App Store Connect. After completing all of these steps, I submitted the app for review. Nearly a day later, the status changed from “Waiting for Review” to “In Review.” I was excited—it felt like Splync was finally about to become profitable. However, just a few minutes later, the status changed to “Rejected.” My initial Tip Jar submission for Splync had been rejected. The rejection message referenced “Guideline 3.2.2 – Business – Other Business Model Issues – Unacceptable.” Apple stated: “We noticed that your app includes the ability to collect charitable donations within the app, which is not appropriate for the App Store, because your app uses in-app purchase to collect donations.”

In short, my Tip Jar was interpreted as a charitable donation feature. Under Apple’s policies, collecting donations through in-app purchases is not allowed unless specific requirements and approval processes are met. This was not my intention. Splync’s Tip Jar was designed purely as a voluntary tip for the developer, not as a donation to a cause or organization. The issue turned out to be wording. Phrases such as “support” and references to the “Splync community” unintentionally made the feature sound like a donation system rather than a personal tip. After revising the wording to be more explicit and direct, I resubmitted the app. The update was accepted without further issues. In Japan, where I live, tipping is not part of everyday culture. This experience made one thing especially clear to me: tipping and donating are fundamentally different. A tip is a personal gesture of gratitude toward a service provider, while a donation is a contribution made in support of a cause. That distinction matters—not only culturally, but also legally and within platform policies.

If you enjoy using Splync, you are welcome to tip the developer at any time. Tipping is entirely optional and does not unlock any features or benefits. It is simply a way to express appreciation, and any amount is sincerely appreciated. In the future, Splync may introduce a paid plan. Until then, the Tip Jar remains the only form of voluntary financial support available within the app.