Lubble: Couple Calendar&To-do

The Onboarding Reality: Two People, One Space

Opening Lubble for the first time presents a clean, aesthetic interface designed for two. The app immediately prompts the user to invite a partner. There is no solo mode. This is a deliberate design choice. The app is built entirely around the concept of shared space. Once the partner is invited and accepts, the shared calendar appears. The calendar displays both personal and shared schedules. The user can add events, set reminders, and view upcoming dates. The interface is intuitive, with a focus on visual clarity. The app's color scheme is soft and modern, designed to appeal to couples. The onboarding process is minimal. There is no lengthy tutorial. The user is expected to explore and discover features naturally. The app's core philosophy, as stated by CEO Donghwan Kim, is "experience design" rather than functionality. The features—calendar, countdowns, notes, photo sharing—do not exist separately. They are integrated into a single, cohesive space. The user can add widgets to the home screen for quick access to the calendar, to-do list, and countdowns. The app also supports stickers for personalization. The onboarding is smooth, but the app's reliance on a partner means it is useless for single users. This is a limitation, but it is also the app's defining characteristic.

The app's subscription model is introduced during onboarding. The app offers a free version with core features. However, decorative elements—such as themes, stickers, and additional customization—are locked behind a subscription. The subscription does not lock essential functionality. This is a user-friendly approach. The user can use the app indefinitely without paying. The subscription is for those who want to personalize their space. The app's pricing model is transparent. The user can see what is free and what is paid. The app does not use aggressive pop-ups or dark patterns to push subscriptions. This is a positive aspect of the app's design. The onboarding experience is focused on connecting with a partner and setting up the shared space. The app's design encourages users to start using it immediately. The onboarding is a reflection of the app's core value: shared experience.

How Shared Calendar and To-Do Work Together

The app's core workflow combines the shared calendar with the shared to-do list. A couple can plan a trip using the calendar to mark dates and the to-do list to track tasks. For example, they can add a flight date to the calendar and create a to-do item for packing. The calendar and to-do list are integrated. The user can see tasks on the calendar view. This integration is not explicitly described in the Play Store description. The Play Store mentions both features separately but does not explain how they work together. In practice, the shared calendar and to-do list create a comprehensive planning tool. The couple can manage their daily lives, from grocery shopping to vacation planning, all in one app. The to-do list can be used for shared responsibilities, such as household chores or bill payments. The calendar ensures that both partners are aware of upcoming events. This synergy is the app's key strength. It reduces the need for multiple apps. The couple can use Lubble for all their shared planning needs.

The app also includes a diary feature for documenting memories. The diary is separate from the calendar and to-do list, but it is part of the same shared space. The couple can write about their experiences and attach photos. The diary serves as a digital scrapbook of their relationship. The countdown feature adds another layer. The couple can track important dates, such as anniversaries or birthdays. The countdown appears on the home screen widget. This integration of planning, task management, and memory documentation is unique. It creates a holistic view of the relationship. The app's design encourages the couple to use all features together. The user can plan a date using the calendar, create a to-do list for the date, and then document the date in the diary. This workflow is natural and intuitive. The app's focus on integration is its main differentiator. It is not just a calendar app; it is a relationship management tool.

The Real-World Performance: Permissions and Stability

The app's performance is generally stable. The latest version, 3.0.2, was updated on July 12, 2026. The update frequency suggests ongoing maintenance. The app's size is around 108-109 MB, which is reasonable for a feature-rich app. The app requires Android 6.0 or higher. However, the app's permission model is a concern. The Exodus Privacy report for version 1.0.11 lists 23 permissions, including CAMERA, RECORD_AUDIO, READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE, USE_BIOMETRIC, USE_FINGERPRINT, and POST_NOTIFICATIONS. This is a large number of permissions for a calendar app. The app also includes one tracker for analytics. The developer states that data is encrypted in transit and that users can request data deletion. However, the app may share personal information, photos, and videos with third parties. This is a significant privacy concern. Users should be cautious about what information they share through the app. The app's permission model is a potential drawback for privacy-conscious users. The app's stability is adequate. There are no major crash reports in the research log. The app's performance is consistent with its purpose. It is a lifestyle app, not a high-performance gaming app. The occasional lag is acceptable. The app's real-world performance is a mixed bag. It is functional, but the permission model is a red flag.

The app's changelog for the latest update mentions fixing issues with calendar photo display and holiday settings save problems. This suggests that the app has had bugs in the past. The developer is actively fixing them. The app's user reviews are generally positive, with a 5.00 rating on the App Store based on 7 reviews. However, the limited number of reviews makes it difficult to gauge overall user satisfaction. One user review on MWM mentions "문의하기 너무 어렵네요" (too hard to contact). This is a potential customer support issue. The app's performance is acceptable for most users. The privacy concerns are the main drawback. Users should weigh the app's functionality against its data collection practices. The app's subscription model is not aggressive, which is a positive. The app's performance is a reflection of its development. It is a well-designed app with some privacy trade-offs.

The Permission Required: Camera and Biometrics

The app requests access to the camera and biometric hardware. The camera permission is used for taking photos within the app. The user can take a photo and share it immediately with their partner. This is a core feature of the app. The biometric permission (fingerprint or face recognition) is used for secure login. The app allows users to lock the app with biometric authentication. This adds a layer of privacy. The app also requests access to storage for saving photos and videos. These permissions are reasonable for a photo-sharing app. However, the app also requests permission to record audio. This is not a core feature. The app does not have a voice messaging feature. The audio permission may be used for future features, but it is not currently documented. The app also requests permission to run at startup and prevent the phone from sleeping. These permissions are used for notifications. The app sends notifications for shared events and reminders. The permission model is comprehensive, but it is not excessive for a feature-rich app. The user can deny certain permissions and still use the core features. The app's permission model is transparent. The user can see what permissions are requested and why. The app's privacy policy is available on the website. The app's permission model is a reflection of its functionality. It is a trade-off between convenience and privacy.